Instability on edge channel

Bug Description
It looks like indico and indico-celery are having stability issues on the edge channel:
kubectl get all -n indico-troubleshooting
NAME                                 READY   STATUS             RESTARTS        AGE
pod/redis-broker-operator-0          1/1     Running            1 (75m ago)     104m
pod/postgresql-k8s-operator-0        1/1     Running            1 (75m ago)     101m
pod/modeloperator-7b667dc68d-j9dqw   1/1     Running            1 (75m ago)     105m
pod/redis-cache-operator-0           1/1     Running            1 (75m ago)     103m
pod/nginx-ingress-integrator-0       2/2     Running            2 (75m ago)     94m
pod/redis-cache-0                    1/1     Running            1 (75m ago)     102m
pod/redis-broker-0                   1/1     Running            1 (75m ago)     104m
pod/postgresql-k8s-0                 1/1     Running            1 (75m ago)     101m
pod/indico-0                         3/5     CrashLoopBackOff   48 (110s ago)   105m

NAME                                         TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
service/modeloperator                        ClusterIP      <IP_ADDRESS>   <none>        17071/TCP        105m
service/indico                               ClusterIP      <IP_ADDRESS>   <none>        65535/TCP        105m
service/indico-endpoints                     ClusterIP      None             <none>        <none>           105m
service/redis-broker-operator                ClusterIP      <IP_ADDRESS>   <none>        30666/TCP        104m
service/redis-broker                         LoadBalancer   <IP_ADDRESS>    <pending>     6379:30682/TCP   104m
service/redis-broker-endpoints               ClusterIP      None             <none>        <none>           104m
service/redis-cache-operator                 ClusterIP      <IP_ADDRESS>    <none>        30666/TCP        103m
service/redis-cache                          LoadBalancer   <IP_ADDRESS>   <pending>     6379:30279/TCP   102m
service/redis-cache-endpoints                ClusterIP      None             <none>        <none>           102m
service/postgresql-k8s-operator              ClusterIP      <IP_ADDRESS>   <none>        30666/TCP        101m
service/postgresql-k8s-master                NodePort       <IP_ADDRESS>    <none>        5432:32415/TCP   101m
service/postgresql-k8s-standbys              NodePort       <IP_ADDRESS>   <none>        5432:31477/TCP   101m
service/postgresql-k8s                       ClusterIP      <IP_ADDRESS>   <none>        5432/TCP         101m
service/postgresql-k8s-endpoints             ClusterIP      None             <none>        <none>           101m
service/nginx-ingress-integrator             ClusterIP      <IP_ADDRESS>   <none>        65535/TCP        94m
service/nginx-ingress-integrator-endpoints   ClusterIP      None             <none>        <none>           94m
service/indico-service                       ClusterIP      <IP_ADDRESS>   <none>        8080/TCP         93m

NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/modeloperator   1/1     1            1           105m

NAME                                       DESIRED   CURRENT   READY   AGE
replicaset.apps/modeloperator-7b667dc68d   1         1         1       105m

NAME                                        READY   AGE
statefulset.apps/redis-broker-operator      1/1     104m
statefulset.apps/postgresql-k8s-operator    1/1     101m
statefulset.apps/redis-cache-operator       1/1     103m
statefulset.apps/nginx-ingress-integrator   1/1     94m
statefulset.apps/redis-cache                1/1     102m
statefulset.apps/redis-broker               1/1     104m
statefulset.apps/postgresql-k8s             1/1     101m
statefulset.apps/indico                     0/1     105m

To Reproduce

Deploy juju on the edge channel as per the documented approach

Environment
Model                   Controller  Cloud/Region        Version  SLA          Timestamp
indico-troubleshooting  micro       microk8s/localhost  2.9.33   unsupported  12:01:12+10:00

App                       Version                 Status   Scale  Charm                     Channel  Rev  Address         Exposed  Message
indico                                            waiting      1  indico                    edge      47  <IP_ADDRESS>  no       installing agent
nginx-ingress-integrator                          active       1  nginx-ingress-integrator  stable    27  <IP_ADDRESS>  no       Ingress with service IP(s): <IP_ADDRESS>
postgresql-k8s            .../postgresql@ed0e37f  active       1  postgresql-k8s            stable     4                  no       Pod configured
redis-broker              ubuntu/redis@691f315    active       1  redis-k8s                 stable     7                  no
redis-cache               ubuntu/redis@691f315    active       1  redis-k8s                 stable     7                  no

Unit                         Workload  Agent      Address      Ports     Message
indico/0*                    error     executing  <IP_ADDRESS>            crash loop backoff: back-off 5m0s restarting failed container=indico pod=indico-0_indico-troubleshooting(ac3fc40f-c245-4d23-a0ea-1cbc5038f7de)
nginx-ingress-integrator/0*  active    idle       <IP_ADDRESS>            Ingress with service IP(s): <IP_ADDRESS>
postgresql-k8s/0*            active    idle       <IP_ADDRESS>  5432/TCP  Pod configured
redis-broker/0*              active    idle       <IP_ADDRESS>  6379/TCP
redis-cache/0*               active    idle       <IP_ADDRESS>  6379/TCP

