just: 1.11.0 -> 1.12.0

just: 1.11.0 -> 1.12.0
just: add adamcstephens as maintainer

https://github.com/casey/just/blob/1.12.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 210527 run on x86_64-linux 1

3 packages built:

dogdns
just
kabeljau

Result of nixpkgs-review pr 210527 run on aarch64-linux 1

3 packages failed to build:

dogdns
just
kabeljau

I'm going to convert this to a draft. This tag hasn't been converted to a release yet, and the upstream aarch64 build failed for a different reason.
https://github.com/casey/just/actions/runs/3908675689/jobs/6679021229
I'll keep an eye on what happens with this release/tag.

Upstream CI has now passed and the release has been cut: https://github.com/casey/just/releases/tag/1.11.0
My rebuild on actual aarch64-linux passed, so I'm considering this ready again.

Result of nixpkgs-review pr 210527 run on x86_64-linux 1

3 packages failed to build:

dogdns
just
kabeljau

Upstream appears to be having some CI issues, so not sure what's going on here.

Sorry everyone if you see this, I apparently completely messed up this rebase and missed it until after push.


Add workflow to build and publish AMIs

@guicaulada could you please add some description in this PR so it's easier for the reviewer to follow?

@dsotirakis I have rebased the PR since it had a lot of commits I created to test changes on the workflow.


mpflutter 是不是不支持dart 3.0.5？

我的flutter和dart版本：
PS F:\application\IntelliJIDEAProjects\awesome_project\awesome_project> ./mpflutter --version
F:\application\IntelliJIDEAProjects\awesome_project\awesome_project>set PUB_HOSTED_URL=https://pub.mpflutter.com
F:\application\IntelliJIDEAProjects\awesome_project\awesome_project>flutter --version
Flutter 3.10.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 796c8ef792 (5 weeks ago) • 2023-06-13 15:51:02 -0700
Engine • revision 45f6e00911
Tools • Dart 3.0.5 • DevTools 2.23.1
执行 ./mpflutter packages get 报错内容：
PS F:\application\IntelliJIDEAProjects\awesome_project\awesome_project> ./mpflutter packages get
F:\application\IntelliJIDEAProjects\awesome_project\awesome_project>set PUB_HOSTED_URL=https://pub.mpflutter.com
F:\application\IntelliJIDEAProjects\awesome_project\awesome_project>flutter packages get
Flutter assets will be downloaded from https://storage.flutter-io.cn. Make sure you trust this source!
Resolving dependencies... (1.2s)
The current Dart SDK version is 3.0.5.
Because mpcore 1.2.0 depends on json_patch >=1.0.1 <3.0.0 which doesn't support null safety, mpcore 1.2.0 is forbidden.
So, because mpflutter_template depends on mpcore 1.2.0, version solving failed.
The lower bound of "sdk: '>=2.0.0 <3.0.0'" must be 2.12.0 or higher to enable null safety.
For details, see https://dart.dev/null-safety

+1

+1

这个啥时候能解决一下。。dart 3多了蛮多好用的特性

dart 3.1.0发布了，要不直接支持一下对应的flutter版本吧😁

+1

已支持 https://mpflutter.com/zh/docs/dart3-support

希望作者把gitee也更新一下


Tr 13 add new hosted field for card holder name

The Card Holder Name from HF is not sent in the requests.


Gulpfile no sass

Not a biggie, but I think the gulpfile is missing the sass compiler? Or was this left out for a reason?

The SASS reboot was a user made thing and it never got included in the Gulpfile. The v4-dev branch uses Bootstrap 4 and has both in the Gulpfile however.


#1: add support for horses in database initialization

First update.

/paulo - can you please review this pull request?

/paulo - can you check now?