Relevant log output
kubectl logs indico-0 -c indico -n indico-troubleshooting --previous
2022-08-29T01:52:47.721Z [pebble] HTTP API server listening on ":38813".
2022-08-29T01:52:47.721Z [pebble] Started daemon.
2022-08-29T01:52:48.505Z [pebble] POST /v1/exec 4.592769ms 202
2022-08-29T01:52:48.508Z [pebble] GET /v1/tasks/1/websocket/control 1.593476ms 200
2022-08-29T01:52:48.509Z [pebble] GET /v1/tasks/1/websocket/stdio 97.518µs 200
2022-08-29T01:52:48.510Z [pebble] GET /v1/tasks/1/websocket/stderr 100.126µs 200
2022-08-29T01:52:52.512Z [pebble] GET /v1/changes/1/wait?timeout=4.000s 4.000263494s 504
2022-08-29T01:52:55.233Z [pebble] GET /v1/changes/1/wait?timeout=4.000s 2.719315873s 200
2022-08-29T01:52:55.303Z [pebble] POST /v1/layers 732.939µs 200
2022-08-29T01:52:55.339Z [pebble] POST /v1/services 3.234324ms 202
2022-08-29T01:52:55.342Z [pebble] Service "indico" starting: /srv/indico/start-indico.sh
2022-08-29T01:52:56.378Z [pebble] GET /v1/changes/2/wait?timeout=4.000s 1.037336613s 200
2022-08-29T01:52:57.982Z [indico] /usr/local/lib/python3.9/dist-packages/indico/core/config.py:179: UserWarning: Ignoring unknown config key OS
2022-08-29T01:52:57.982Z [indico]   warnings.warn(f'Ignoring unknown config key {key}')
2022-08-29T01:52:57.982Z [indico] /usr/local/lib/python3.9/dist-packages/indico/core/config.py:179: UserWarning: Ignoring unknown config key AST
2022-08-29T01:52:57.982Z [indico]   warnings.warn(f'Ignoring unknown config key {key}')
2022-08-29T01:53:05.309Z [pebble] Check "indico-ready" failure 1 (threshold 3): dial tcp [::1]:8081: connect: connection refused
2022-08-29T01:53:06.856Z [indico] Your database is not empty!
2022-08-29T01:53:06.856Z [indico] If you just added a new table/model, create an alembic revision instead!
2022-08-29T01:53:06.920Z [indico]
2022-08-29T01:53:06.920Z [indico] Tables in your database:
2022-08-29T01:53:06.920Z [indico]   * attachments.folders
2022-08-29T01:53:06.920Z [indico]   * attachments.folder_principals
2022-08-29T01:53:06.920Z [indico]   * attachments.attachments
2022-08-29T01:53:06.920Z [indico]   * attachments.legacy_folder_id_map
2022-08-29T01:53:06.920Z [indico]   * attachments.attachment_principals
2022-08-29T01:53:06.920Z [indico]   * attachments.files
2022-08-29T01:53:06.920Z [indico]   * attachments.legacy_attachment_id_map
2022-08-29T01:53:06.920Z [indico]   * categories.categories
2022-08-29T01:53:06.920Z [indico]   * categories.settings
2022-08-29T01:53:06.920Z [indico]   * categories.legacy_id_map
2022-08-29T01:53:06.920Z [indico]   * categories.roles
2022-08-29T01:53:06.920Z [indico]   * categories.logs
2022-08-29T01:53:06.920Z [indico]   * categories.event_move_requests
2022-08-29T01:53:06.920Z [indico]   * categories.principals
2022-08-29T01:53:06.920Z [indico]   * categories.role_members
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.email_templates
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.abstract_review_questions
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.abstracts
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.abstract_reviews
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.email_logs
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.abstract_person_links
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.reviewed_for_tracks
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.submitted_for_tracks
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.abstract_comments
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.abstract_field_values
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.files
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.abstract_review_ratings
2022-08-29T01:53:06.920Z [indico]   * event_abstracts.proposed_for_tracks
2022-08-29T01:53:06.920Z [indico]   * event_editing.file_types
2022-08-29T01:53:06.920Z [indico]   * event_editing.review_conditions
2022-08-29T01:53:06.920Z [indico]   * event_editing.tags
2022-08-29T01:53:06.920Z [indico]   * event_editing.review_condition_file_types
2022-08-29T01:53:06.920Z [indico]   * event_editing.revisions
2022-08-29T01:53:06.920Z [indico]   * event_editing.revision_tags
2022-08-29T01:53:06.920Z [indico]   * event_editing.comments
2022-08-29T01:53:06.920Z [indico]   * event_editing.revision_files
2022-08-29T01:53:06.920Z [indico]   * event_editing.editables
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.review_questions
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.templates
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.competences
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.revisions
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.judges
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.content_reviewers
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.layout_reviewers
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.reviews
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.review_comments
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.files
2022-08-29T01:53:06.920Z [indico]   * event_paper_reviewing.review_ratings
2022-08-29T01:53:06.920Z [indico]   * event_registration.forms
2022-08-29T01:53:06.920Z [indico]   * event_registration.tags
2022-08-29T01:53:06.920Z [indico]   * event_registration.legacy_registration_map
2022-08-29T01:53:06.920Z [indico]   * event_registration.registrations
2022-08-29T01:53:06.920Z [indico]   * event_registration.registration_tags
2022-08-29T01:53:06.920Z [indico]   * event_registration.form_items
2022-08-29T01:53:06.920Z [indico]   * event_registration.invitations
2022-08-29T01:53:06.920Z [indico]   * event_registration.form_field_data
2022-08-29T01:53:06.920Z [indico]   * event_registration.registration_data
2022-08-29T01:53:06.920Z [indico]   * event_surveys.surveys
2022-08-29T01:53:06.920Z [indico]   * event_surveys.submissions
2022-08-29T01:53:06.920Z [indico]   * event_surveys.items
2022-08-29T01:53:06.920Z [indico]   * event_surveys.anonymous_submissions
2022-08-29T01:53:06.920Z [indico]   * event_surveys.answers
2022-08-29T01:53:06.920Z [indico]   * events.events
2022-08-29T01:53:06.920Z [indico]   * events.settings
2022-08-29T01:53:06.920Z [indico]   * events.legacy_id_map
2022-08-29T01:53:06.920Z [indico]   * events.image_files
2022-08-29T01:53:06.920Z [indico]   * events.menu_entries
2022-08-29T01:53:06.920Z [indico]   * events.pages
2022-08-29T01:53:06.920Z [indico]   * events.contribution_fields
2022-08-29T01:53:06.920Z [indico]   * events.event_references
2022-08-29T01:53:06.920Z [indico]   * events.roles
2022-08-29T01:53:06.921Z [indico]   * events.static_list_links
2022-08-29T01:53:06.921Z [indico]   * events.session_types
2022-08-29T01:53:06.921Z [indico]   * events.contribution_types
2022-08-29T01:53:06.921Z [indico]   * events.track_groups
2022-08-29T01:53:06.921Z [indico]   * events.legacy_page_id_map
2022-08-29T01:53:06.921Z [indico]   * events.settings_principals
2022-08-29T01:53:06.921Z [indico]   * events.logs
2022-08-29T01:53:06.921Z [indico]   * events.persons
2022-08-29T01:53:06.921Z [indico]   * events.static_sites
2022-08-29T01:53:06.921Z [indico]   * events.role_members
2022-08-29T01:53:06.921Z [indico]   * events.principals
2022-08-29T01:53:06.921Z [indico]   * events.reminders
2022-08-29T01:53:06.921Z [indico]   * events.agreements
2022-08-29T01:53:06.921Z [indico]   * events.legacy_image_id_map
2022-08-29T01:53:06.921Z [indico]   * events.requests
2022-08-29T01:53:06.921Z [indico]   * events.vc_rooms
2022-08-29T01:53:06.921Z [indico]   * events.event_person_links
2022-08-29T01:53:06.922Z [indico]   * events.sessions
2022-08-29T01:53:06.922Z [indico]   * events.breaks
2022-08-29T01:53:06.922Z [indico]   * events.session_principals
2022-08-29T01:53:06.922Z [indico]   * events.session_blocks
2022-08-29T01:53:06.922Z [indico]   * events.legacy_session_id_map
2022-08-29T01:53:06.922Z [indico]   * events.tracks
2022-08-29T01:53:06.922Z [indico]   * events.session_block_person_links
2022-08-29T01:53:06.922Z [indico]   * events.legacy_session_block_id_map
2022-08-29T01:53:06.922Z [indico]   * events.track_principals
2022-08-29T01:53:06.922Z [indico]   * events.contributions
2022-08-29T01:53:06.922Z [indico]   * events.timetable_entries
2022-08-29T01:53:06.922Z [indico]   * events.contribution_field_values
2022-08-29T01:53:06.922Z [indico]   * events.subcontributions
2022-08-29T01:53:06.922Z [indico]   * events.contribution_person_links
2022-08-29T01:53:06.923Z [indico]   * events.contribution_references
2022-08-29T01:53:06.923Z [indico]   * events.legacy_contribution_id_map
2022-08-29T01:53:06.923Z [indico]   * events.contribution_principals
2022-08-29T01:53:06.923Z [indico]   * events.vc_room_events
2022-08-29T01:53:06.923Z [indico]   * events.notes
2022-08-29T01:53:06.923Z [indico]   * events.subcontribution_person_links
2022-08-29T01:53:06.923Z [indico]   * events.subcontribution_references
2022-08-29T01:53:06.923Z [indico]   * events.legacy_subcontribution_id_map
2022-08-29T01:53:06.923Z [indico]   * events.note_revisions
2022-08-29T01:53:06.923Z [indico]   * events.payment_transactions
2022-08-29T01:53:06.923Z [indico]   * events.series
2022-08-29T01:53:06.923Z [indico]   * events.labels
2022-08-29T01:53:06.923Z [indico]   * indico.settings
2022-08-29T01:53:06.923Z [indico]   * indico.news
2022-08-29T01:53:06.923Z [indico]   * indico.affiliations
2022-08-29T01:53:06.923Z [indico]   * indico.designer_templates
2022-08-29T01:53:06.923Z [indico]   * indico.ip_network_groups
2022-08-29T01:53:06.923Z [indico]   * indico.ip_networks
2022-08-29T01:53:06.923Z [indico]   * indico.reference_types
2022-08-29T01:53:06.923Z [indico]   * indico.settings_principals
2022-08-29T01:53:06.923Z [indico]   * indico.files
2022-08-29T01:53:06.923Z [indico]   * indico.designer_image_files
2022-08-29T01:53:06.923Z [indico]   * oauth.applications
2022-08-29T01:53:06.923Z [indico]   * oauth.application_user_links
2022-08-29T01:53:06.923Z [indico]   * oauth.tokens
2022-08-29T01:53:06.923Z [indico]   * roombooking.map_areas
2022-08-29T01:53:06.923Z [indico]   * roombooking.equipment_types
2022-08-29T01:53:06.923Z [indico]   * roombooking.equipment_features
2022-08-29T01:53:06.923Z [indico]   * roombooking.features
2022-08-29T01:53:06.923Z [indico]   * roombooking.blockings
2022-08-29T01:53:06.923Z [indico]   * roombooking.locations
2022-08-29T01:53:06.923Z [indico]   * roombooking.rooms
2022-08-29T01:53:06.923Z [indico]   * roombooking.photos
2022-08-29T01:53:06.923Z [indico]   * roombooking.room_nonbookable_periods
2022-08-29T01:53:06.923Z [indico]   * roombooking.blocked_rooms
2022-08-29T01:53:06.923Z [indico]   * roombooking.blocking_principals
2022-08-29T01:53:06.923Z [indico]   * roombooking.room_equipment
2022-08-29T01:53:06.923Z [indico]   * roombooking.favorite_rooms
2022-08-29T01:53:06.923Z [indico]   * roombooking.room_principals
2022-08-29T01:53:06.924Z [indico]   * roombooking.room_attributes
2022-08-29T01:53:06.924Z [indico]   * roombooking.room_attribute_values
2022-08-29T01:53:06.924Z [indico]   * roombooking.room_bookable_hours
2022-08-29T01:53:06.924Z [indico]   * roombooking.reservation_links
2022-08-29T01:53:06.924Z [indico]   * roombooking.reservations
2022-08-29T01:53:06.924Z [indico]   * roombooking.reservation_edit_logs
2022-08-29T01:53:06.924Z [indico]   * roombooking.reservation_occurrences
2022-08-29T01:53:06.924Z [indico]   * users.registration_requests
2022-08-29T01:53:06.924Z [indico]   * users.users
2022-08-29T01:53:06.924Z [indico]   * users.groups
2022-08-29T01:53:06.924Z [indico]   * users.settings
2022-08-29T01:53:06.924Z [indico]   * users.emails
2022-08-29T01:53:06.924Z [indico]   * users.favorite_users
2022-08-29T01:53:06.924Z [indico]   * users.favorite_categories
2022-08-29T01:53:06.924Z [indico]   * users.favorite_events
2022-08-29T01:53:06.924Z [indico]   * users.tokens
2022-08-29T01:53:06.924Z [indico]   * users.identities
2022-08-29T01:53:06.924Z [indico]   * users.suggested_categories
2022-08-29T01:53:06.924Z [indico]   * users.group_members
2022-08-29T01:53:06.924Z [indico]   * users.api_keys
2022-08-29T01:53:11.632Z [indico] /usr/local/lib/python3.9/dist-packages/indico/core/config.py:179: UserWarning: Ignoring unknown config key OS
2022-08-29T01:53:11.632Z [indico]   warnings.warn(f'Ignoring unknown config key {key}')
2022-08-29T01:53:11.632Z [indico] /usr/local/lib/python3.9/dist-packages/indico/core/config.py:179: UserWarning: Ignoring unknown config key AST
2022-08-29T01:53:11.632Z [indico]   warnings.warn(f'Ignoring unknown config key {key}')
2022-08-29T01:53:15.306Z [pebble] Check "indico-ready" failure 2 (threshold 3): dial tcp [::1]:8081: connect: connection refused
2022-08-29T01:53:19.838Z [indico] INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
2022-08-29T01:53:19.839Z [indico] INFO  [alembic.runtime.migration] Will assume transactional DDL.
2022-08-29T01:53:25.263Z [indico] /usr/local/lib/python3.9/dist-packages/indico/core/config.py:179: UserWarning: Ignoring unknown config key OS
2022-08-29T01:53:25.263Z [indico]   warnings.warn(f'Ignoring unknown config key {key}')
2022-08-29T01:53:25.263Z [indico] /usr/local/lib/python3.9/dist-packages/indico/core/config.py:179: UserWarning: Ignoring unknown config key AST
2022-08-29T01:53:25.263Z [indico]   warnings.warn(f'Ignoring unknown config key {key}')
2022-08-29T01:53:25.313Z [pebble] Check "indico-ready" failure 3 (threshold 3): dial tcp [::1]:8081: connect: connection refused
2022-08-29T01:53:25.313Z [pebble] Check "indico-ready" failure threshold 3 hit, triggering action
2022-08-29T01:53:27.192Z [pebble] Exiting on terminated signal.
2022-08-29T01:53:27.231Z [pebble] Stopping all running services.
2022-08-29T01:53:27.283Z [pebble] Service "indico" stopped

kubectl logs indico-0 -c indico-celery -n indico-troubleshooting --previous
2022-08-29T01:54:31.991Z [pebble] HTTP API server listening on ":38814".
2022-08-29T01:54:31.991Z [pebble] Started daemon.
2022-08-29T01:54:32.802Z [pebble] POST /v1/exec 44.734693ms 202
2022-08-29T01:54:32.806Z [pebble] GET /v1/tasks/1/websocket/control 1.903068ms 200
2022-08-29T01:54:32.807Z [pebble] GET /v1/tasks/1/websocket/stdio 125.39µs 200
2022-08-29T01:54:32.807Z [pebble] GET /v1/tasks/1/websocket/stderr 77.979µs 200
2022-08-29T01:54:36.812Z [pebble] GET /v1/changes/1/wait?timeout=4.000s 4.003235043s 504
2022-08-29T01:54:38.558Z [pebble] GET /v1/changes/1/wait?timeout=4.000s 1.743602256s 200
2022-08-29T01:54:38.637Z [pebble] POST /v1/layers 969.759µs 200
2022-08-29T01:54:38.679Z [pebble] POST /v1/services 3.059161ms 202
2022-08-29T01:54:38.682Z [pebble] Service "indico-celery" starting: /usr/local/bin/indico celery worker -B
2022-08-29T01:54:39.765Z [pebble] GET /v1/changes/2/wait?timeout=4.000s 1.084934487s 200
2022-08-29T01:54:41.394Z [indico-celery] /usr/local/lib/python3.9/dist-packages/indico/core/config.py:179: UserWarning: Ignoring unknown config key OS
2022-08-29T01:54:41.394Z [indico-celery]   warnings.warn(f'Ignoring unknown config key {key}')
2022-08-29T01:54:41.394Z [indico-celery] /usr/local/lib/python3.9/dist-packages/indico/core/config.py:179: UserWarning: Ignoring unknown config key AST
2022-08-29T01:54:41.394Z [indico-celery]   warnings.warn(f'Ignoring unknown config key {key}')
2022-08-29T01:54:48.608Z [indico-celery]
2022-08-29T01:54:48.608Z [indico-celery]  -------------- celery@indico-0 v5.2.7 (dawn-chorus)
2022-08-29T01:54:48.608Z [indico-celery] --- ***** -----
2022-08-29T01:54:48.608Z [indico-celery] -- ******* ---- Linux-5.15.0-46-generic-x86_64-with-glibc2.35 2022-08-29 01:54:48
2022-08-29T01:54:48.608Z [indico-celery] - *** --- * ---
2022-08-29T01:54:48.608Z [indico-celery] - ** ---------- [config]
2022-08-29T01:54:48.608Z [indico-celery] - ** ---------- .> app:         indico:0x7f0c1015aee0
2022-08-29T01:54:48.608Z [indico-celery] - ** ---------- .> transport:   redis://<IP_ADDRESS>:6379//
2022-08-29T01:54:48.608Z [indico-celery] - ** ---------- .> results:     redis://<IP_ADDRESS>:6379/
2022-08-29T01:54:48.608Z [indico-celery] - *** --- * --- .> concurrency: 4 (prefork)
2022-08-29T01:54:48.608Z [indico-celery] -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
2022-08-29T01:54:48.608Z [indico-celery] --- ***** -----
2022-08-29T01:54:48.608Z [indico-celery]  -------------- [queues]
2022-08-29T01:54:48.608Z [indico-celery]                 .> celery           exchange=celery(direct) key=celery
2022-08-29T01:54:48.608Z [indico-celery]
2022-08-29T01:54:48.608Z [indico-celery]
2022-08-29T01:54:48.907Z [indico-celery] 2022-08-29 01:54:48,906  INFO<PHONE_NUMBER>000000  -       celery.beat               beat: Starting...
2022-08-29T01:55:17.654Z [pebble] Check "ready" failure 1 (threshold 3): exec check timed out
2022-08-29T01:55:37.660Z [pebble] Check "ready" failure 2 (threshold 3): exec check timed out
2022-08-29T01:55:57.659Z [pebble] Check "ready" failure 3 (threshold 3): exec check timed out
2022-08-29T01:55:57.659Z [pebble] Check "ready" failure threshold 3 hit, triggering action
2022-08-29T01:56:02.236Z [pebble] Exiting on terminated signal.
2022-08-29T01:56:02.241Z [pebble] Stopping all running services.
2022-08-29T01:56:02.257Z [indico-celery]
2022-08-29T01:56:02.257Z [indico-celery] worker: Warm shutdown (MainProcess)
2022-08-29T01:56:03.285Z [indico-celery] 2022-08-29 01:56:03,285  INFO<PHONE_NUMBER>000000  -       celery.beat               beat: Shutting down...
2022-08-29T01:56:05.837Z [pebble] Service "indico-celery" stopped