[KYUUBI #2085][FOLLOWUP] Fix the wrong path of module:hive

Why are the changes needed?

Fix the wrong path of module:hive
How was this patch tested?

https://github.com/cfmcgrady/incubator-kyuubi/pull/12

@yaooqinn @pan3793

thanks, merging to master


Recipient of connection request has no way to get info about requester

As a user of a business partner that get added as a partner I want to know who added me

If I add a new business partner which has Aries support, then an Aries connection is created between the two Agents.
I know the public DID of the business partner and can retrieve the public profile. However, the connection request that my agent sends to the partner does not contain my public DID but a freshly generated peer DID. Hence, the business partner does not have any information about me. How do we handle that?
Options:

Add functionality to ACA-PY to allow connections based on public DIDs. I think that should be not too hard.
Hack: Put public DID as the agent label (this is what we DID in the first demonstrator), since the agent label is communicated in a connection request.
Add functionality to ACA-PY to include public profile endpoint in the connection request.
Hack: Automatically send a basic message with the public DID after connection is established
Automatically request the public did or public profile endpoint as a self-attested value in a proof request

Started implementing option 1. See Issue and Code


sudo: 1.9.5p1 → 1.9.5p2

Motivation for this change
Sudo reported a critical security vulnerability today and the fix is included in sudo 1.9.5p2. This PR updates the package and adds
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test sudo

@GrahamcOfBorg test sudo

Backported in 93c2261684ea8c65606d7167b5d52b8da7d7778a.

Backported in 93c2261684ea8c65606d7167b5d52b8da7d7778a.

Thanks for the quick fix and backport.

Thanks for the quick fix and backport.


Merge NodeType and ServerType

However, my second thought is that it's not reasonable to do this, because the necessity to carefully follow two different JSON strings mappings that are already historically used ("indexer-executor" - "peon" and "realtime" - "middleManager") will load only to increase in complexity and reduce the code safety.


Little Help

when running the peatio-trading ui, i got this page as if the styles were missing, that is the css. was it my nginx because i had difficult time configuring ssl for nginx. please help

what am i missing? think think

solved

how you solved?  i have the same problem


Create codeql-analysis.yml

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Think we need a rebase on this guy

@lwr20 forgot about this one - what else do we need to get this merged?

@fasaxc what do you think about this bit of code? https://github.com/projectcalico/calico/blame/ded8136c9de1a9135369f3ab5dbebff9b44a0b4e/felix/fv/metrics/metrics.go#L74-L77
The scanner is complaining about our use if InsecureSkipVerify - the comment seems to suggest that we verify the cert ourselves? Should we ignore this (and the other instance) or fix up the code to not need it?

@lwr20 I think this is ready to go in, but it probably needs:

Rebase on master
run make generate to update generated files.

Rebased and ran make generate

@lwr20 for some reason it's still complaining about some generated files:
The following files are dirty00:00
 manifests/calico-bpf.yaml               |   142 +-00:00
 manifests/calico-etcd.yaml              |   107 +-00:00
 manifests/calico-policy-only.yaml       |   359 +-00:00
 manifests/calico-typha.yaml             |   353 +-00:00
 manifests/calico-vxlan.yaml             |   142 +-00:00
 manifests/calico.yaml                   |   142 +-00:00
 manifests/canal-etcd.yaml               |   175 +-00:00
 manifests/canal.yaml                    |   144 +-00:00
 manifests/crds.yaml                     |  3977 +++++++00:00
 manifests/flannel-migration/calico.yaml |   142 +-00:00
 manifests/tigera-operator.yaml          | 18079 ++++++++++++++++++++++++++++++00:00
 node/tests/k8st/infra/calico-kdd.yaml   |   110 +-

@caseydavenport @lwr20 Can we merge this one?

@Behnam-Shobiri No, we can't merge this, it fails CI.  I think some of the "fixes" I attempted to put in are wrong.  I don't really have time to work on this right now, please feel free to take over this PR or do your own, better version of it


No frames have been received issue in Frigate

The issue is that sometimes, frigate will respond with "No frames have been received". This can change upon next refresh - of the total of 4 cameras this would happen to any of them at some time (sometimes multiple at once).
Screenshot:

I have seen quite a few spikes in CPU usage but I am unsure whether this is the issue.

Also the streams seem to run not very smooth, compared to the Reolink app (where they run just fine).
I am using version 0.13.2-6476F8A of the add on, including the HACS integration on a QNAP TS-364 in Home Assistant 2024.3.0 (HA OS version in a VM). The VM has 8 GB of RAM and 4 CPU cores.
I also have 4 Reolink P1 Pro all connected via Wifi.
Configuration

mqtt:
  host: localhost
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: ****
  password: ****
  stats_interval: 300

record:
  enabled: True
  retain:
    days: 1
    mode: motion

ffmpeg:
  global_args: -hide_banner
  hwaccel_args: []
  input_args: preset-rtsp-generic
  output_args:
    record: preset-record-generic-audio-copy

database:
  path: /config/frigate.db

rtmp:
  enabled: false

cameras:
  Kamera-01-Wohnzimmer:
    ffmpeg:
      inputs:
        - path: rtsp://frigate:****@<IP_ADDRESS>:554/h264Preview_01_main
          roles:
            - record
  Kamera-04-Flur:
    ffmpeg:
      inputs:
        - path: rtsp://frigate:****@<IP_ADDRESS>:554/h264Preview_01_main
          roles:
            - record
  Kamera-03:
    ffmpeg:
      inputs:
        - path: rtsp://admin:****@<IP_ADDRESS>:554/h264Preview_01_main
          roles:
            - record
  Kamera-02:
    ffmpeg:
      inputs:
        - path: rtsp://admin:****@<IP_ADDRESS>:554/h264Preview_01_main
          roles:
            - record

Debug log

s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
2024-03-10 17:38:28.023811526  [INFO] Preparing Frigate...
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
2024-03-10 17:38:28.073116198  [INFO] Starting NGINX...
s6-rc: info: service legacy-services successfully started
2024-03-10 17:38:28.563511077  [INFO] Preparing new go2rtc config...
2024-03-10 17:38:28.571052880  [INFO] Starting Frigate...
2024-03-10 17:38:28.793645963  [INFO] Got IP address from supervisor: <IP_ADDRESS>
2024-03-10 17:38:28.858570931  [INFO] Got WebRTC port from supervisor: 8555
2024-03-10 17:38:30.681424420  [INFO] Starting go2rtc...
2024-03-10 17:38:30.834728907  18:38:30.834 INF go2rtc version 1.8.4 linux/amd64
2024-03-10 17:38:30.836841665  18:38:30.836 INF [api] listen addr=:1984
2024-03-10 17:38:30.838241784  18:38:30.838 INF [rtsp] listen addr=:8554
2024-03-10 17:38:30.839586218  18:38:30.839 INF [webrtc] listen addr=:8555
2024-03-10 17:38:35.568869862  [2024-03-10 18:38:35] frigate.app                    INFO    : Starting Frigate (0.13.2-6476f8a)
2024-03-10 17:38:35.568875024  [2024-03-10 18:38:35] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-03-10 17:38:38.039463208  [INFO] Starting go2rtc healthcheck service...
2024-03-10 17:38:42.167070658  2024/03/10 18:38:42 [error] 145#145: *1 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /api/version HTTP/1.1", upstream: "http://<IP_ADDRESS>:5001version", host: "<IP_ADDRESS>:5000"
2024-03-10 17:38:44.346145825  [2024-03-10 18:38:44] peewee_migrate.logs            INFO    : Starting migrations
2024-03-10 17:38:44.386148910  [2024-03-10 18:38:44] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-03-10 17:38:44.399605782  [2024-03-10 18:38:44] frigate.app                    INFO    : Recording process started: 331
2024-03-10 17:38:44.407848972  [2024-03-10 18:38:44] frigate.app                    INFO    : go2rtc process pid: 93
2024-03-10 17:38:44.477122701  [2024-03-10 18:38:44] frigate.app                    INFO    : Output process started: 342
2024-03-10 17:38:44.486489302  [2024-03-10 18:38:44] detector.cpu                   INFO    : Starting detection process: 341
2024-03-10 17:38:44.536222422  [2024-03-10 18:38:44] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2024-03-10 17:38:44.779478108  2024/03/10 18:38:44 [error] 146#146: *3 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://<IP_ADDRESS>:5001stats", host: "ccab4aaf-frigate:5000"
2024-03-10 17:38:45.397035965  [2024-03-10 18:38:45] frigate.app                    INFO    : Camera processor started for Kamera-01-Wohnzimmer: 363
2024-03-10 17:38:45.431165267  [2024-03-10 18:38:45] frigate.app                    INFO    : Camera processor started for Kamera-04-Flur: 364
2024-03-10 17:38:45.441047690  [2024-03-10 18:38:45] frigate.app                    INFO    : Camera processor started for Kamera-03: 365
2024-03-10 17:38:45.466632112  [2024-03-10 18:38:45] frigate.app                    INFO    : Camera processor started for Kamera-02: 366
2024-03-10 17:38:45.496404599  [2024-03-10 18:38:45] frigate.app                    INFO    : Capture process started for Kamera-01-Wohnzimmer: 371
2024-03-10 17:38:45.532184307  [2024-03-10 18:38:45] frigate.app                    INFO    : Capture process started for Kamera-04-Flur: 374
2024-03-10 17:38:45.537127256  [2024-03-10 18:38:45] frigate.app                    INFO    : Capture process started for Kamera-03: 377
2024-03-10 17:38:45.563543217  [2024-03-10 18:38:45] frigate.app                    INFO    : Capture process started for Kamera-02: 382
2024-03-10 17:39:05.315883486  [2024-03-10 18:39:05] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-02/all: client is not connected
2024-03-10 17:39:05.318469734  [2024-03-10 18:39:05] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-02/motion: client is not connected
2024-03-10 17:39:06.993442835  [2024-03-10 18:39:06] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-04-Flur/all: client is not connected
2024-03-10 17:39:06.995455405  [2024-03-10 18:39:06] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-04-Flur/motion: client is not connected
2024-03-10 17:39:09.206223774  [2024-03-10 18:39:09] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-01-Wohnzimmer/all: client is not connected
2024-03-10 17:39:09.206228992  [2024-03-10 18:39:09] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-01-Wohnzimmer/motion: client is not connected
2024-03-10 17:39:09.789451027  [2024-03-10 18:39:09] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-03/all: client is not connected
2024-03-10 17:39:09.789456638  [2024-03-10 18:39:09] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-03/motion: client is not connected
2024-03-10 17:39:26.343231843  <IP_ADDRESS> - - [10/Mar/2024:18:39:26 +0100] "GET /api/config HTTP/1.1" 200 16677 "-" "HomeAssistant/2024.3.0 aiohttp/3.9.3 Python/3.12" "-"
2024-03-10 17:40:05.251969795  <IP_ADDRESS> - - [10/Mar/2024:18:40:05 +0100] "GET // HTTP/1.1" 200 6694 "http://homeassistant.local:8123/ccab4aaf_frigate" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:05.413801110  <IP_ADDRESS> - - [10/Mar/2024:18:40:05 +0100] "GET /api/config HTTP/1.1" 200 16677 "http://homeassistant.local:8123/api/hassio_ingress/SfvDs2xLv3NW18Z6kHjC96UWZH7k-r_jHc05bS6Gy8M//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:05.762176742  <IP_ADDRESS> - - [10/Mar/2024:18:40:05 +0100] "GET /api/Kamera-01-Wohnzimmer/latest.jpg?h=100 HTTP/1.1" 200 1815 "http://homeassistant.local:8123/api/hassio_ingress/SfvDs2xLv3NW18Z6kHjC96UWZH7k-r_jHc05bS6Gy8M//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:06.096788685  <IP_ADDRESS> - - [10/Mar/2024:18:40:06 +0100] "GET /api/Kamera-03/latest.jpg?h=371 HTTP/1.1" 200 10116 "http://homeassistant.local:8123/api/hassio_ingress/SfvDs2xLv3NW18Z6kHjC96UWZH7k-r_jHc05bS6Gy8M//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:06.105686750  <IP_ADDRESS> - - [10/Mar/2024:18:40:06 +0100] "GET /api/Kamera-04-Flur/latest.jpg?h=371 HTTP/1.1" 200 20873 "http://homeassistant.local:8123/api/hassio_ingress/SfvDs2xLv3NW18Z6kHjC96UWZH7k-r_jHc05bS6Gy8M//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:06.263442094  <IP_ADDRESS> - - [10/Mar/2024:18:40:06 +0100] "GET /api/Kamera-01-Wohnzimmer/latest.jpg?h=371 HTTP/1.1" 200 10116 "http://homeassistant.local:8123/api/hassio_ingress/SfvDs2xLv3NW18Z6kHjC96UWZH7k-r_jHc05bS6Gy8M//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:06.369424984  <IP_ADDRESS> - - [10/Mar/2024:18:40:06 +0100] "GET /api/Kamera-02/latest.jpg?h=371 HTTP/1.1" 200 10116 "http://homeassistant.local:8123/api/hassio_ingress/SfvDs2xLv3NW18Z6kHjC96UWZH7k-r_jHc05bS6Gy8M//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:08.108712753  <IP_ADDRESS> - - [10/Mar/2024:18:40:08 +0100] "GET /api/config HTTP/1.1" 200 16677 "http://homeassistant.local:8123/api/hassio_ingress/SfvDs2xLv3NW18Z6kHjC96UWZH7k-r_jHc05bS6Gy8M//" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:09.164691995  <IP_ADDRESS> - - [10/Mar/2024:18:40:09 +0100] "GET /ws HTTP/1.1" 101 4 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "<IP_ADDRESS>, <IP_ADDRESS>"
2024-03-10 17:40:15.759629206  [2024-03-10 18:40:15] frigate.comms.mqtt             ERROR   : Unable to publish to events: client is not connected
2024-03-10 17:40:15.846505050  [2024-03-10 18:40:15] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-03/person/snapshot: client is not connected
2024-03-10 17:40:15.847557127  [2024-03-10 18:40:15] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-03/person: client is not connected
2024-03-10 17:40:15.847946169  [2024-03-10 18:40:15] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-03/all: client is not connected
2024-03-10 17:40:19.568406392  [2024-03-10 18:40:19] frigate.record.maintainer      WARNING : Unable to keep up with recording segments in cache for Kamera-02. Keeping the 6 most recent segments out of 7 and discarding the rest...
2024-03-10 17:40:26.047007594  [2024-03-10 18:40:26] frigate.comms.mqtt             ERROR   : Unable to publish to events: client is not connected
2024-03-10 17:40:26.085662180  [2024-03-10 18:40:26] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-02/person/snapshot: client is not connected
2024-03-10 17:40:26.085702646  [2024-03-10 18:40:26] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-02/person: client is not connected
2024-03-10 17:40:26.085704771  [2024-03-10 18:40:26] frigate.comms.mqtt             ERROR   : Unable to publish to Kamera-02/all: client is not connected
2024-03-10 17:40:29.553826451  [2024-03-10 18:40:29] frigate.record.maintainer      WARNING : Unable to keep up with recording segments in cache for Kamera-03. Keeping the 6 most recent segments out of 7 and discarding the rest...
2024-03-10 17:40:29.555255470  [2024-03-10 18:40:29] frigate.record.maintainer      WARNING : Unable to keep up with recording segments in cache for Kamera-02. Keeping the 6 most recent segments out of 7 and discarding the rest...
2024-03-10 17:40:29.783193666  [2024-03-10 18:40:29] frigate.comms.mqtt             ERROR   : Unable to publish to events: client is not connected
2024-03-10 17:40:39.587061006  [2024-03-10 18:40:39] frigate.record.maintainer      WARNING : Unable to keep up with recording segments in cache for Kamera-03. Keeping the 6 most recent segments out of 7 and discarding the rest...

This isn't an issue with the integration, should be reported on the frigate repo


Run doesn't run

Environment
Windows build number: win 10 ver 1909
PowerToys version:  0.18.1
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce
Perhaps I simply don't understand how it is  supposed to run. I have my data on the D drive. so, d:\documents has my documents. etc. - No documents are found. Is there an index? How is it controlled? Without being able to find spreadsheets, or documents it is not as useful as Windows Search.
Expected behavior

Actual behavior

Screenshots

Betting D drive isn’t indexed. We have a tracking bug against this to alert the user

It's issue #2041 which is currently in progress.

I just want to clarify, you can go to Indexing Options in Control Panel and add the D drive to see results in PowerToys Run.
Closing this issue. Please reopen if you're still having problems.


File Uploader

Catalog # 26
Link to Design
Link to Code

Blocked as the status of the design it was set to 'status: refining' by @carrenelloyd

I think @lee-chase and Chloe have been discussing this.  @carrenelloyd what was the reason behind the refining status tag - do you have a link to anything around the refinements underway?


Compiling problem

Describe your problem here.
ehhhh, i'm having this error when trying to compile
(I used google translator sorry lol)

I fixed an error I was getting, but these I couldn't fix :(
(I used google translator :D)
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

use flixel 4.11.0 and flixel addons 2.11.0

can you please send me the code to do this
(Google translator)

haxelib install flixel 4.11.0
haxelib install flixel-addons 2.11.0

still with the same error :(

you have to make sure it is using those versions via
haxelib set flixel 4.11.0
haxelib set flixel-addons 2.11.0

it worked bro, thanks a lot :)

you're welcome :)
btw don't forget to close the issue please

ok


Update package.json

Mixing nodemon and concurrently are also missing

Well, I've saw the the readme defines install them. Closing.


Deprecate startup.sh

Deadline for discussion: 2020-12-16
These are superseded by GOV.UK Docker, which is the official way we
develop GOV.UK apps 1. Having alternative scripts in our repos is
confusing for new developers, and is just another thing we have to
maintain and help people troubleshoot 2.
This is as much a proposal as a PR, so feel free to leave
comments about your own thoughts on this. In particular, I'd
like to know if there are objective reasons why we still need
these scripts for some apps.
If this PR does go in, them I'm also proposing to modify the
startup.sh scripts to print a deprecation notice advising people
to use GOV.UK Docker instead, and warning the scripts may be
removed without notice.

I echo Alex in that converging to a single way of running apps locally makes sense from a maintenance point of view, as well as removing potential points of confusion for new developers.
That being said, I'm currently against this proposal. The start-up scripts are very lightweight in what they do, either pointing to local instances of services that they need or allowing you to point to live (which is what I tend to use them for).
It feels somewhat overkill to need to build the container images for any dependent apps (say if you want to run frontend) when you don't actually require these locally to be able to run the app assuming you point to live. I think that keeping the start-up scripts reduces the barrier to entry to get the apps which contain these scripts running, which is no bad thing.

Thanks @richardTowers and @karlbaker02 for your comments. I need to respond to both of them separately, but there's a common theme that I'd like to give a different perspective on: whether the scripts are lightweight.
I'd actually argue GOV.UK Docker is equally lightweight. Compare:

Steps with GOV.UK Docker:

Install Docker / GOV.UK Docker (works for all development)
Run make for the app (works for all development)
Run govuk-docker-up app-live

Steps with startup.sh:

Install Rbenv and Ruby manually (works for all development)
Install other system packages manually (specific to the repo)
Manually do bundle install
Run ./startup.sh

So while I agree running rails s appears to be lightweight, it's also what's not in those scripts that's the maintenance effort, where people pop up on Slack wondering why something doesn't work on their local machine.

Thanks @richardTowers and @karlbaker02 for your comments. I need to respond to both of them separately, but there's a common theme that I'd like to give a different perspective on: whether the scripts are lightweight.
I'd actually argue GOV.UK Docker is equally lightweight. Compare:

Steps with GOV.UK Docker:

Install Docker / GOV.UK Docker (works for all development)
Run make for the app (works for all development)
Run govuk-docker-up app-live

Steps with startup.sh:

Install Rbenv and Ruby manually (works for all development)
Install other system packages manually (specific to the repo)
Manually do bundle install
Run ./startup.sh

So while I agree running rails s appears to be lightweight, it's also what's not in those scripts that's the maintenance effort, where people pop up on Slack wondering why something doesn't work on their local machine.

I think what I'd say to this is that even though GOV.UK Docker might be fairly lightweight in terms of what it does as you've described above, on balance it's easier, quicker and feels more transparent running said apps with the start-up scripts. The effort to create a new gemset and install gems is minimal, the effort to debug problems with GOV.UK Docker when things go wrong can be more involved. I see that this could be a particular issue for frontend devs, but it's something that would be experienced by all.

For me it's not whether the scripts are lightweight, it's how much abstraction they bring (more abstraction == bad, in this argument, although that's obviously not universal).
In your example:

Run make for the app

Okay, what will this do? Read the Makefile in govuk-docker. Hmmm, my make's not up to scratch... how does the $app-name target appear? There's an APPS variable that does some things with ls and xargs - I guess there's another Makefile in projects/$app/Makefile then. Guess I'll read that one too. government-frontend: bundle-$app content-store router static 🤔  what does this do I wonder? I guess the magic is in the bundle-$app target, so back to the big Makefile. Right, so it's going to clone the app, then run govuk-docker build $app-lite (what does that do? Guess I better read exe/govuk-docker too - okay, it runs docker-compose build $app-lite), then run rbenv install, gem install, and bundle. Gotcha.

Run govuk-docker-up app-live

Same thing here, but less bad. Once you've understood govuk-docker's abstractions, it's obvious that this is going to call docker-compose up.

If we document this as the way, then people will naturally assume "there's obviously a reason for this complexity, so it can't be as simple as just running rails s", when actually it's exactly that simple.
I'm not trying to 💩  on govuk-docker here - there's no question that it solves the problem of running lots of apps in the nicest way we've been able to come up with, but it's a lot more abstraction than startup.sh.

Are we confident that everything can be run in docker? I thought there were some outliers, still. I think possibly email-alert-frontend was easier to get running locally for some frontend changes? Haven't encountered any issues myself on the apps I'm familiar with.
If removing this code might be worth checking whether you need to do a parallel update to the docs on govuk_publishing_components as I think they still refer to the startup scripts.

As long as the app runs, I don't mind what command I run to get it to do so - as long as the app runs.
But I do think that deprecating the startup scripts at this particular time is not a good idea. Developers that aren't using govuk-docker don't need any extra stress and shouldn't need to worry about a deprecation notice that states that startup.sh could disappear at any time without warning

Also, the docs were written for the user: Frontend Developers working on GOV.UK (I think I added this doc). Most frontend devs have told me that they find running the startup script more productive (as per Alex's comment). I deliberately included the govuk-docker instructions. Of course there'd be situations where you'd need more apps running locally, but for frontend development that isn't often the case.

I'm in favour of keeping the startup scripts as they make it easy for anyone to quickly get the environment up. Though it is easy to run the docker image - I still prefer this method and use it every day. It also helps onboarding new starting really easy.
I find also docker can take up more memory on my system than the start up scripts (that may just be my set up).

Thanks for all your comments so far everyone. I've now had some time to read through them properly. I'm going to try and summarise what I've read so far, and provide some answers / suggestions.
Summary of where we've got to

Several people have commented the startup.sh scripts are easier to use. @richardTowers also commented they can be easier to understand because they're closer to the actual command being run: rails s. @richardTowers also suggested putting the content of the script in the README. This would make the approach harder (due to copy/paste), so I suspect some people here would be against that, if they rely on these scripts currently.

@karlbaker02 and @maxgds asked about the level of support in GOV.UK Docker. All apps are supported, and all frontend apps fully support the app-live stack (the equivalent of startup.sh --live).

Most of our apps still have a startup.sh script (inc. all the backend ones). However, I think we only use them for certain frontend apps with the --live flag. Even this doesn't work for stateful frontend apps e.g. Email Alert Frontend.

@maxgds pointed out some READMEs still refer to these scripts (only). We should fix.

@injms pointed out we should avoid making any breaking changes right now. I agree.

Suggested actions to make progress
Taking all that together, let's see if we can agree on some (less extreme) actions:

Update various documentation:

Frontend app READMEs should Point to this documentation.
Other apps should point to the GOV.UK Docker README.
GOV.UK Docker compatibility incorrect for Frontend (is supported)
GOV.UK Docker compatibility out-of-date for Whitehall (is supported)
GOV.UK Docker compatibility incorrect for Calculators (is supported)
Update this manual to say startup.sh only (actually) works for some frontend apps.

Remove startup.sh scripts for all non-frontend apps. These are no different to running rails s manually, so we're actually making things clearer / easier by removing them for non-frontend apps.

Change startup.sh scripts for frontend apps to always run with --live, since this is the only way they currently work. Keep / remove startup.sh scripts for certain frontend apps:

Remove for Email Alert Frontend (doesn't work / stateful, requires local Email Alert API).
Remove for Feedback (doesn't work / stateful, requires local Support API).
Remove for Whitehall (doesn't work / stateful, requires local database and Email Alert API).
Keep for Collections
Keep for Frontend
Keep for Finder Frontend
Keep for Service Manual Frontend
Keep for Calculators
Keep for govuk_publishing_components
Keep for GOV.UK Developer Docs
Keep for Government Frontend
Keep for Info Frontend
Keep for Manuals Frontend
Keep for Smart Answers

What you can do
If you agree with these actions, you could give this comment a 👍. If you think we need to do something different, please comment which actions you agree with, and which you think we need to change / add / remove.

Just want to question the Whitehall side of things, I don't use the startup script myself and when I tried just now I got into a rabbithole of dependencies needing installing locally so stopped, BUT, for pages such as https://www.gov.uk/government/how-government-works would the startup script be a good and fast option? Does Whitehall's frontend side support the --live option in the script? Whitehall is currently doing a bunch of frontend delivery (long term plan is to change that but we're not there yet) and it doesn't have a use live data option in docker.

@maxgds that's a good point: Whitehall doesn't have a "live" option, either in it's startup.sh script or in GOV.UK Docker. This is because it's not really a frontend app - it's tightly coupled to its database / APIs. It's a monolith.
While some pages may work with a simple rails s, I think we should only have a startup.sh script if it works for all pages. Otherwise, it will only disappoint / confuse people. Most frontend apps are fine - the ones I suggest keeping it for, where all pages should render with --live - but not apps like Whitehall, which require a database and/or privileged access to protected APIs. These need the GOV.UK Docker ecosystem, and often some local data, in order to work with them.

While some pages may work with a simple rails s, I think we should only have a startup.sh script if it works for all >pages. Otherwise, it will only disappoint / confuse people.

I'm not going to make a big fuss about this because I don't use it and we want to rip out the frontend bits of Whitehall anyway, but I strongly disagree with this. If I need to update the CSS for the specific page I linked above, it's one hell of a requirement to install docker and download a database full of content in order to view what amounts to a static template full of hard coded html. At that point I'm going to not bother to run it at all, do live coding in the browser, paste it into the codebase and hope for the best when it reaches integration or heroku.

Ah, I think I need to clarify what I meant by "disappoint / confuse". Whitehall renders a lot of pages. Some of them work against live APIs, but many don't. All of them work in GOV.UK Docker, because it has all the dependencies. The problem for someone using Whitehall's startup.sh is that we don't know what will work, and what won't. So when someone tries to develop a page, they may encounter an error and be confused because we said "it should work".
Hopefully a developer will already have GOV.UK Docker for developing other GOV.UK apps.
If you feel strongly about having partial frontend support for Whitehall, perhaps we could make the experience better by updating the README to explain startup.sh will only work for some things, and to try GOV.UK Docker if not.
How does that sound?

How does that sound?

That makes sense. I was in a position for a long while of running lots of things in Docker but rarely needing to use Whitehall so I hadn't downloaded the required data. That eventually became necessary but it was no small undertaking - an alternative to that, depending on what it is you need to do, is a good thing to provide for where it works.

As long as the app runs, I don't mind what command I run to get it to do so - as long as the app runs.

I think this is my general feeling, to navigate through all app pages and functionality easily, locally.
(From a FE POV, part of me also wants one command to spin up most of site locally and move through it like I'm on live, I'm not sure if microservices architecture but with a monolith local "feel" conceptually has a name..)

While I share the view about converging to a single way of running apps locally, as it makes sense especially from a maintenance point of view,

I do agree with this sentiment to have one unifying method

I don't agree. I think having a simple way of running the applications on the host is valuable.

I also think this is true.

Are we confident that everything can be run in docker? I thought there were some outliers, still.

I was wondering if this was the case with all apps? I did think some had some known issues (I know whitehall has been mentioned which sounds like it's own rabbit hole, I wondered about frontend...)

All apps are supported
GOV.UK Docker compatibility incorrect for Frontend (is supported)

I was recently was starting up  frontend + docker.  I had expectations that this would work navigating through find-local-council
 as I thought this would install the relevant mapit dependencies or utilise setup from a live api.

I can identify with this, eg with /find-my-council, I don't need all of the local postcodes across all of the UK installed locally in order to continue to work - I just need the dozen or so postcodes that lead to the variations of outcome pages.

the effort to debug problems with GOV.UK Docker when things go wrong can be more involved

I'm a bit concerned about this when startup sometimes hasn't been as smooth as it could be

I think that keeping the start-up scripts reduces the barrier to entry to get the apps which contain these scripts running, which is no bad thing.

&

I'm in favour of keeping the startup scripts as they make it easy for anyone to quickly get the environment up.

I tend to agree or deprecate once there's one unifying method across all, however the suggested way forward seems like a nice halfway.

Change startup.sh scripts for frontend apps to always run with --live

This makes sense.

Thanks for all your comments everyone. Since the discussion is now very long, and the direction quite different from the beginning, I'm closing this one in favour of a (hopefully) more agreeable proposal / PR:
>>>>>>>>>> https://github.com/alphagov/govuk-developer-docs/pull/2897 <<<<<<<<<<<
What's changed?

The third commit is different (suggest, rather than deprecate).

The PR description contains a bunch of associated actions.

@alex-ju @maxgds @chris-gds @chao-xian @injms hello 👋. I've got a PR up on Collections to implement the changes we discussed here. I'd appreciate your thoughts on one specific commit: https://github.com/alphagov/collections/pull/2362/commits/58d68104e5110069ff5f758da1704084a20c9166.
For context, we've now rewritten the bulk of the READMEs for GOV.UK repos. The idea is now to make frontend repos  consistent with those. See here for the first use of the new content: https://github.com/alphagov/content-publisher/pull/2257.
Much of the PR is about getting the README into shape, and has already been reviewed. You don't need to look at the other commits. Once I've got some feedback from you, I'll look at rolling out the same change across other frontend repos.
You're welcome to leave a comment on the PR, or here.


Help Regarding UI

Currently, I've been using Tkinter to make GUI for YouTua but it doesn't look the way people need. So, is there anyone who can configure YouTua with a better GUI library in Python. Also, if you think you can change the current GUI made using Tkinter to look better, it'll be useful. Please let me know if anything comes up in your mind.

Python doesn't excel in UI, that's a fact. There's various UI libraries, but I personally would recommend these:

Flexx
PyQT5
PySide

Yeah @Sylack-lab , I did look into them but the thing is if I want to change, I'd have to do this from scratch plus I haven't used the libraries in any other projects so a helping hand would be good for the same.

Hey @dhhruv !
Sorry for the late response, but I could come up only an exact clone of your Tkinter UI. I guess that the UI is already simple and compact, that said it makes really easy to navigate and get the job done!
Here are some screenshots:

But, I'll try to think of new designs.

That's good but if you can think to make it more attractive and more user-friendly, it would be better. Please let me know if you get any more ideas.

Hey @dhhruv !
Here's a small improvement to the UI.
Can you tell me some other points to work on? Maybe new features? According to that, I can rebuild the UI with your suggestions.


Feature : Import Helpers

I've been working on a library of helper functions that make importing JSON onto your CoreData objects using AlecrimCoreData and SwiftyJSON incredibly easy using generics.
It's something that I think would be a benefit to the community. I'm looking into open-sourcing it, but I'm not sure what the best place to put it is. Since its use depends on the use of AlecrimCoreData, it might make sense as a subspec of this library. Would you be interested in including it here, or should I create a separate repository?

Hello.
I would like to apologize for the delay in response. I had a health problem and recently I needed surgery because of it. Now I'm fine, but I'm still in after surgery period.
About the library, I'm very excited to see it working. :-)
I think a separated repository will be a better place, since it uses two third-party libraries (ACD and SwiftJSON).
Please feel free to contact me if you need further help. I can not promise I'll answer as readily, but I'll try.

Alright thanks. That's kind of what I was thinking. I'm looking into cleaning up my library a bit and making a few things more configurable.


Support hardware secure CDM/Widevine playback in Chrome for Windows

Have you read the FAQ and checked for duplicate open issues?
Yes
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Support hardware secure CDM playback in Chrome for Windows with documentation.
Describe alternatives you've considered
Whether Chrome can support PlayReady like Edge with "hardware secure CDM".
Additional context
In Chrome 99, enabling "Hardware Secure Decryption" in chrome://flags will show "Google Widevine Windows CDM" in chrome://components. Does shaka player support this CDM?

👋 There are no reasons Shaka shouldn't support L1 implementation of Widevine (already does on Android w/ Chrome)

I believe that once enabled, L1 support on Windows is triggered in software by setting robustness to HW_SECURE_ALL.  @xhwang-chromium, can you confirm?  To trigger the L1 implementation where possible, should this be set for both audio and video, or just video?

We recommend to set video to be HW_SECURE_ALL and audio to be HW_SECURE_CRYPTO. But the L1 path will be selected when either is set.

Is there an api in shaka player to detect whether the CDM supports HW or SW? Or can shaka try HW first and fallback to SW? Thanks.

You could use this to detect what is the maximum level that is supported.
async function getWidevineRobustness () {
  const robustnessLevels = [
    'SW_SECURE_CRYPTO', // Widevine L3
    'SW_SECURE_DECODE', // Widevine L3
    'HW_SECURE_CRYPTO', // Widevine L2
    'HW_SECURE_DECODE', // Widevine L1
    'HW_SECURE_ALL', // Widevine L1
  ];

  const videoTestConfig = [
    {
      videoCapabilities: [
        {
          contentType: 'video/mp4; codecs="avc1.42E01E"',
          robustness: 'SW_SECURE_DECODE',
        },
      ],
    },
  ];

  const audioTestConfig = [
    {
      audioCapabilities: [
        {
          contentType: 'audio/mp4;codecs="mp4a.40.2"',
          robustness: 'SW_SECURE_DECODE',
        },
      ],
    },
  ];

  let videoRobustness;
  let audioRobustness;

  for (let i = 0; i < robustnessLevels.length; i++) {
    const level = robustnessLevels[i];
    videoTestConfig[0].videoCapabilities[0].robustness = level;
    try {
      // eslint-disable-next-line no-await-in-loop
      await navigator.requestMediaKeySystemAccess('com.widevine.alpha', videoTestConfig);
      videoRobustness = level;
    } catch (err) {}
  }

  for (let j = 0; j < robustnessLevels.length; j++) {
    const level = robustnessLevels[j];
    audioTestConfig[0].audioCapabilities[0].robustness = level;
    try {
      // eslint-disable-next-line no-await-in-loop
      await navigator.requestMediaKeySystemAccess('com.widevine.alpha', audioTestConfig);
      audioRobustness = level;
    } catch (err) {}
  }

  return {
    videoRobustness: videoRobustness,
    audioRobustness: audioRobustness,
  }
}

@xhwang-chromium   or if anybody else knows, can you please comment on what are the system requirements for Widevine to leverage L1 on Windows?
I assume some form of Trusted Execution Environment is required, so only selected processors are suitable. Can you confirm?
Does operating system version itself play a role in this? Is presence of Trusted Platform Module (TPM) required as well?

As mentioned above Shaka supports hardware DRM, just through DRM configuration.  There is no automatic selection of hardware vs software CDM, though.  If not specified by the app, the default is up to the browser/platform.
Shaka could offer something in the future where we will automatically try HW first, then fall back to SW.  I'll rename the issue to reflect this.
But before doing any work on this, we would need @xhwang-chromium to confirm is this is even necessary.  If no robustness is specified, will Chrome choose the L1 CDM by default if available, and L3 otherwise?  Or would L3 always be used by default?

Re https://github.com/shaka-project/shaka-player/issues/4013#issuecomment-1110579710. For Chrome browser we only support 'SW_SECURE_CRYPTO' (on Android), 'SW_SECURE_DECODE' and 'HW_SECURE_ALL'. So querying for the following would be sufficient. Also, if L1 is preferred, it should be queried first, e.g.
  const robustnessLevels = [
    'HW_SECURE_ALL', // Widevine L1
    'SW_SECURE_DECODE', // Widevine L3
    'SW_SECURE_CRYPTO', // Widevine L3
  ]

Re https://github.com/shaka-project/shaka-player/issues/4013#issuecomment-1118998669. In short, for Widevine in Chrome, if no robustness is specified, we'll default to the lowest robustness, e.g. Widevine L3.
Here's our general recommendation on this topic:
Avoid Empty Robustness
What does the spec say?
http://w3c.github.io/encrypted-media/#idl-def-mediakeysystemmediacapability, emphasis added

Implementations MUST configure the CDM to support at least the robustness levels specified in the configuration of the MediaKeySystemAccess object used to create the MediaKeys object. Exact configuration of the CDM is implementation-specific, and implementations MAY configure the CDM to use the highest robustness level in the configuration even if a higher robustness level is available. If only the empty string is specified, implementations MAY be configured to use the lowest robustness level the implementation supports.

Applications SHOULD specify the robustness level(s) they require to avoid unexpected client incompatibilities.
What does Chrome do for empty robustness?
Chrome’s behavior is platform-dependent and is subject to change in the future. You may end up with the lowest level even though higher levels are available.
When an empty robustness is used, Chrome will show a warning message in the dev console.

It is recommended that a robustness level be specified. Not specifying the robustness level could result in unexpected behavior, potentially including failure to play.

What should applications do?
Always specify the robustness level(s) required (by the license server) and/or that would affect the streams selected. The application could specify multiple MediaKeySystemMediaCapability values with different robustness levels and make decisions based on which one is supported.

I enabled "Google Widevine Windows CDM" in Chrome Beta 102. When video robustness is SW_SECURE_DECODE and audio robustness is SW_SECURE_CRYPTO, it seems like this L1 CDM is still selected, instead of the L3 "Widevine Content Decryption Module". Widevine proxy generates EXTERNAL_LICENSE_ERROR with message "Missing ContentId within Pssh data for ExternalLicenseRequest". When the L1 CDM is disabled, the L3 CDM can play the content. The test content uses custom encryption keys and the keys are sent to the widevine proxy. However, test content with contend id in pssh and widevine keys (https://storage.googleapis.com/shaka-demo-assets/sintel-widevine/dash.mpd) can play when L1 CDM is enabled.

Do you have a repro page I can look at? Thanks!

Please try this repro:
https://shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;panel=CUSTOM CONTENT;build=compiled
Manifest url:
https://personal-data-2018.s3.amazonaws.com/bbb/b5.mpd
DRM custom license server url:
https://widevine-proxy.appspot.com/proxy
Shaka reports error code 6007 when L1 CDM (Hardware Secure Decryption flag) is enabled.
Codec: avc1.640029,mp4a.40.2

It's querying for HEVC w empty robustness (which will be defaulted to SW_* levels).
I think I know how this happened. I'll file a Chromium bug and fix it.
Again, it's always recommended not to have any empty robustness when querying Widevine capabilities.

@xhwang-chromium can you paste the link to the Chromium bug? Thanks!

Fix is here. The CL description has all the info.
https://chromium-review.googlesource.com/c/chromium/src/+/3654750


installation on Ubuntu ppc64le

Expected behaviour
I want to install this package on Ubuntu ppc64le architecture but it constantly tells me that there is no available version... I have used docker image and compiled OpenCV from source, similar as it is here which succeed but then installing opencv-python fails...
Actual behaviour
Collecting pip
  Using cached https://files.pythonhosted.org/packages/30/db/9e38760b32e3e7f40cce46dd5fb107b8c73840df38f0046d8e6514e675a1/pip-19.2.3-py2.py3-none-any.whl
Installing collected packages: pip
  Found existing installation: pip 19.2.3
    Uninstalling pip-19.2.3:
      Successfully uninstalled pip-19.2.3
Successfully installed pip-19.2.3

$ pip install opencv-python
Collecting opencv-python
  ERROR: Could not find a version that satisfies the requirement opencv-python (from versions: none)
ERROR: No matching distribution found for opencv-python

Steps to reproduce

docker source: https://hub.docker.com/r/nvidia/cuda-ppc64le
operating system: FROM nvidia/cuda-ppc64le:10.0-runtime-ubuntu18.04
architecture: ppc64le
opencv-python version - last

There are no builds for your architecture. If you compile OpenCV manually (like you have done), then opencv-python is obsolete. This repository just provides an automatic toolchain for Python to compile OpenCV Python bindings and generates pre-built packages for some popular architectures and uploads them to PyPI (see https://pypi.org/project/opencv-python/#files, no ppc64le wheel there -> pip complains about missing distribution).
However, if you wish to have opencv-python wheel package for your architecture, then you must execute following commands:
git clone https://github.com/skvark/opencv-python
cd opencv-python
python setup.py bdist_wheel (this will take 10+ minutes)
cd dist
pip install generated_wheel_package.whl

Well I have tried also following with the same failer...
pip install https://github.com/skvark/opencv-python/archive/master.zip
Which should do the build too, right?

Btw, having compiled openCV manually and installing opencv-python from pip uses my custom build or does it creates another copy (binaries/compilation)?

Well I have tried also following with the same failer...
pip install https://github.com/skvark/opencv-python/archive/master.zip
Which should do the build too, right?

The setup.py `logic currently assumes that it's run inside a directory which is a Git repository (because setup.py clones opencv and opencv_contrib submodules) so that command will fail. I'll try to publish a source tarball in the next release which means that pip install opencv-python will fall back to manual build if a compatible pre-built wheel is not found from PyPI.

Btw, having compiled openCV manually and installing opencv-python from pip uses my custom build or does it creates another copy (binaries/compilation)?

This repository has nothing to do with your custom build. In fact, the first step in the README says that you must remove other manually installed OpenCV python binding versions if you wish to use opencv-python. opencv-python uses its own copy of OpenCV.
You either use opencv-python OR you compile OpenCV manually and install it manually to your Python environment. You can't use both simultaneously because they are two different packages.


How to use streams?

Hi Alec,
How can I use (XADD, XREAD, XREADGROUP) from Redis streams with Fred?
What I am especially looking for is some easy way to subscribe to stream messages coming in.
Is there a comparison of speed, memory usage and features with the redis-rs crate somewhere?
Thanks a lot.

Hi @8192K,
Here's a few options showing stream examples:

The integration tests cover most of the interfaces but use somewhat contrived examples.
I added a streams example in my working branch. It'll be included in the main examples folder with the next release. I'm not expecting any of the streams interface to change between releases in the future.

In terms of performance or a more detailed technical breakdown - sort of. I've been meaning to write a design document for a while but only recently started including this in the repo. Here's a few links you may find useful, but some of these are tied to the next release (planned for this month).

A benchmarking tool will be included with the next release. You might find the README and examples section helpful.
I'm in the process of working on a more detailed design doc. It's still a work in progress but aims to provide a quick overview for anybody that wants to evaluate this in more detail.
The redis-protocol crate implements a zero-copy RESP2 and RESP3 parser so memory usage is generally minimal. Ultimately this really depends more on your use case or app code, however.

Closing for now, but feel free to reopen if you have other questions.


🐛 BUG: Sass Plugin isn't working

Quick checklist

[X] I am using the latest version of Snowpack and all plugins.

What package manager are you using?
npm
What operating system are you using?
Windows
Describe the bug
So I'm trying to make a simple react typescript app with snowpack, using sass as styling. Every time I try to run the app I get a error saying that main.scss isn't found when it literally exists, I also tried building the project and running it like that but that also did nothing, I watched some tutorials and they were using the same method I was and it still didn't work. I'm looking for some advice here on how to make this work, all help is appreciated

Steps to reproduce

npx create-snowpack-app using template react typescript
npm i @snowpack/plugin-sass
go into your snowpack.config.js and put in the following information into your plugins array

[
      '@snowpack/plugin-sass',
      {
        native: true,
        compilerOptions: {
          loadPath: 'styles',
          sourceMap: true,
          style: 'compressed',
        },
      },
    ]

Create a sass/scss file in a folder called styles, import it in the App.jsx file and run npm start
When i do this i get a error saying that the file is not found

Link to minimal reproducible example (optional)
No response

It is ...quite strange here.
For resolving this issue here, you just need to remove 'sourceMap:true' in your config, since it is a default value. And when you explicit 'sourceMap:true', then you also need to explicit 'embedSourceMap:true' in your config..., which is quite confusing here is  'embedSourceMap:false' should be accepted however get an error from Sass.
I don't use sourceMap so often, not very sure why..


cannot reset wrong account token

Visual Studio Code Version : 1.1.1
Code Sync Settings Version : 1.2.3
I wanted to initialize sync. I did set the token wrong in my github account and then I also entered a wrong string when I was asked for the token in the command line of visual studio code (vsc).
I think, I entered the string "default" as access token in vsc
After that, I was not able to get to the command line to reset the token.
Even after deinstallation and reinstallation, the wrong value seemed cached.
Is there a file that I can delete to be able to start again with initialization?
Error says: Please open an issue in Github Repo. Please find attached the console log.
1463600575811.txt

Type "Sync" and select reset settings in order to remove those settings and try again.
Let me know if issue still occurs.

Problem solved:
I used the ctrl + p command line instead of the ctrl + shift + p command palette.
In the command line, "Sync" was not available as a command ... when using command palette everything worked fine just as documented ...


Fix race in test

Fixes the warning that shows up at 'go test -race'.
I don't understand why this is necessary, also why the same patch is not required at line 995. I'd happy if someone explains. cc @grobie

CI failure is the flaky test. This is good to go.

cc @grobie I added the requested changes.


[Feature Request] Add a more obvious button to the open source page

Overview
Add more obvious button for new members signing up open source team volunteer.
Details
Add a "Join Us Now" button between "who is" and projects in open source page. It will link to the open source sign-up form.
Why would this feature be useful?
Better for new ppl to sign up
Additional Notes
No response

I'll take a look at this after uni. Feel free to assign this to me.

Ohh, I saw this is already assigned to @KnightRadiant44 after I raised a PR here

dw, I can assign this to you @yiukuenchu

Fixed in #164


SampleAppx.*.png still included even when custom assets are specified

Steps to reproduce:

create "custom_assets" folder
Set assets: '.\\custom_assets' in config
Run build

Expected behavior: the default SampleAppx.*.png are not included
Actual behavior:
ls .\pre-appx\assets\

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       26/10/1985     09:15          18804 SampleAppx.150x150.png
-a----       05/05/2020     16:34          19154 SampleAppx.310x150.png
-a----       26/10/1985     09:15           1912 SampleAppx.44x44.png
-a----       26/10/1985     09:15           1742 SampleAppx.50x50.png
-a----       05/05/2020     16:33           5561 MyApp.150x150.png
-a----       05/05/2020     16:33           1534 MyApp.44x44.png
-a----       05/05/2020     16:33           1738 MyApp.50x50.png

@felixrieseberg ping

@mahnunchik I created a fork that merged PR134 and may have solved this problem