### Additional context

_No response_

We believe this is because pebble checks at that time were "alive" rather than "ready", which has since been reverted. Can you confirm latest edge now works for you?

 The health checks have been modified recently. Can you double check if this is still an issue?

I let this run over the weekend and it still seems to be an issue
juju status
Model   Controller  Cloud/Region        Version  SLA          Timestamp
indico  micro       microk8s/localhost  2.9.33   unsupported  14:53:40+10:00

App     Version  Status   Scale  Charm   Channel  Rev  Address       Exposed  Message
indico           waiting      1  indico  edge      78  <IP_ADDRESS>  no       installing agent

Unit       Workload  Agent  Address      Ports  Message
indico/0*  waiting   idle   <IP_ADDRESS>         Waiting for redis-broker relation

kubectl get all -n indico
NAME                                 READY   STATUS    RESTARTS         AGE
pod/modeloperator-5b855dc787-s74x8   1/1     Running   24 (4h26m ago)   3d5h
pod/indico-0                         5/5     Running   159 (50m ago)    3d5h

NAME                       TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
service/modeloperator      ClusterIP   <IP_ADDRESS>   <none>        17071/TCP   3d5h
service/indico             ClusterIP   <IP_ADDRESS>   <none>        65535/TCP   3d5h
service/indico-endpoints   ClusterIP   None           <none>        <none>      3d5h

NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/modeloperator   1/1     1            1           3d5h

NAME                                       DESIRED   CURRENT   READY   AGE
replicaset.apps/modeloperator-5b855dc787   1         1         1       3d5h

NAME                      READY   AGE
statefulset.apps/indico   1/1     3d5h

kubectl logs --previous indico-0 -n indico -c indico
2022-09-19T03:04:29.110Z [pebble] HTTP API server listening on ":38813".
2022-09-19T03:04:29.110Z [pebble] Started daemon.
2022-09-19T04:03:07.517Z [pebble] Exiting on terminated signal.

Hi @jdkandersson , based on our experience operating the charm, I think we can close this now


ok.ru

Checklist

[X] I'm reporting a broken site support
[X] I've verified that I'm running youtube-dl version 2020.05.03
[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 issues including closed ones

Verbose log
./youtube-dl  https://ok.ru/video/c1466275 --verbose
[debug] System config: []
[debug] User config: [u'--no-mtime']
[debug] Custom config: []
[debug] Command-line args: [u'https://ok.ru/video/c1466275', u'--verbose']
[debug] Encodings: locale ISO-8859-1, fs ISO-8859-1, out ISO-8859-1, pref ISO-8859-1
[debug] youtube-dl version 2020.05.03
[debug] Python version 2.7.17 (CPython) - Linux-4.18.0-25-generic-x86_64-with-Ubuntu-18.04-bionic
[debug] exe versions: ffmpeg 3.4.6, ffprobe 3.4.6, phantomjs ., rtmpdump 2.4
[debug] Proxy map: {}
[generic] c1466275: Requesting header
WARNING: Falling back on generic information extractor.
[generic] c1466275: Downloading webpage
[generic] c1466275: Extracting information
ERROR: Unsupported URL: https://ok.ru/video/c1466275
Traceback (most recent call last):
  File "./youtube-dl/youtube_dl/extractor/generic.py", line 2378, in _real_extract
    doc = compat_etree_fromstring(webpage.encode('utf-8'))
  File "./youtube-dl/youtube_dl/compat.py", line 2551, in compat_etree_fromstring
    doc = _XML(text, parser=etree.XMLParser(target=_TreeBuilder(element_factory=_element_factory)))
  File "./youtube-dl/youtube_dl/compat.py", line 2540, in _XML
    parser.feed(text)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1659, in feed
    self._raiseerror(v)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1523, in _raiseerror
    raise err
ParseError: not well-formed (invalid token): line 8, column 54
Traceback (most recent call last):
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 797, in extract_info
    ie_result = ie.extract(url)
  File "./youtube-dl/youtube_dl/extractor/common.py", line 530, in extract
    ie_result = self._real_extract(url)
  File "./youtube-dl/youtube_dl/extractor/generic.py", line 3370, in _real_extract
    raise UnsupportedError(url)
UnsupportedError: Unsupported URL: https://ok.ru/video/c1466275

Description
Related
https://github.com/ytdl-org/youtube-dl/issues/23874
WRITE DESCRIPTION HERE
Thanks

i think https://ok.ru/video/c1466275 it's not a video url
maybe playlist
i assume ok.ru extractor doesn't support playlists


1.12

the Hidden Syntaxes thing doesn't fully work.
It does not block /minecraft:

The /minecraft: commands are the reason that feature exists. The code should always work with any command unless @GiansCode changed anything, which I doubt.
Check if you enabled the feature in the plugin config or if there are errors in the console regarding eZProtector.

is enabled and does not work, that is why I opened an issue.

Haven't changed a thing and cannot recreate this using latest version on 1.11. Maybe 1.12 changed something, I'll test this when I finish the update in the coming days (just been incredibly busy).

Just realized the plugin hasn't been updated for 1.12 therefore shouldn't even enable itself on startup. @pedrocarcamo please wait for an update before posting possible bugs with newer versions of minecraft/spigot.


Misspelling on Getting Started Page

Hi,
Just wanted to let you know about some misspelled words on the getting started Page. In the "Removing Settings" section there is the following line "publc static void RemoveUserName() => AppSettings.Remove(nameof(UserName));".
Here is the link to the page, https://jamesmontemagno.github.io/SettingsPlugin/RemoveSettings.html
Not really a problem, just wanted to let you know. Cheers!

Send a PR


[BUG] login issues in sources

I cant login into my booknet and dreame account after get cookies. Can u please explain me in detail how to login after get cookies.  After logging in my browser it is not downloading in automatic

When you click Get Cookies, a Browaer window should open. Login like you normally would and close the window.
Now on automatic you should just need to select Use account before checking.

I have logged in but the chapter container is not found and it could not connect for booknet.com.

Should be fixed now.

When I attempt to sign in with a cookie the program just locks up

Booknet should be fixed now. Do you also have a problem with Dreame?

Yeah dreame login also not working

Another person reported a problem where the login cookies were not working for webnovel.com but which was fixed with a relog, so maybe try doing that. I can't actually test Dreame since I can't create an account but it should work.
I've also added a button, which shows after starting the browser, to save the cookies.

Thank you 😄👍 Ut is working


[SALTSTACK] - include SqliteBrowser

Could it be able to get SqliteBrowser installed in to the base setup?
Two options

old but workable version  ships with Ubuntu 22.04
add newest release with 3rd party repo for up-to-date builds see official download page - https://sqlitebrowser.org/dl/

Hi @grrrrr I'm sure this is doable. I'll take a look at it tomorrow!

Hey @grrrrr , I've created the necessary state files and am running some final tests, then if all is well I'll submit the PR tonight.
Cheers!


accuracy is 0

hi：
the problem is accuracy is always 0 when i applying train_net.py,meanwhile,the loss is decreasing and accuracy on lfw is incresing.
i think that i applyed the one you revised at num_class..look at the error below:
class_number:85742(MS1M-V2)
epoch 0, total_step 1250, total loss is 42.33 , inference loss is 42.01, reg_loss is 0.32, training accuracy is 0.000000, time 323.625 samples/sec
epoch 0, total_step 1300, total loss is 42.36 , inference loss is 42.03, reg_loss is 0.32, training accuracy is 0.000000, time 319.744 samples/sec
epoch 0, total_step 1350, total loss is 42.08 , inference loss is 41.76, reg_loss is 0.32, training accuracy is 0.000000, time 322.450 samples/sec
epoch 0, total_step 1400, total loss is 42.24 , inference loss is 41.92, reg_loss is 0.32, training accuracy is 0.000000, time 319.986 samples/sec
epoch 0, total_step 1450, total loss is 42.51 , inference loss is 42.19, reg_loss is 0.32, training accuracy is 0.000000, time 322.289 samples/sec
epoch 0, total_step 1500, total loss is 42.49 , inference loss is 42.17, reg_loss is 0.32, training accuracy is 0.000000, time 318.947 samples/sec
epoch 0, total_step 1550, total loss is 42.36 , inference loss is 42.04, reg_loss is 0.32, training accuracy is 0.000000, time 314.517 samples/sec
epoch 0, total_step 1600, total loss is 42.45 , inference loss is 42.14, reg_loss is 0.31, training accuracy is 0.000000, time 324.133 samples/sec
epoch 0, total_step 1650, total loss is 42.35 , inference loss is 42.03, reg_loss is 0.31, training accuracy is 0.000000, time 322.223 samples/sec
epoch 0, total_step 1700, total loss is 42.44 , inference loss is 42.12, reg_loss is 0.31, training accuracy is 0.000000, time 323.349 samples/sec
thresholds max: 0.71 <=> min: 0.49
total time 13.695s to evaluate 12000 images of lfw
Accuracy: 0.716+-0.016
Validation rate: 0.03367+-0.01538 @ FAR=0.00100
fpr and tpr: 0.725 0.875
Area Under Curve (AUC): 0.799
Equal Error Rate (EER): 0.275

I have the same problem with you when I run python train_nets.py --class_number=85742,the epoch and training accuracy are always 0,only the reg_loss is decreasing,but accuracy on lfw is incresing.Have you solved this problem?Please tell me details.Thank you very much!

just keep running

just keep running

I keep running for 11 epochs and accuracy in validation set rise to 99.5%,but training accuracy is still always 0. Do you know why? Thank you very much!

same with #40


Update galley to 0.16.8

retest this please

Seems this test failure is caused by galley fix. I've tested against both galley-0.16.8 vs. galley-0.16.7, and fount it can pass with 0.16.7, but failed on 0.16.8.
We must check what happened with this fix.

This is weird. I pushed a pr for 0.16.8-snapshot and it passed. Maybe it used an old snapshot. Let's look at it.


feat(sdk): Load KAS keys from policy service

Uses the new 'cached' field in the kas registry, if it is set
This wasn't previously used since the SDK requires the key identifiers and algorithm which were not present in the old 'public key' field
Before merging this, we should merge the proto change to avoid causing autor-releaser

Sorry, just realized those comments ^^ should be on https://github.com/opentdf/platform/pull/1347 instead. Resolving here and adding there.

This looks good to me, but it looks like the pipeline is ❌ and it will probably have conflicts with #1318 ?

yes, I'll fix that up after merging this.


Change namespace of SDK

Change Description
I renamed the neamespace from Microsoft.Presidio to Presidio
In order to upload the nuget to Presidio org on nuget.org
Issue reference
This PR fixes issue #XX
Checklist

[ ] I have reviewed the contribution guidelines
[ ] I have signed the CLA
[ ] My code includes unit tests
[ ] All unit tests and lint checks pass locally
[ ] My PR contains documentation updates / additions if required

The automated refactoring and SDK generation override the UT, in the last commit I fixed it and the tests are back. Please approve
@navalev , @SharonHart


Add name of community to marker on initial minimap

Right now it's just the marker thingy, can we change that to be a circle marker + label?  That'd be svelte.

This wouldn't really work well in practice.  The base layer (USGS) has good place labels most of the time and it'd be very hard to float an additional place label in many cases.  Closing.


feat: add container background on hover theming option

Description
https://gr4vy.atlassian.net/browse/TA-5571
Contribution guidelines
For contribution guidelines, styleguide, and other helpful information please
see the CONTRIBUTING.md file in the root of this project.

:rocket: PR was released in v2.24.3 :rocket:


Write an informational spec on transforming ko into a rock

Context
Write a spec on converting a ko project into a rockcraft.yaml
What needs to get done

Explore how to transform ko project into a rock
Write the spec and get it reviewed

Definition of Done
spec is written and approved

nice suggestion @kimwnasptd, adding to the spec

spec KF111 approved!


Images to video

UI improvements, I think it looks slightly better and fits in better
main features:
mp4 is now created where where it is wanted (no need to file write and then copy the data) -> I also believe this was corrupting the data, mp4 looked funky sometimes at the start and end
decoupled the webm creation and the mp4 conversion. Mp4 now created and downloaded on request from the user

The Videogen bridge uses all the external API to collect the data before rendering everything for etro in videogen
before the getScript API change i was using fetch images and etro was trying to do a http get for some reason instead of loading the local files
subtitle generation per section is fine, and works correclty I wasn't able to test the audio but with local files it should be fine


Do not works with PHP 7.2?

After installing and login succesfully I get
ErrorException in 848f5cb076f09c2c022ca47012713908eaad38c7.php line 33:
count(): Parameter must be an array or an object that implements Countable (View: /var/www/html/test/test1/vendor/crocodicstudio/crudbooster/src/views/sidebar.blade.php) (View: /var/www/html/test/test1/vendor/crocodicstudio/crudbooster/src/views/sidebar.blade.php) (View: /var/www/html/test/test1/vendor/crocodicstudio/crudbooster/src/views/sidebar.blade.php)
I read some threads somewhere were exist a workaround from sidebar.blade.php, but then the problem is in vendor/crocodicstudio/crudbooster/src/views/default/table.blade.php.
Exist some way of fix them?
Thanks.

ErrorException in abed363cfe67d91d3658fd2b5b9c9ca81b8cbde9.php line 33: count(): Parameter must be an array or an object that implements Countable (View: /var/www/html/crudbooster-sample-1.3/vendor/crocodicstudio/crudbooster/src/views/sidebar.blade.php) (View: /var/www/html/crudbooster-sample-1.3/vendor/crocodicstudio/crudbooster/src/views/sidebar.blade.php) (View: /var/www/html/crudbooster-sample-1.3/vendor/crocodicstudio/crudbooster/src/views/sidebar.blade.php)
Hallo sir, same with me. I have using php 7.2, and error notification like that :(

This sample not working on  PHP 7.2

how to fix this?

Add this to routes/web.php:
`<?php
if(version_compare(PHP_VERSION, '7.2.0', '>=')) {
error_reporting(E_ALL ^ E_NOTICE ^ E_WARNING);
}
`
I tested this on Php 7.2 and and is working fine.
Just a side note, that this particular app, will have issue with export to excel due to a php_zip.exe file extension requirement on Php 7.2 on xampp setup for windows. May work for other OS. I had to revert back to Php 7.1.30 to get this working as expected.


feat(prettier): support for printing objects with longer properties

Current dependencies on/for this PR:

main

PR #1352

PR #1353   👈

This stack of pull requests is managed by Graphite.

Merge activity

Nov 16, 7:43 AM: @Boshen started a stack merge that includes this pull request via Graphite.


Source code modules

Similar to CABL modules, it should be possible to have specific modules in the project configuration.

Use profiles


fix typo in mention notifications screen

fixes a typo in the mention screen for username notifications

@svelle Is this ready for review?

@svelle Is this ready for review?

@hanzei yes it is, thanks for checking.

/update-branch


Add possibility to exclude trackers from clean_transmission

Motivation for changes:
I want to exclude torrents from a certain tracker to be removed from transmission
Currently, the clean_transmission plugin allows only to include torrents from a certain tracker, not exclude them. This does not fit the use case where you want to keep seeding torrents from your private trackers up to a certain ratio, but not other ones.
Detailed changes:

Add tracker_mode property which allows you to specify whether you want to include torrents that have a tracker matching the tracker pattern (current behaviour) or  exclude them.

Config usage if relevant (new plugin or updated schema):
      # clean all torrents but those from .se trackers
      clean_transmission:
        finished_for: 2 hours
        tracker: '.se$'
        tracker_mode: 'exclude'

Like @gazpachoking said in gitter, I vote into making clean_transmission into a regular output plugin that can operate on entries with input such as from_transmission. Then it could benefit from all filter plugins (among other things)  and wouldn't require custom stuff like this.

any progress on this?

I gues the feature made it through in #1482. Oh well...


How to build Android library with GPU delegate?

I have stability issues with running my model on Android with GPU delegate.
So I thought I can rebuild the library from scratch and thy the most fresh one, but I can't figure out how to do it.
Actually I need to build the library, that you uploaded here. I would like to build libtensorflowlite_c_arm64_delegate.so for the beginning.
I tried to build TensorFlow with different parameters. The most successful was this one, which I found here:
bazel build -c opt --config=android_arm64 //tensorflow/lite/c:tensorflowlite_c
I've got the library libtensorflowlite_c.so for arm64 without GPU delegate and it is working.
How to build Android library with GPU delegate?

Ok. I've managed to build the Android library with usual TensorFlow and GPU together. It looks like you are using some custom build instructions to archive that.
Building
I added the following lines at the end of this file
tflite_jni_binary(
    name = "libtensorflowlite_jni_normal_with_gpu.so", # <-- the new name here
    linkscript = ":tflite_version_script.lds",
    deps = [
        "//tensorflow/lite/c:c_api",
        "//tensorflow/lite/c:c_api_experimental",
        "//tensorflow/lite/delegates/nnapi/java/src/main/native",
        "//tensorflow/lite/delegates/xnnpack:xnnpack_delegate",
        "//tensorflow/lite/java/src/main/native",
        "//tensorflow/lite/delegates/gpu/java/src/main/native", # <-- this line was added
    ],
)

Then I started the command
bazel build -c opt --config=android_arm64 //tensorflow/lite/java:libtensorflowlite_jni_normal_with_gpu.so
Check
I've checked the symbols using this command:
nm -gDC libtensorflowlite_jni_normal_with_gpu.so
All the required symbols are present: the usual options TfLiteInterpreterOptionsCreate as well as the delegate one TfLiteGpuDelegateV2Create.
Conclusion

It looks like my app is working and much more stable, so I think I did it right
It makes sense to add these notes to Readme or to Wiki
One another idea is instead of using local precompiled so-libraries to use standard libraries Maven as mentioned here:

dependencies {
    implementation 'org.tensorflow:tensorflow-lite:2.3.0'
    implementation 'org.tensorflow:tensorflow-lite-gpu:2.3.0'
}

What do you think?

Thanks a lot @applikationsprogramvara for sharing this guide and your interests in project.  The idea of using maven libraries is great.  I have tested it locally for android and I think we should include it in the package. Have you tested this on iOS too?

@am15h nope. I was not lucky to start this example. All my attempts ended up with errors.

Hi @applikationsprogramvara, I have added this tutorial in wiki, https://github.com/am15h/tflite_flutter_plugin/wiki/Build-android-binaries-with-GPU-delegate. Please review it and make edits if required. Also as we are discussing binary placing in this thread https://github.com/am15h/tflite_flutter_plugin/issues/110, I am closing this issue. Thanks a lot for your contribution.


Keep filesystem labels

This makes some changes to display and preserve all filesystem labels rather than just for ext filesystems.
Displaying of labels should be supported for any filesystem supported by the kernel (using lsblk), while copying labels is supported for a limited set of filesystems (just ext and fat for existing filesystems, a few more for new filesystems).
See the commit messages for some more details.
These changes were previously submitted at https://github.com/billw2/rpi-clone/pull/101 and have been in use in my project since that PR was submitted four years ago. Now I've just rebased and reviewed them, the changes still applied without issue.
This also fixes #7.

Just spotted your PR, after my Pi didn't boot after a clone
So I did the thing:
git clone https://github.com/matthijskooijman/rpi-clone.git
cd rpi-clone
git checkout keep-fs-labels

And finally ended with a sudo ./rpi-clone sda.
Booted disk: mmcblk0 127.9GB               Destination disk: sda 500.1GB
---------------------------------------------------------------------------
Part               Size    FS     Label           Part   Size    FS     Label
1 /boot/firmware   512.0M  fat32  bootfs          1      512.0M  fat32  --
2 root             118.6G  ext4   rootfs          2      465.3G  ext4   --
---------------------------------------------------------------------------
== SYNC mmcblk0 file systems to sda ==
/boot/firmware        (63.0M used)   : SYNC to sda1 (512.0M size)
/                     (102.9G used)  : SYNC to sda2 (465.3G size)
---------------------------------------------------------------------------
Run setup script       : no.
Verbose mode           : no.
-----------------------:

Ok to proceed with the clone?  (yes/no): yes

Syncing file systems (can take a long time)
Syncing mounted partitions:
     e2label /dev/sda2 rootfs
  Mounting /dev/sda2 on /mnt/clone
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
  => rsync // /mnt/clone with-root-excludes ...
     fatlabel /dev/sda1 bootfs
fatlabel: warning - lowercase labels might not work properly on some systems
  Mounting /dev/sda1 on /mnt/clone/boot/firmware
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
  => rsync /boot/firmware/ /mnt/clone/boot/firmware  ...

Editing /mnt/clone/boot/firmware/cmdline.txt PARTUUID to use 41300809
Editing /mnt/clone/etc/fstab PARTUUID to use 41300809
===============================
Done with clone to /dev/sda
   Start - 21:41:31    End - 21:41:59    Elapsed Time - 0:28

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

Hit Enter when ready to unmount the /dev/sda partitions ...
  unmounting /mnt/clone/boot/firmware
  unmounting /mnt/clone
===============================

I didn't really think about rsync should be able to get things sorted, without having to copy everything over again.
It managed to fix it in a few seconds, and everyting worked as expected. Thanks!

Also, here's the result of the first clone, with the good old branch:
sudo rpi-clone sda -f

Booted disk: mmcblk0 127.9GB               Destination disk: sda 500.1GB
---------------------------------------------------------------------------
Part               Size    FS     Label           Part   Size    FS     Label
1 /boot/firmware   512.0M  fat32  --              1      100.0M  fat32  --
2 root             118.6G  ext4   rootfs          2       16.0M  --     --
                                                  3      465.1G  ntfs   --
                                                  4      508.0M  ntfs   --
---------------------------------------------------------------------------
== Initialize: IMAGE partition table - forced by option ==
1 /boot/firmware      (63.0M used)   : MKFS  SYNC to sda1
2 root                (102.9G used)  : RESIZE  MKFS  SYNC to sda2
---------------------------------------------------------------------------
Run setup script       : no.
Verbose mode           : no.
-----------------------:
** WARNING **          : All destination disk sda data will be overwritten!
-----------------------:

Initialize and clone to the destination disk sda?  (yes/no): yes
Optional destination ext type file system label (16 chars max):

Initializing
  Imaging past partition 1 start.
  => dd if=/dev/mmcblk0 of=/dev/sda bs=1M count=8 ...
  Resizing destination disk last partition ...
    Resize success.
  Changing destination Disk ID ...
  => mkfs -t vfat -F 32  /dev/sda1 ...
  => mkfs -t ext4  /dev/sda2 ...

Syncing file systems (can take a long time)
Syncing mounted partitions:
  Mounting /dev/sda2 on /mnt/clone
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
  => rsync // /mnt/clone with-root-excludes ...

  Mounting /dev/sda1 on /mnt/clone/boot/firmware
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
  => rsync /boot/firmware/ /mnt/clone/boot/firmware  ...

Editing /mnt/clone/etc/fstab PARTUUID to use 41300809
===============================
Done with clone to /dev/sda
   Start - 18:21:37    End - 19:08:11    Elapsed Time - 46:34

Cloned partitions are mounted on /mnt/clone for inspection or customizing.

Hit Enter when ready to unmount the /dev/sda partitions ...  unmounting /mnt/clone/boot/firmware
  unmounting /mnt/clone
===============================

Thank you for making this! (Also mentioned in the old branch, where I noticed it first: https://github.com/billw2/rpi-clone/issues/122)


Pin versions of fftw, gdal, zlib and curl at runtime

Similar to #232 but for the GMT devel builds. Addresses the Windows GMT Dev Tests failures mentioned in https://github.com/GenericMappingTools/pygmt/issues/2215.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Actually, I'm not sure if the changes can work as expected.
If gmt is pinned to GDAL >=3.6.0, the following command should report an error:
mamba create --name pygmt python=3.10 numpy pandas xarray netcdf4 packaging gmt geopandas

instead of creating a broken environment.

Actually, I'm not sure if the changes can work as expected.
If gmt is pinned to GDAL >=3.6.0, the following command should report an error:
mamba create --name pygmt python=3.10 numpy pandas xarray netcdf4 packaging gmt geopandas

instead of creating a broken environment.

Erm, that command is for the main branch GMT 6.4.0. This PR is for the devel branch GMT 6.5.0.devXXX.
Also, that GMT 6.4.0 installation runs fine right now, but it is currently pulling in GDAL 3.5.3, and if you do:
mamba activate pygmt
gmt --version

an error like gmt: error while loading shared libraries: libgdal.so.32: cannot open shared object file: No such file or directory will be reported due to GDAL version mismatch (GMT on conda-forge built with GDAL 3.6 doesn't work with GDAL 3.5.3 installation). Which you mentioned at https://github.com/GenericMappingTools/pygmt/issues/2215#issuecomment-1330201807 is an issue with fiona.

Also, that GMT 6.4.0 installation runs fine right now, but it is currently pulling in GDAL 3.5.3, and if you do:
mamba activate pygmt
gmt --version

an error like gmt: error while loading shared libraries: libgdal.so.32: cannot open shared object file: No such file or directory will be reported due to GDAL version mismatch (GMT on conda-forge built with GDAL 3.6 doesn't work with GDAL 3.5.3 installation).

I thought it should fail to create the environment because GMT requires GDAL >=3.6 but Fiona is incompatible with GDAL 3.6.

I thought it should fail to create the environment because GMT requires GDAL >=3.6 but Fiona is incompatible with GDAL 3.6.

If you're talking about GMT 6.4.0, the build 5 at osx-64/gmt-6.4.0-h46ce199_5.conda doesn't set GDAL>= 3.6.

The build number 6 osx-64/gmt-6.4.0-h46ce199_6.conda has the correct GDAL >=3.6 pinings

So for Python 3.10, the mamba solver is actually installing build 5 to satisfy the fiona dependency instead of build 6. Build 6 can't be installed with fiona yet.

Ok, and still need to do the same for the v5.x branch. Do you want to do it?


Advanced Portal Gun Persistent Portal

Describe the feature you'd like to have added
Hi! I left a comment with a similar suggestion but figured this is probably the better place for it.
I was wondering what you thought of an extra ability on the advanced portal gun to make persistent portals, like the regular portal gun does.
I don't think the current functionality of the advanced portal gun should be changed much so it would need some form of limiter, say one deployment at a time or a fluid and power cost per tick while the portal is kept open, or even both.
The persistent feature could be one of two things, either a left or shift left click with the gun will open a portal to the selected favourite, and close again when another persistent portal is opened, or a regular portal to the same favourite is opened. This would allow you quick back and forth access to a location say if you're setting something up, but won't need to regularly access it once it's setup.
The other way it could work would be an extra slot in the favourites wheel to function as the regular portal gun, allowing you to left and right click to place each side of the portal.
I guess this is almost an extension of the shift right click to return as it would allow you to keep a portal live for the duration you need it, rather than continuously opening a new portal back and forth.
Potentially this could be even more advanced allowing you to set a timeout for the portals in the same way you can set pickup delays etc in the regular just dire machines, but I worry that may be a bit too advanced and over powered, so perhaps would be better suited for a super advanced portal gun.
Additional information
No response

I'm not sure I want to add this - but I do want a block form of the portals, that you can build and have be persistent.


Fix TSDataSampler Slicing Bug #1716

Title: Fix TSDataSampler Slicing Bug #1716

Description
I have optimized the mechanism for reading data from data_arr in the __getitem__ method:

In most cases, maintain high performance of slicing and preserve the original logic.
For the issue raised by #1716, I adopted a straightforward approach to circumvent the problem: set self.nan_idx to len(self.data_arr) - 1 instead of -1.

Motivation and Context

Related Issue Link
The __getitem__ function of TSDataSampler generally operates without issue, yet in certain scenarios, particularly when step_len is significant and nan must be added prior to start, it may inadvertently sample an empty list, which is erroneous.
Consider the following code snippet as an example:
import numpy as np
import pandas as pd
from qlib.data.dataset import TSDataSampler

datetimes = [
    '2000-01-31', '2000-02-29', '2000-03-31', '2000-04-30', '2000-05-31'
]
instruments = ['000001', '000002', '000003', '000004', '000005']
index = pd.MultiIndex.from_product([pd.to_datetime(datetimes), instruments],
                                   names=['datetime', 'instrument'])
data = np.random.randn(len(datetimes) * len(instruments))
test_df = pd.DataFrame(data=data, index=index, columns=['ret'])
dataset = TSDataSampler(test_df, datetimes[0], datetimes[-1], step_len=2)
print(dataset[0])

The expected outcome should be an array with nan as the initial element followed by numerical values.
However, the actual result is an empty list, as depicted in the following image:

Mechanism of the Error
How did this issue arise? It stems from the fact that the dataframe data has been stored in an ndarray (variable name: data_arr) in the order of 'instrument, time', and thus a set of indicies is generated during the fetch. The logical error occurs when step_len is large, and the count from the current processing position back to start requires nan supplementation (as shown in the following image):

These nan values are then converted to -1 during subsequent processing (as shown in the following image) because self.nan_idx is hardcoded as -1:

Therefore, the error occurs when there are several -1s at the beginning, causing the slice to become [-1, index of the last value to be fetched]. In cases requiring padding, this index is typically small, leading to the retrieval of an empty list, which is the error reported in the issue.

My Modification Approach
Since the error always occurs at the beginning with nan, the indicies[0] must be self.nan_idx, which is hardcoded to -1. For this scenario, it causes issues with the retrieved slices. After examining, I found that self.nan_idx is only called once in this context. Therefore, following the original author's intention, I changed self.nan_idx to len(self.data_arr) - 1. This solution not only addresses the problem but also avoids reducing code readability.
How Has This Been Tested?

[x] Passed the test by running: pytest qlib/tests/test_all_pipeline.py under the upper directory of qlib.
[x] If you are adding a new feature, tested on your own test scripts.

My test scripts are located in tests/data_mid_layer_tests/test_dataset.py.
TestTSDataSampler includes two test contents:

Reproducing and testing the resolution of #1716 (i.e., partial sampling results in an empty list).
An additional test case should be considered: if the first element does not require nan padding and is directly fetched, the test result should be the direct retrieval of the first value.

Screenshots of Test Results (if appropriate):

Pipeline test:

Your own tests:

Types of changes

[x] Bug fix
[ ] New feature
[ ] Documentation update

@microsoft-github-policy-service agree

Could you please fix the CI errors?
@YeewahChan

Could you please fix the CI errors? @YeewahChan

The CI errors were due to pylint formatting issues, but I've fixed them now.

Could you please fix the CI errors? @YeewahChan

The CI errors were due to pylint formatting issues, but I've fixed them now.

Thanks for your great efforts!


Roll Plugins from 4407b5a86650 to 5c1c0c0bd024 (1 revision)

https://github.com/flutter/plugins/compare/4407b5a86650...5c1c0c0bd024
2021-04-27<EMAIL_ADDRESS>[camera] android-rework part 2: Android auto focus feature (flutter/plugins#3796)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


IamClient.getAccountPasswordPolicy deserialization error

Describe the bug
Although aws iam get-account-password-policy works as expected, calls to IamClient.getAccountPasswordPolicy() are throwing a deserialization error. There is a password policy set for this account, and a call made to IamClient.updateAccountPasswordPolicy()  immediately before calling getAccountPasswordPolicy() works as expected.
Expected Behavior
The account's password policy should be getting returned with no exception thrown.
Current Behavior
Calls to the function shown above throw the exception found in this log output:
2022-10-10T14:03:06-0400 info IamClient : [Logging] Request: POST https:443
 Path: /
 X-Amz-Date: 20221010T180306Z,
User-Agent: aws-sdk-swift/1.0 api/iam/1.0 os/linux lang/swift/5.6,
Authorization: AWS4-HMAC-SHA256 Credential=AKIAYAXAUTGDQK3VE3SQ/20221010/us-east-1/iam/aws4_request, SignedHeaders=content-type;host;x-amz-date;x-amz-user-agent, Signature=2427011950d9add0c49a9fec86aa066408ea203672f9d214f41a5fc17392efb9,
Host: iam.amazonaws.com,
Content-Type: application/x-www-form-urlencoded,
x-amz-user-agent: aws-sdk-swift/1.0
 Optional([])
2022-10-10T14:03:06-0400 info SerialExecutor : [Logging] Creating connection pool for Optional("https://iam.amazonaws.com/?")with max connections: 50
2022-10-10T14:03:06-0400 info CRTClientEngine : [Logging] Connection was acquired to: Optional("https://iam.amazonaws.com/?")
2022-10-10T14:03:06-0400 info CRTClientEngine : [Logging] headers were received
2022-10-10T14:03:06-0400 info CRTClientEngine : [Logging] headers were received
2022-10-10T14:03:06-0400 info CRTClientEngine : [Logging] headers were received
2022-10-10T14:03:06-0400 info CRTClientEngine : [Logging] headers were received
2022-10-10T14:03:06-0400 info CRTClientEngine : [Logging] header block is done
2022-10-10T14:03:06-0400 info CRTClientEngine : [Logging] stream completed
2022-10-10T14:03:06-0400 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://iam.amazonaws.com/?") is closing
Error: client(ClientRuntime.ClientError.retryError(Swift.DecodingError.dataCorrupted(Swift.DecodingError.Context(codingPath: [], debugDescription: "The given data could not be parsed into XML.", underlyingError: nil))), nil)

Reproduction Steps
The code throwing the exception follows:
    public func getAccountPasswordPolicy() async throws -> IamClientTypes.PasswordPolicy {
        let input = GetAccountPasswordPolicyInput()
        do {
            let output = try await client.getAccountPasswordPolicy(input: input)

            guard let policy = output.passwordPolicy else {
                throw ServiceHandlerError.noSuchPolicy
            }
            return policy
        } catch {
            throw error
        }
    }

Possible Solution
No response
Additional Information/Context
The same problem also occurs with IamClient.listSAMLProviders().
AWS SWIFT SDK version used
0.3.0
Compiler and Version used
Swift version 5.6.3 (swift-5.6.3-RELEASE)
Operating System and version
Amazon LInux 2

There's a slim chance this is happening when the response from the server is empty, though the use cases I'm seeing it with shouldn't be returning empty results. Just wanted to throw this out there in case I'm wrong.

Tried to reproduce with below snippet without calling updateAccountPasswordPolicy. I set the passport policy directly from console
import AWSIAM
import ClientRuntime

@main
public struct iam {
    public static func main() async {
        SDKLoggingSystem.initialize(logLevel: .debug)
        try! await getAccountPasswordPolicy()

    }

    public static func getAccountPasswordPolicy() async throws {
        let client = try IAMClient(region: "us-west-2")
        let input = GetAccountPasswordPolicyInput()
        let output = try await client.getAccountPasswordPolicy(input: input)
        print(output)
    }
}

o/p
GetAccountPasswordPolicyOutputResponse(passwordPolicy: Optional(AWSIAM.IAMClientTypes.PasswordPolicy(allowUsersToChangePassword: true, expirePasswords: true, hardExpiry: Optional(true), maxPasswordAge: Optional(90), minimumPasswordLength: Optional(8), passwordReusePrevention: Optional(5), requireLowercaseCharacters: true, requireNumbers: true, requireSymbols: true, requireUppercaseCharacters: true)))

It seems working as expected, likely fixed by serde improvements done recently.
@shepazon could try with latest version of SDK?


Xenium Ranger <IP_ADDRESS> after Cellpose resegmentation - "ValueError: A linearring requires at least 4 coordinates."

After segmentation with cellpose, I ran Xenium Ranger <IP_ADDRESS>
xeniumranger import-segmentation --id=my_ID \                                  --xenium-bundle=$DIR/outs \                                  --nuclei=$DIR/outs/mask_nuclei.ome_cp_masks.tif \                                  --cells=$DIR/outs/mask_cells.ome_cp_masks.tif
When I try to read the output folder with spatialdata_io (0.1.7.dev5+g82ff327), spatialdata (0.2.7.dev7+gd746485)
sdata = spatialdata_io.xenium(dir)
I get this error:
"ValueError: A linearring requires at least 4 coordinates."

Is there a temporary workaround to manually create the SpatialData data framework from Xenium ranger output? (I mean a tutorial/notebook/...)

Nobody have an idea about how to resolve this issue?
Does anybody knows how to download the previous working version of Xenium Ranger (v<IP_ADDRESS>)?
Or any tutorial to manually create the spatial data object from Xenium Ranger output?

After updating to Xenium Ranger v3.1, still not working.
Nobody has any idea how to resolve this issue?
Traceback (most recent call last):   File "./Read_Write_zarr.py", line 11, in <module>     sdata = spatialdata_io.xenium(dir)   File "./lib/python3.10/site-packages/spatialdata_io/_utils.py", line 46, in wrapper     return f(*args, **kwargs)   File "./lib/python3.10/site-packages/spatialdata_io/readers/xenium.py", line 232, in xenium     polygons["cell_boundaries"] = _get_polygons(   File "./lib/python3.10/site-packages/spatialdata_io/readers/xenium.py", line 349, in _get_polygons     out = Parallel(n_jobs=n_jobs)(   File "./lib/python3.10/site-packages/joblib/parallel.py", line 1918, in __call__     return output if self.return_generator else list(output)   File "./lib/python3.10/site-packages/joblib/parallel.py", line 1847, in _get_sequential_output     res = func(*args, **kwargs)   File "./lib/python3.10/site-packages/spatialdata_io/readers/xenium.py", line 341, in _poly     return Polygon(arr[:-1])   File "./lib/python3.10/site-packages/shapely/geometry/polygon.py", line 230, in __new__     shell = LinearRing(shell)   File "./lib/python3.10/site-packages/shapely/geometry/polygon.py", line 104, in __new__     geom = shapely.linearrings(coordinates)   File "./lib/python3.10/site-packages/shapely/decorators.py", line 77, in wrapped     return func(*args, **kwargs)   File "./lib/python3.10/site-packages/shapely/creation.py", line 173, in linearrings     return lib.linearrings(coords, out=out, **kwargs) ValueError: A linearring requires at least 4 coordinates.


YQ-2824: Bring minimal schema inference to cloned clickhouse code

Changelog entry
Bring minimal necessary code from ClickHouse for schema inference
Changelog category

Not for changelog (changelog entry is not required)

Additional information

Generally code is taken from https://github.com/ClickHouse/ClickHouse/pull/32455
It uses evaluation of constant expressions for inferring types, which is not present in our code and in ClickHouse was later replaced with more explicit inference by hand. The latter seemed as bringing less code, thus was used instead

Больше не актуально


re-run firefox tests - hoping to reproduce the occasional geckgodrive…

…r failure

Found a workaround, add in master branch.