[BUG] Erros, can't even start

Describe the bug
I followed the process for installation, installed requirements, run script and it can't even start
showing errors
https://prnt.sc/6SF4830dRA54
**Terminal output
C:\Users\logde\OneDrive\Desktop\OpenSea-NFT-Stealer-master>py opensea.py lazy-lions
Beginning download of "lazy-lions" collection.
Traceback (most recent call last):
File "C:\Users\logde\OneDrive\Desktop\OpenSea-NFT-Stealer-master\opensea.py", line 124, in
data = json.loads(scraper.get(f"https://api.opensea.io/api/v1/assets?order_direction=asc{token_ids}&limit=50"
File "C:\Users\logde\AppData\Local\Programs\Python\Python310\lib\json_init_.py", line 346, in loads
return _default_decoder.decode(s)
File "C:\Users\logde\AppData\Local\Programs\Python\Python310\lib\json\decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Users\logde\AppData\Local\Programs\Python\Python310\lib\json\decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
C:\Users\logde\OneDrive\Desktop\OpenSea-NFT-Stealer-master>**
paste here

Same error, I tried to change browser User-Agent data with no luck.  Also I tried to check the url (printing the result of the dict) and it works.  Maybe is a thing related to changes on the API on opensea side

This interface now requires an API Key

@G-Z-Ming thanks for the advice.  I'm going to open a dev account and try to fix the code and share here if I can do it too...

fixed https://github.com/sj-dan/OpenSea-NFT-Stealer/pull/53


fix(atenlib): make functions with dtype attributes trace_only

ONNX requires if branches to produce the same type. This requirement conflicts with some logic we have in the atenlib. This PR fixes the logic.
cc @fatcat-z @xiaowuhu @titaiwangms @BowenBao @gramalingam
Fixes #419

I am going to test this fix with ORT.

What happened to CI / test (ubuntu-latest, py310-onnx-weekly) (pull_request) ?

onnx weekly didn't upload a linux wheel last week. we expect this to be fixed next week.


Trying to add nix-flatpak as a home-manager module. What am I doing wrong?

So, I added the nix-flatpak input to my NixOS flake, rebuilt and switched to the new generation, everything seemed fine.
Then, I wanted to add the input to my home-manager flake too, since I will want some Flatpaks installed system-wide, and some only for specific users. Followed the instructions as best as I could, since the examples show importing the module inside a NixOS HM module, but I use HM standalone, and I ran into this error.
$ home-manager -v switch --flake ~/.config/home-manager/#andy3153

error:
       … while updating the lock file of flake 'path:/home/andy3153/.config/home-manager?lastModified=1710550103&narHash=sha256-k7/smjAUtDKPYjwQYQ4l2AlW2Tdth/2F0LOlFyGvdHk%3D'

       … while updating the flake input 'nix-flatpak'

       … while fetching the input 'github:gmodena/nix-flatpak/v0.3.0'

       error: failed to extract archive (Could not open /tmp/nix-10224-0/nix-flatpak-a243cb0522f6240c194b873dde68e25370b06034)

This is my home-manager flake.
What have I done wrong?

Solved here. Still have no idea what the root cause was though.


Fix handling of indicators in plain scalars to conform to YAML 1.2

YAML 1.2 has special handling of indicators to be compatible with JSON.
The following is equivalent to {"a": "b"} (note, no space after :):
{"a":b}

But without the quoted key, a space is required. So the : here is part
of the plain scalar:
{a:b}  # == {"a:b"}

A plain scalar can also start with a : as long as it's followed by
"safe" characters:
{a: :b}  # == {"a": ":b"}

(Fixes #118)
(See #116 for failing build)

@chyh1990 saw that you merged the rustfmt PR :)! Rebased this one and it now has a green build too.

@chyh1990 Yay :). Are you planning to cut a release with this fix soon?

v0.4.3 has been released on Github & crates.io


Update init script for Python

[I think the script for initialization of the function app in Python have to be updated - to add --model V1. Since right now this script creates function app in Python in V2 and the tutorial is for V1, this can be confusing to non experienced users.]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 4b610110-f417-3565-bbd6-35e90a567a2d
Version Independent ID: 53b5d6ae-54ef-c45d-19f1-cd2ebd7e1bd6
Content: Tutorial - Create a serverless notification app using Azure Web PubSub service and Azure Functions
Content Source: articles/azure-web-pubsub/tutorial-serverless-notification.md
Service: azure-web-pubsub
GitHub Login: @JialinXin
Microsoft Alias: jixin

Thanks for the suggestions. Looks the default model is updated from V1 to V2 and the sample here is out of date then. PR is created and will fix soon.


Route with cert-manager annotations is not created

Hi, I'm trying to install a route of edge termination using cert-manager annotations in openshift cluster (crc), this is part of our operator's reconcile loop.  The following annotations are added to the route:
      "annotations": {
        "cert-manager.io/common-name": "arkamq.io",
        "cert-manager.io/issuer-kind": "Issuer",
        "cert-manager.io/issuer-name": "selfsigned-issuer-ingress"
      }

The dump of the full Route spec:
  "route": {
    "kind": "Route",
    "apiVersion": "v1",
    "metadata": {
      "name": "artemis-broker-wconsj-0-svc-rte",
      "namespace": "default",
      "creationTimestamp": null,
      "labels": {
        "ActiveMQArtemis": "artemis-broker",
        "application": "artemis-broker-app",
        "statefulset.kubernetes.io/pod-name": "artemis-broker-ss-0"
      },
      "annotations": {
        "cert-manager.io/common-name": "arkamq.io",
        "cert-manager.io/issuer-kind": "Issuer",
        "cert-manager.io/issuer-name": "selfsigned-issuer-ingress"
      }
    },
    "spec": {
      "host": "artemis-broker-wconsj-0-svc-rte-default.apps-crc.testing",
      "to": {
        "kind": "Service",
        "name": "artemis-broker-wconsj-0-svc",
        "weight": null
      },
      "port": {
        "targetPort": "wconsj-0"
      },
      "tls": {
        "termination": "edge",
        "insecureEdgeTerminationPolicy": "Redirect"
      },
      "wildcardPolicy": "None"
    },
    "status": {
      "ingress": null
    }
  }

However the route is not created. I dumped the openshift-route pod's log and I see something is going on but no obvious error messages. I'll attach the log. My environment is
CRC version: 2.25.0+97705a
OpenShift version: 4.13.6
Podman version: 4.4.4

cert-manager is installed from operatorHub from default channel
openshit-route is installed using the following command

oc apply -f https://github.com/cert-manager/openshift-routes/releases/latest/download/cert-manager-openshift-routes.yaml

I'll attach also the output of oc events to provide more information.
Please help. Thanks!
oc_events.log
openshift-routes-pod.log

It looks like there is an issue with the route definition? In the logs the route is visible, but in the pasted configuration apiVersion: v1 for kind Route is not valid, it should be apiVersion: route.openshift.io/v1. This might just be a copy paste issue though?
Can you also check to see whether a CertificateRequest CR was generated? I don't see the event for it in your attachment but there is a log message the CR is not ready. If it was cceated, can you check to make sure the issuer is in a Ready state in the default namespace and perhaps check your cert-manager controller logs (assuming the certificate request was created).
$ oc get issuers -n default
$ oc get certificaterequests -n default
$ oc describe certificaterequest <cr>
$ oc get events -n cert-manager
$ oc get events -n default
$ oc logs cert-manager-controller -n cert-manager

"CR not ready"
I0905 13:27:30.681290       1 app.go:90] cert-manager-openshift-routes/controller-manager "msg"="Event(v1.ObjectReference{Kind:\"Route\", Namespace:\"default\", Name:\"artemis-broker-wconsj-0-svc-rte\", UID:\"345b4999-f3db-4dc4-bc4c-2c842fb9f4f1\", APIVersion:\"route.openshift.io/v1\", ResourceVersion:\"140254\", FieldPath:\"\"}): type: 'Normal' reason: 'Issuing' Issuing cert as no certificate exists"
I0905 13:27:30.690862       1 sync.go:99] cert-manager-openshift-routes/route/sync "msg"="cr is not ready yet" "resourceVersion"="140254" "route"={"Namespace":"default","Name":"artemis-broker-wconsj-0-svc-rte"}

I was able to successfully generate a certificate using your provided Route spec, aside from the apiVersion that needed a correction.

Thank you. I'll try.

@ctrought Hi,
I tried to fix the route's apiVersion (it's in our operator code) and re-deployed our resources.
I can see the apiVersion is correct now (route.openshift.io/v1).
But the route is still not able to be deployed. The route is created/deployed by our operator based on
our deployed CR. I observed during the process the route is first being created and then it's gone.
(I'm using oc get routes command)
Here is the output of the command I tried:

first I tried to get route:(i have everything in default namespace)

$ oc get route
NAME                              HOST/PORT                                                  PATH   SERVICES                      PORT       TERMINATION     WILDCARD
artemis-broker-wconsj-0-svc-rte   artemis-broker-wconsj-0-svc-rte-default.apps-crc.testing          artemis-broker-wconsj-0-svc   wconsj-0   edge/Redirect   None

A few seconds later the route is gone:

$ oc get route
No resources found in default namespace.

get issuer

$ oc get issuers -n default
NAME                        READY   AGE
selfsigned-issuer-ingress   True    2m19s

get csr

$ oc get certificaterequests -n default
No resources found in default namespace.

get cert-manager events

$ oc get events -n cert-manager (see the attached oc_get_events_n_cert_manager.output.log
[oc_get_events_n_cert_manager.output.log](https://github.com/cert-manager/openshift-routes/files/12610988/oc_get_events_n_cert_manager.output.log)
)

get default events

$ oc get events -n default (see attached oc_get_events_n_default.output.log
[oc_get_events_n_default.output.log](https://github.com/cert-manager/openshift-routes/files/12610992/oc_get_events_n_default.output.log)
)

get cert-manager log

$ oc logs cert-manager-7cc7959fbb-w6fzk -n cert-manager (see attached oc_logs_c
[oc_logs_cert_manager.log](https://github.com/cert-manager/openshift-routes/files/12610998/oc_logs_cert_manager.log)
ert_manager.log)

get openshift-routes log

$ oc logs cert-manager-openshift-routes-5bfbc6fb88-75zvd -n cert-manager (see attached) cert-manager-openshift-routes-pod.log
[cert-manager-openshift-routes-pod.log](https://github.com/cert-manager/openshift-routes/files/12611006/cert-manager-openshift-routes-pod.log)

In oc_get_events_n_default.output I see some error like
7m20s       Warning   InternalReconcileError                       route/artemis-broker-wconsj-0-svc-rte                      error while reconciling: Operation cannot be fulfilled on routes.route.openshift.io "artemis-broker-wconsj-0-svc-rte": the object has been modified; please apply your changes to the latest version and try again

Not sure if that's relevant. But I do see the CSR get approved in the same file:
m31s       Normal    cert-manager.io                              certificaterequest/artemis-broker-wconsj-0-svc-rte-q4r49   Certificate request has been approved by cert-manager.io

I'm not sure what could be the issue. Please help.
Thanks

I observed during the process the route is first being created and then it's gone

That sounds like something else is causing it. Cert-manager routes won't delete your route. Maybe whatever you're using to deploy the route is removing the route?
Have you tried deploying the route directly instead of using the operator you mentioned? You can check the kube api-server audit logs to see what's deleting the route. Since you're using OpenShift, you can use the cluster logging operator to send audit logs to elasticsearch or loki to query the audit logs if you don't already. Or you can use the CLI to view them https://docs.openshift.com/container-platform/4.13/security/audit-log-view.html

Thanks. Yes turns out it's out operator's bug that causes the Route resource being deleted.
Now with the bug fixed the route seems working (I can access the service via the route). However it looks like the route is not using the certificate from openshift-route. There is no cert resource generated (in default namespace). By examining the certificate it seems that the route is using the default certificate.
The route spec does show some fields being generated by openshift-route, but it's not complete.
For example if I deploy this route:
apiVersion: route.openshift.io/v1
kind: Route
metadata:
  annotations:
    cert-manager.io/common-name: arkamq.io
    cert-manager.io/issuer-kind: Issuer
    cert-manager.io/issuer-name: selfsigned-issuer-ingress
  labels:
    ActiveMQArtemis: artemis-broker
    application: artemis-broker-app
    statefulset.kubernetes.io/pod-name: artemis-broker-ss-0
  name: my-route-artemis-broker
  namespace: default
spec:
  host: my-route-artemis-broker-default.apps-crc.testing
  port:
    targetPort: wconsj-0
  tls:
    insecureEdgeTerminationPolicy: Redirect
    termination: edge
  to:
    kind: Service
    name: artemis-broker-wconsj-0-svc
    weight: 100

and then use oc get route to get the created route, there are some new annotations
injected (cert-manager.io/certificate-revision and cert-manager.io/next-private-key)
But no certs in the route spec. See below for the full contents:
(20)[20:51:26]@route$ oc get route my-route-artemis-broker -o yaml
apiVersion: route.openshift.io/v1
kind: Route
metadata:
  annotations:
    cert-manager.io/certificate-revision: "0"
    cert-manager.io/common-name: arkamq.io
    cert-manager.io/issuer-kind: Issuer
    cert-manager.io/issuer-name: selfsigned-issuer-ingress
    cert-manager.io/next-private-key: |
      -----BEGIN RSA PRIVATE KEY-----
      MIIEowIBAAKCAQEAudmUOn8c6KwCKB+ZI4tKBcUB1iJI3Baeh7gOpTcZmOmYJ3cn
      Zq+H1lQ5xcdc9c4tkEEcLscNOlWZiCTpMmKZFXbPJxr8K4g7s/KasTBY8XtnkPTL
      VQedaMiRy1aIJKYxE88ImUh/L/bY3iQIkUA4RedeaaTEE/CTFe+8+pOmTyEH/Ta4
      atNAffGbnhwHKOxjuMW3n0ePvHP0twSFxxRA+n6wHHzREftcDmyo3rr1MGfMwwh0
      7jAphdZ3jFrz+9glr6PUwdiK14bAYiQRDr99PabLtRqtADpXBuKmEr3RIoJ0R10Q
      YC+LFJ8l0jsp4yXdOkPAMTN8c9iLkesbm10IfwIDAQABAoIBAHbXBazeKWsyynJD
      ulX7NIs57bGy3Ko3oImijWLiN/EKtivOSpij95V66DJrCCt5+rK6n73dtLyvjex7
      xc5dNAyAm3gjDkr740lvAbH5+3X29kO/9OFbbDFbx7ahj4734nwLMDFsJUBTdVue
      6QeQbCtvBnVBUcx6UmN9mHcWwQrpOIs/5SpI49TNixN641k6JxE9YG060Ih1kEMg
      x0rE6R3Spb09/aFcFvJLgloJD4GC3IZEkZoqFvBc4myg7t3JuuA8HXfE34mcHLff
      NaAIjlVrO14e83NOMddIvrLqMXybJC3DUST+Cl9ZwMCwiWSteTsjkTv+b3aDnWrB
      /vATodkCgYEA9B8mWahrrFHe3XVh10qmbjlcGil4FU9T8dy4M9VKPEq8OOUWjvEe
      dWt7lX97VHy6jCjInJObLsbzZxiacea6E6t78V2QxvcCAR9uDjN4NDzKB/xIs9we
      U7rargeohUZNd8fncYEKO5TCzNN97k4+uzzC8i0pvI7ja1CSMVn+5gUCgYEAwuSU
      TgIQTutBxmGf4jmjlhH+6lK1QTdM1TW9bvtyI2i/JrvuRU8T0RzrMfFvU+lER3Su
      D20M9goFDgL51GsKKfmbJOWO22lAzz3ASHbl6+M7POY8pzb/+QZ2AAX+yHfOO2sz
      I7RxwN6gD0Jz/PcrVOJ9zZWw/hgX8LVeWo1k17MCgYAb9Z1c029RkyblUlZcZA5f
      vW4RCQLZ3fYNU2w9c4ZHFYAtO/+za2ZDqIXE/47OhGKRPvKLDFTPrLWf7y9xMC3L
      pu5RHJhCUXQHUOQ3+CkiQnwZIgnpn6JRkKsPF41zhjPFLj4Rv+e+HzGYZ/iaXJfO
      tgzV09pd4DenyNiVkmshSQKBgF3Yv+lIaR33fvbOL7U52CH9jGi9ZvZ+cIsCk7OL
      dQzD9bfrKvNI/tvlNwQXpGodm3llICPheSpI7OIwYKj+2igYP7Lmr4HMDx88Nwkt
      581M4EuU+oPyohQCHnQobuWNe0t1dWyuCVC8Ywq2DzAyvTTk03tZp57Tb0PDsimc
      iICtAoGBAOOZeVUpkHY/oDsMyenTfJWDxKTtncnNlV0tG5QII9J/AAdRX7gNGIrq
      cp1ubde4LZVpvB5HXf5LF+12ZZDbFCbDTK6Kx8HoDLRcv/1vs/A/heXdnxl1e4eh
      vRtYoO8fDx3tVC4QSdWoJr2HjNXp5GO28rviJusafeNfhAaEirwl
      -----END RSA PRIVATE KEY-----
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"route.openshift.io/v1","kind":"Route","metadata":{"annotations":{"cert-manager.io/common-name":"arkamq.io","cert-manager.io/issuer-kind":"Issuer","cert-manager.io/issuer-name":"selfsigned-issuer-ingress"},"labels":{"ActiveMQArtemis":"artemis-broker","application":"artemis-broker-app","statefulset.kubernetes.io/pod-name":"artemis-broker-ss-0"},"name":"my-route-artemis-broker","namespace":"default"},"spec":{"host":"my-route-artemis-broker-default.apps-crc.testing","port":{"targetPort":"wconsj-0"},"tls":{"insecureEdgeTerminationPolicy":"Redirect","termination":"edge"},"to":{"kind":"Service","name":"artemis-broker-wconsj-0-svc","weight":100}}}
  creationTimestamp: "2023-09-19T09:20:20Z"
  labels:
    ActiveMQArtemis: artemis-broker
    application: artemis-broker-app
    statefulset.kubernetes.io/pod-name: artemis-broker-ss-0
  name: my-route-artemis-broker
  namespace: default
  resourceVersion: "1060469"
  uid: 1d98e663-18b5-4ce8-bf1c-b8521068370f
spec:
  host: my-route-artemis-broker-default.apps-crc.testing
  port:
    targetPort: wconsj-0
  tls:
    insecureEdgeTerminationPolicy: Redirect
    termination: edge
  to:
    kind: Service
    name: artemis-broker-wconsj-0-svc
    weight: 100
  wildcardPolicy: None
status:
  ingress:
  - conditions:
    - lastTransitionTime: "2023-09-19T09:20:20Z"
      status: "True"
      type: Admitted
    host: my-route-artemis-broker-default.apps-crc.testing
    routerCanonicalHostname: router-default.apps-crc.testing
    routerName: default
    wildcardPolicy: None

I have no idea what's the problem. Please help. If you need more info please let me know.
Thanks

@ctml91 and I check the audit log and there seems to be no specific info regarding the route. Everything is pretty general.

Can you gather the logs again from the controller, etc.?
$ oc get issuers -n default
$ oc get certificaterequests -n default
$ oc describe certificaterequest <cr>
$ oc get events -n default
$ oc get events -n cert-manager
$ oc logs <cert-manager-route-controller> -n cert-manager
$ oc logs <cert-manager-controller> -n cert-manager

Hi
Here are the information I gathered.
$ oc get issuers -n default
(20)[23:22:08]@route$  oc get issuers -n default
NAME                        READY   AGE
selfsigned-issuer-ingress   True    11h

$ oc get certificaterequests -n default
(20)[23:22:17]@route$ oc get certificaterequests -n default
NAME                                    APPROVED   DENIED   READY   ISSUER                      REQUESTOR                                                          AGE
artemis-broker-wconsj-0-svc-rte-s5jd4   True                False   selfsigned-issuer-ingress   system:serviceaccount:cert-manager:cert-manager-openshift-routes   11h
my-route-artemis-broker-njg94           True                False   selfsigned-issuer-ingress   system:serviceaccount:cert-manager:cert-manager-openshift-routes   6h2m

$ oc describe certificaterequest
(20)[23:23:22]@route$ oc describe certificaterequests my-route-artemis-broker-njg94
Name:         my-route-artemis-broker-njg94
Namespace:    default
Labels:       <none>
Annotations:  cert-manager.io/certificate-revision: 1
API Version:  cert-manager.io/v1
Kind:         CertificateRequest
Metadata:
  Creation Timestamp:  2023-09-19T09:20:20Z
  Generate Name:       my-route-artemis-broker-
  Generation:          1
  Managed Fields:
    API Version:  cert-manager.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:cert-manager.io/certificate-revision:
        f:generateName:
        f:ownerReferences:
          .:
          k:{"uid":"1d98e663-18b5-4ce8-bf1c-b8521068370f"}:
      f:spec:
        .:
        f:duration:
        f:issuerRef:
          .:
          f:kind:
          f:name:
        f:request:
        f:usages:
    Manager:      Go-http-client
    Operation:    Update
    Time:         2023-09-19T09:20:20Z
    API Version:  cert-manager.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:conditions:
          .:
          k:{"type":"Approved"}:
            .:
            f:lastTransitionTime:
            f:message:
            f:reason:
            f:status:
            f:type:
    Manager:      cert-manager-certificaterequests-approver
    Operation:    Update
    Subresource:  status
    Time:         2023-09-19T09:20:20Z
    API Version:  cert-manager.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        f:conditions:
          k:{"type":"Ready"}:
            .:
            f:lastTransitionTime:
            f:message:
            f:reason:
            f:status:
            f:type:
        f:failureTime:
    Manager:      cert-manager-certificaterequests-issuer-selfsigned
    Operation:    Update
    Subresource:  status
    Time:         2023-09-19T09:20:20Z
  Owner References:
    API Version:           route.openshift.io/v1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Route
    Name:                  my-route-artemis-broker
    UID:                   1d98e663-18b5-4ce8-bf1c-b8521068370f
  Resource Version:        1060483
  UID:                     13169b94-65cc-4c79-a80f-6b09449c996a
Spec:
  Duration:  2160h0m0s
  Extra:
    authentication.kubernetes.io/pod-name:
      cert-manager-openshift-routes-5bfbc6fb88-75zvd
    authentication.kubernetes.io/pod-uid:
      7f3e6354-93c1-4911-9bda-be692822a411
  Groups:
    system:serviceaccounts
    system:serviceaccounts:cert-manager
    system:authenticated
  Issuer Ref:
    Kind:   Issuer
    Name:   selfsigned-issuer-ingress
  Request:  LS0tLS1CRUdJTiBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0KTUlJQ3B6Q0NBWThDQVFBd0ZERVNNQkFHQTFVRUF4TUpZWEpyWVcxeExtbHZNSUlCSWpBTkJna3Foa2lHOXcwQgpBUUVGQUFPQ0FROEFNSUlCQ2dLQ0FRRUF1ZG1VT244YzZLd0NLQitaSTR0S0JjVUIxaUpJM0JhZWg3Z09wVGNaCm1PbVlKM2NuWnErSDFsUTV4Y2RjOWM0dGtFRWNMc2NOT2xXWmlDVHBNbUtaRlhiUEp4cjhLNGc3cy9LYXNUQlkKOFh0bmtQVExWUWVkYU1pUnkxYUlKS1l4RTg4SW1VaC9ML2JZM2lRSWtVQTRSZWRlYWFURUUvQ1RGZSs4K3BPbQpUeUVIL1RhNGF0TkFmZkdibmh3SEtPeGp1TVczbjBlUHZIUDB0d1NGeHhSQStuNndISHpSRWZ0Y0RteW8zcnIxCk1HZk13d2gwN2pBcGhkWjNqRnJ6KzlnbHI2UFV3ZGlLMTRiQVlpUVJEcjk5UGFiTHRScXRBRHBYQnVLbUVyM1IKSW9KMFIxMFFZQytMRko4bDBqc3A0eVhkT2tQQU1UTjhjOWlMa2VzYm0xMElmd0lEQVFBQm9FNHdUQVlKS29aSQpodmNOQVFrT01UOHdQVEE3QmdOVkhSRUVOREF5Z2pCdGVTMXliM1YwWlMxaGNuUmxiV2x6TFdKeWIydGxjaTFrClpXWmhkV3gwTG1Gd2NITXRZM0pqTG5SbGMzUnBibWN3RFFZSktvWklodmNOQVFFTEJRQURnZ0VCQUY1WWxGN3AKck1Pc0RyNGd3SWw4eVJkY1N2bGQ3VzFzaGxqMTVXRkwwd2JMWXRwSG5FRE5Lb1ZrS0xXRmNlRlQyU25wb2JjMgp6UnFySUFZU3oxeThZejBGTHJLQ1EwVG9tbXFMQXNsc0RPZUt6ZGhXOWJnYkFOcW5IUmowajUwb2I2WjJ1dCtyCkJ6TENSWHVpY3pDaUFPUjNHVVFkL2J6VGtFU2ZyUFoybStjZlF3THZnUEUrc2gzWFBaSHpwNVlyRDhlenpLY24KVHpBREJHcXRRL1puc1liWkMxQUVrMEJBS1JuOEppb05ybXAxRTVFandtclB5eldIOTlSdW9vV0VTS2tsRExOVQpHVHRyT3lxb3Q1enUwSmlqYU5YeWswby9BZGxHaDF0QStuckNuZDhSLzBJT1NvUlcrMU9Ca0tOelFZTUp4bmNoClYxREFJZFNKTE1aY2hjRT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUgUkVRVUVTVC0tLS0tCg==
  UID:      0d32d56f-00fe-4f7c-affe-f1d01a5c6598
  Usages:
    server auth
    digital signature
    key encipherment
  Username:  system:serviceaccount:cert-manager:cert-manager-openshift-routes
Status:
  Conditions:
    Last Transition Time:  2023-09-19T09:20:20Z
    Message:               Certificate request has been approved by cert-manager.io
    Reason:                cert-manager.io
    Status:                True
    Type:                  Approved
    Last Transition Time:  2023-09-19T09:20:20Z
    Message:               Annotation "cert-manager.io/private-key-secret-name" missing or reference empty: secret name missing
    Reason:                Failed
    Status:                False
    Type:                  Ready
  Failure Time:            2023-09-19T09:20:20Z
Events:                    <none>

$ oc get events -n default
(20)[23:28:34]@route$ oc get events -n default
No resources found in default namespace.

$ oc get events -n cert-manager
(20)[23:29:09]@route$ oc get events -n cert-manager
No resources found in cert-manager namespace.

$ oc logs  -n cert-manager
oc logs cert-manager-openshift-routes-5bfbc6fb88-75zvd -n cert-manager > cert-manager-openshift-routes.log

$ oc logs  -n cert-manager
oc logs cert-manager-7cc7959fbb-w6fzk -n cert-manager > cert-manager.log

cert-manager.log
cert-manager-openshift-routes.log

Annotation "cert-manager.io/private-key-secret-name" missing or reference empty: secret name missing
I'm not sure what this annotation is for?

I just realized that openshift-routes is not compatible with cert-manager's SelfSigned issuer at the moment. The SelfSigned issuer requires the private key to be stored in a Secret resource and requires the special annotation cert-manager.io/private-key-secret-name to be present on the CertificateRequest.
Usually, cert-manager creates this annotation when it creates the CertificateRequest. But since openshift-routes is the one that creates the CertificateRequest and openshift-routes doesn't know that the issuer is the SelfSigned issuer, it doesn't add the annotation and doesn't create the Secret.
I think we need to mention this limitation in the README! 😅


MXRoom isDirect returns YES for rooms that are not direct

MXRoom objects may think that an instance is a direct room when in fact it is not.
(Present in Riot IOS using SDK 0.8.1, but not with SDK 0.7.11 or Riot Desktop)
How to replicate:
User A (riot desktop) creates a room (not a conversation, but a room) and invites only user B.
User B accepts the invitation (riot iOS). For user B, the room shows under people instead of Rooms.
User A invites user C. User C accepts (Riot iOS). User B still sees the room under People, and the MXRoom object of that particular room still returns YES when calling isDirect.
User C also sees the room under People.

@javierquevedo the behavior observed for the userB is the expected one. Because we implented the direct chat handling as it was described in https://github.com/vector-im/riot-web/issues/2099. The userB behavior is related to the fifth point When receiving an invite, we need to check if it's tagged as DM or not DM. If it's a DM, we add it to m.direct on account_data. If it has no tag at all, we'll have to apply heuristics to decide whether to consider it a DM (given it may have come from a client that doesn't know about m.direct).
As you can see, this point was not implemented on the web-client.
We are currently discussing on this point. I think we should remove this use case on mobile app.
About the userC, I have no explanation. I did not reproduce it. He should not see the room as direct. Maybe, this issue on userC will be fixed, if we remove the heuristic method on new joined room...

@giomfo I believe that the behaviour is not the expected one. To my knowledge when you "Create a Room" this should never be flagged as Direct. On the contrary, rooms created using the "Start Chat" button, should always be created as Direct. Hence, the behaviour is not the expected one. Right?

@javierquevedo I understand your point of view, and I agree with you. But this was not the requested implementation.
See my discussion with Dave: https://matrix.to/#/!tDRGDwZwQnlkowsjsm:matrix.org/$149874336611440LMrCc:matrix.org
Thank you for your report, we will have to discuss about this use case to harmonise all the client behaviour.


flutter_inappwebview.callhandler

Environment
Flutter version: 3.13.0
Plugin version:  flutter_inappwebview: ^6.0.0-beta.22
Description
How do I pre-inject flutter_inappwebview.callhandler

Some Vue pages need to get the local token at the start, which will prompt the callHandler undefined. Is it possible to inject a callHandler the first time a webview is created?


Deprecate u-hiddenVisually in labels

The .u- utility classes are being deprecated in version 3.0 of Citadel. In places where u-hiddenVisuallyis being used for labels, replace it with is-srOnly (behavior of this class hides the content to users, but is read out by assistive technology like screen readers).
@bc-miko-ademagic

Nice one 👍

@mickr @mcampa @hegrec - anyone have any complaints? i would like to merge this if possible.

👍

@bc-miko-ademagic @mcampa - can someone merge this in? I don't have access.


ggml_allocr_alloc: not enough space in the buffer

Issue description
When I pass the prompt greater than 1000+ tokens - it fails with ggml_allocr_alloc error.
Expected Behavior
Should allow to consume prompt size equals to model's context size.
Actual Behavior
AI: ggml_allocr_alloc: not enough space in the buffer (needed 308691360, largest block available 281657952)
GGML_ASSERT: /Users/pixelycia/Projects/node-llama-cpp/node_modules/node-llama-cpp/llama/llama.cpp/ggml-alloc.c:173: !"not enough space in the buffer"
zsh: abort      node-llama-cpp chat -m ./models/mistral-7b-openorca.Q5_K_M.gguf -c 8192
Steps to reproduce
I was able to reproduce error through the code and CLI:

node-llama-cpp chat -m ./models/mistral-7b-openorca.Q5_K_M.gguf -c 8192
Pass long prompt.

My Environment

Dependency
Version

Operating System
MacOS Sonoma 14.0

Node.js version
v18.18.0

Typescript version
5.1.3

node-llama-cpp version
^2.5.1

Additional Context
I compiled latest llama.cpp and from original repository - it works perfectly fine.
Tried to clear \ re-download \ re-build with the build-in CLI tool "node-llama-cpp" with different releases \ metal \ no-metal support - fails with error all the time.
Relevant Features Used

[X] Metal support
[ ] CUDA support
[ ] Grammar

Are you willing to resolve this issue by submitting a Pull Request?
Yes, I have the time, but I don't know how to start. I would need guidance.

@Pixelycia As far as I've seen, the model you mentioned here doesn't support a context length of 8192.
Try decreasing it to 2048 and it shouldn't fail then.

@Pixelycia As far as I've seen, the model you mentioned here doesn't support a context length of 8192.
Try decreasing it to 2048 and it shouldn't fail then.

https://huggingface.co/Open-Orca/Mistral-7B-OpenOrca - 8k context, anyway different models with smaller context fail on 1000+ tokens as well

@Pixelycia I think it has something to do with how you convert the models to GGUF.
I'm using pre-converted models by The Bloke on Hugging Face with long context without any problem.
Does your Mac has an Intel chip or an Apple silicone chip?
Also, how much RAM does your machine have?

@Pixelycia I think it has something to do with how you convert the models to GGUF. I'm using pre-converted models by The Bloke on Hugging Face with long context without any problem. Does your Mac has an Intel chip or an Apple silicone chip? Also, how much RAM does your machine have?

Apple Silicon, M1, 32 GB RAM, I used different Bloke's GGUF models, no luck.
There is a difference I noticed how llama.cpp reacts on request and how this library. It look's like llama.cpp allocate space in RAM with batches (I can see my request appear in console sliced with delay), but this lib seems tries to allocate entire space at once.

@Pixelycia I have M1 Max with 32GB RAM and it works for me.
Can you please give me specific instructions on how to reproduce this issue?
For example, what specific model by The Bloke to get, how to load it and what text to prompt it with. Please do this on the latest version of node-llama-app.
Also, does it still happen to you with version 2.7.0?
I've updated the code to use a new llama.cpp interface that works differently than how it used to.
The delay you notice may be because only after you send the initial prompt to a LlamaChatSession, node-llama-cpp starts evaluating the system prompt and everything else that precedes your prompt.

@giladgd sorry for the delay in response, I'll do more tests and return to you

@giladgd the error mentioned in the ticket gone, so we can close it, but probably I still do not understand something, if I put the long prompt in a fresh session context (bigger than a batch size) - it writes to me:
GGML_ASSERT: /Users/runner/work/node-llama-cpp/node-llama-cpp/llama/llama.cpp/llama.cpp:5746: n_tokens <= n_batch

and indeed it's true. To make my prompt work I need to increase batch size, that going to be bigger that the prompt or just equals to the context size. But why I should do it? What I'm doing wrong?
I'm trying to use the library not only in a chat mode, but in an instruction mode as well, i.e. I want to send an instruction with a big context and get a response in a single shot (for example I can recreate session on each prompt or implement different type of session class).
P.S. I used random TheBloke's model https://huggingface.co/TheBloke/MistralLite-7B-GGUF
P.S.2. I used code from the example:
import { fileURLToPath } from "url"
import path from "path"
import { LlamaChatSession, LlamaContext, LlamaModel } from "node-llama-cpp"

const __dirname = path.dirname(fileURLToPath(import.meta.url))

const model = new LlamaModel({
  modelPath: path.join(__dirname, "server/models", "mistrallite.Q5_K_M.gguf"),
})
const context = new LlamaContext({ model, contextSize: 4096, batchSize: 512 }) // Increate batchSize to 4096 to make it work
const session = new LlamaChatSession({ context })

const q1 = `...`

const a1 = await session.prompt(q1)
console.log("AI: " + a1)

@Pixelycia The context size is the number of tokens the model can be aware of at once for generating a new token, and the batch size is the number of input tokens that can be processed on a single "GPU process" (this is an oversimplification to make it easier to understand).
I'm currently working on making the experience more seamless so you won't have to configure any of those, and everything will just work as you expect it to, but it's not ready yet.
Still, the current implementation is more tightly coupled with llama.cpp's implementation, so in practice, you can only evaluate <batch size> amount of tokens at once.
Setting the batch size to be the same as the context size should suffice for your use case with the current version of node-llama-cpp.


POC issue

where should I get this "[POC][G][GET][BUILTIN]" I want to see the results, and what it does.
because this is not an XSS vulnerability, I want to run only XSS finding, check my command and let me know.

@hahwul please check the aforementioned issue and respond ASAP


fix(model-datastructure): fix LinearHistory

I think, I have got something. The idea is to order the merges by ID and distance from the base version, but keep all normal versions between merges linearly as they appeared. bf502cf is a WIP, I'm going to clean up and document the code.

:tada: This PR is included in version 3.16.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


how can i import Promise

Hello ,I want to import Promise. But I don't want to use typing. how can I use?

Promise are part of ES2015 standard. if you want to use them in ES5 env you need a polyfill like this one


Export as javascript array with key:pair value

How to export the hashmap into single javascript array to be passed on to server side?

I think what you want is something like this:
var items = [];
map.forEach(function(value, key) {
  items.push({key:key, value:value});
});
// Send items to server


Download or share Directory from Lighting App Drive with external tool

🚀 Feature
Would be useful to make the artifacts available via

download dir or
download subdir or
files via regular expression match.
provide s3 link so that I don't have to download the artifacts it needs to be shared with another tool

The download could be to my file system or sent remote location such as an s3 bucket.
Motivation

I could have many experiments, and downloading one file at a time is very time-consuming.  The picture below shows many files that have to be individually downloaded one at a time.
The artifact can be uploaded to the cloud storage of my choice -- in case the artifact size is big
I need to make the artifact to another tool that is not an Lighting App
I need to make the artifact available to Another Lightning App

Pitch
Make the output of the application available that is not this Lightning App.
Alternatives
Additional context
cc @borda

It would also be nice if the Drives could be shared between applications. A user would like to have a trainer app that would only save check point and different deployment application that wraps these checkpoints around an API and a different app to test it with streamlit.


Optimize CI visual regression snapshotting

🛠 Summary of changes
Adjusts continuous integration workflow to optimize visual regressions.
Specifically:

Ensure that parallelized page are closed once completed to avoid memory leak
Avoid using networkidle0, which effectively incurs a sleep(500ms) (docs)
Avoid unnecessary NPM package build and limit build to documentation site

Parallelize tasks for building documentation site

Avoid creating an Incognito browsing context, which seems to incur a noticeable start-up cost, and should hopefully not be necessary anymore with changes in #403 and https://github.com/18F/identity-design-system/pull/402#issuecomment-1915477963

Performance Impact
On average, this should save upward of 10 seconds from the "visual_regression" workflow.
See snapshot-branch and snapshot-main timings in below builds:

Before (min 46s, max 46s)
After (1) (min 32s, max 37s)
After (2) (min 36s, max 39s)
After (3) (min 36s, max 46s)
After (4) (min 33s, max 36s)

📜 Testing Plan
Verify build passes.

Noting for future reference that running the snapshotting with a single page in series (70d3a7eab0b7430900f5fa7cad6ad2c2ebf3bf51) seemed to be quite performant as well. I expect that the parallelization starts hitting some bottlenecks when trying to create so many pages in parallel, and there's some benefit in limiting the concurrency, maybe with one or a few dedicated "page" instances, and maybe with a library that could help simplify this (e.g. p-map). I didn't go too far down this rabbit-hole since I've started hitting diminishing returns with these changes, but something to look at in the future if performance becomes a concern.


Setting visual shader type to 'CanvasItem' crashes the editor

Godot version:
master / cfcb6e11f25ad
OS/device including version:
Manjaro Linux 17.1
Issue description:
When creating a visual shader material for a control, switching the mode to CanvasItem crashes the editor.
However, if you open the visual shader editor first (with mode set to Spatial) and change the mode to CanvasItem later, it seems to work as expected.

win64
confirmed


[Enum Request] MatrixPeriodType

Please provide an new "MatrixPeriodType" Enum with these valeus:
Day,Week,Month,Quarter,Year,"Accounting Period"
In the Base Application this Options are mostly referenced as PeriodType-Variable.
Since many Partners using the same option in there matrix pages it would be useful when we could all use the same enum.
I think extensibility is not Required at this Time.

This is large rework for many pages and global procedures (100+ objects). Not sure we should spend resources for this work now. Probably we can simply add this enum without reworking of existing objects as pattern for new partners? What do you think?

That would be fine for me.
A complete rebuild of the solution wouldn't be that tragic i think . you only have to change from option to enum everywhere. afaik you don't even need a mapping to other enums. But you are right: the number of touched objects would be high.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Support for gRPC compression

Provide a minimal implementation of compression using gzip (which is supported in Go providing a popular interoperability target). There is a general spec outlining how compression should work https://github.com/grpc/grpc/blob/master/doc/compression.md. The decompress library looks promising, it provides gzip and zlib plus it is fairly popular and implemented in pure OCaml.
Bonus feature would be to design an API such that compression is extensible and library users can provide their own compression algorithms.

I tried using a service with grpcurl but the underlying library it uses by default sends a grpc-accept-encoding: gzip header. This results in the error 406 (Not Acceptable); malformed header: missing HTTP content-type due to the check here https://github.com/dialohq/ocaml-grpc/blob/e066812702d4c2221fe85d39d1a78305ea7d7361/lib/grpc-eio/server.ml#L39.
According to https://grpc.io/docs/guides/compression/#compression-method-asymmetry-between-peers, in the case of an unsupported compression type, an unimplemented error should be returned. https://github.com/grpc/grpc-go/blob/5051eeae537cb2839dd499e1a63a141098a3a03a/server.go#L1316.
As for the compression itself, I took a stab at it and got it partly working, decompressing an inbound body https://github.com/dialohq/ocaml-grpc/compare/main...joprice:ocaml-grpc:gzipSupport?expand=1#diff-2592ab6cc5a62541ce6f428cc52bed5bc738dbbdfbb6be87042a0fb5bfe390b2R56. That branch also has the Unimplemented response on it, along with some other local changes I had made for error handling that I can clean up if this general approach makes sense.

That would be great @joprice this library should interop correctly against other implementations.
Have a look at the Typed RPC PR https://github.com/dialohq/ocaml-grpc/pull/55 that should be the new API going forward.
You might also be interested in https://github.com/tmcgilchrist/ocaml-grpc/tree/fixes which has the initial support for running tests against the Go gRPC bindings. That is what I would eventually like to have but as your found out there are plenty of corner cases where ocaml-grpc doesn't do the right thing.

I'll check both of those out. I actually just got the full end to end working  https://github.com/dialohq/ocaml-grpc/compare/main...joprice:ocaml-grpc:gzipSupport?expand=1#diff-2592ab6cc5a62541ce6f428cc52bed5bc738dbbdfbb6be87042a0fb5bfe390b2R49-R69.
I added a codec type and the negotiation of client and server encodings. It combings the two together into a new codec to support asymmetric encoding. I added a parameter to the server v builder function that takes in a list of supported compression implementations. The implementations could be moved to separate libraries to avoid having to build things unnecessarily, and since it's just a record of functions, you can provide your own implementation easily.

Here's some more docs I found on compression. The last one looks especially useful as it has some nice flowcharts that can be used to validate the implementation.

https://grpc.github.io/grpc/cpp/md_doc_compression.html
https://grpc.io/docs/guides/compression/
https://github.com/grpc/grpc/blob/master/doc/compression_cookbook.md


Merge test to stable v0.9.24-rc3

Revert because the pull request was merged before Travis had run, thus causing Travis to fail.
Log from Travis:
4.03s$ git fetch origin +refs/pull/373/merge: --quiet
fatal: Couldn't find remote ref refs/pull/373/merge
The command "eval git fetch origin +refs/pull/373/merge: --quiet " failed. Retrying, 2 of 3.
fatal: Couldn't find remote ref refs/pull/373/merge
The command "eval git fetch origin +refs/pull/373/merge: --quiet " failed. Retrying, 3 of 3.
fatal: Couldn't find remote ref refs/pull/373/merge
The command "eval git fetch origin +refs/pull/373/merge: --quiet " failed 3 times.
The command "git fetch origin +refs/pull/373/merge: --quiet" failed and exited with 128 during .
Your build has been stopped.

For a similar problem, see:
https://github.com/hpi-swa/smalltalkCI/issues/84


Can I turn off depth_from_visual_hull?

https://github.com/autonomousvision/differentiable_volumetric_rendering/blob/1ea03f36ebcfb8995c06f9ddb83a00593ae1d5f4/configs/single_view_reconstruction/multi_view_supervision/ours_rgb.yaml#L9
Hi, I am training single view image prediction from multiview supervision on NMR dataset. I notice that it needs to load the depth hull. I wonder how important it is? Can I turn off it, training purely from images?
Thank you!

Hi @wenzhengchen , thanks a lot for your interest in our project!
Yes, in our single-view reconstruction experiments with L_rgb, we use the depth of the visual hull for the Occupancy Loss. Please have a look at our paper at 3.4 Training - Occupancy Loss:
"In the single-view reconstruction experiments,  we instead use  the  first  point  on  the  ray  which  lies  inside  all  object masks (depth of the visual hull). If we have additional depth supervision,  we  use  the  ground  truth  depth  for  the  occupancy loss."
This loss encourages occupancy along the ray if we don't predict a surface point there, but the GT is occupied. By using the visual hull depth, it basically starts with a better estimate - please note that it further uses the L_rgb loss to improve over the visual hull (see e.g. Fig. 7).
We didn't do an ablation study on this - I suspect that training might take longer if you disable this, and it might also degrade results - but we have no comparison on this.
I hope this helps. Good luck with your research!

Thank you so much! It really helps :)


HSEARCH-4253 JSON-format Elasticsearch mapping templates on the application side

https://hibernate.atlassian.net/browse/HSEARCH-4253
https://hibernate.atlassian.net/browse/HSEARCH-4234

Full build: https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/detail/PR-2665/3/pipeline

I just updated the request with a small fix and the rebase on top of the current master.
I still need to address all the comments.

A full build to check this few changes: https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/detail/PR-2665/5/pipeline


Upgrade to 5.18

Is it possible to upgrade the .deb kernels to 5.18.3 or higher?
Thanks

Ok great. Thanks

New kernel is built, but I need to test on my hardware and make sure everything is legit.

Ok great. Thanks. Let me know when is ready so I can test it as well.

@giovannicaligaris Deb packages are live in the 1.1.0 PR branch: https://github.com/gnickm/sof-essx8336-debian-fix/tree/version/1.1.0/dist

I installed and the sound card is detected. After running setup-pulseaudio.sh I can hear a crackling sound when the tablet powers on and thats about it. No sound after that. I tried disabling the pulseaudio setup and I get the same result.
Very close now, but I am not sure what it could be.

sudo dmesg | grep sof
[sudo] password for mobian:
[    1.019790] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    1.019793] software IO TLB: mapped [mem 0x00000000694fe000-0x000000006d4fe000] (64MB)
[    4.385777] xor: measuring software checksum speed
[    5.096151] Modules linked in: rtsx_usb(+) btrfs blake2b_generic xor sd_mod t10_pi crc64_rocksoft crc64 crc_t10dif crct10dif_generic uas usb_storage raid6_pq zstd_compress libcrc32c crc32c_generic hid_generic usbhid hid i915 drm_buddy i2c_algo_bit drm_dp_helper spi_pxa2xx_platform dw_dmac dw_dmac_core cec mmc_block rc_core ahci ttm libahci drm_kms_helper libata xhci_pci xhci_hcd drm sdhci_pci scsi_mod usbcore cqhci sdhci i2c_i801 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel mmc_core i2c_smbus intel_lpss_pci scsi_common intel_lpss idma64 usb_common wmi battery video pinctrl_jasperlake button
[   13.380855] sof-audio-pci-intel-icl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[   13.380983] sof-audio-pci-intel-icl 0000:00:1f.3: enabling device (0000 -> 0002)
[   13.381255] sof-audio-pci-intel-icl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[   13.381392] sof-audio-pci-intel-icl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   13.388454] sof-audio-pci-intel-icl 0000:00:1f.3: use msi interrupt mode
[   13.450141] sof-audio-pci-intel-icl 0000:00:1f.3: NHLT_DEVICE_I2S detected, ssp_mask 0x1
[   13.450150] sof-audio-pci-intel-icl 0000:00:1f.3: hda codecs found, mask 4
[   13.481723] sof-audio-pci-intel-icl 0000:00:1f.3: firmware: direct-loading firmware intel/sof/sof-jsl.ri
[   13.481737] sof-audio-pci-intel-icl 0000:00:1f.3: Firmware info: version 2:1:1-3964a
[   13.481739] sof-audio-pci-intel-icl 0000:00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:19:1
[   13.481741] sof-audio-pci-intel-icl 0000:00:1f.3: warn: FW ABI is more recent than kernel
[   13.481749] sof-audio-pci-intel-icl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[   13.585078] sof-audio-pci-intel-icl 0000:00:1f.3: Firmware info: version 2:1:1-3964a
[   13.585086] sof-audio-pci-intel-icl 0000:00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:19:1
[   13.585088] sof-audio-pci-intel-icl 0000:00:1f.3: warn: FW ABI is more recent than kernel
[   13.670488] sof-essx8336 sof-essx8336: quirk mask 0x0
[   13.670495] sof-essx8336 sof-essx8336: quirk SSP0
[   13.722791] sof-audio-pci-intel-icl 0000:00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-jsl-es8336-ssp0.tplg
[   13.722813] sof-audio-pci-intel-icl 0000:00:1f.3: Topology: ABI 3:20:0 Kernel ABI 3:19:1
[   13.722817] sof-audio-pci-intel-icl 0000:00:1f.3: warn: topology ABI is more recent than kernel
[   13.723073] sof-essx8336 sof-essx8336: ASoC: Parent card not yet available, widget card binding deferred
[   13.830283] sof-essx8336 sof-essx8336: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
[   13.830290] sof-essx8336 sof-essx8336: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4
[   13.850061] input: sof-essx8336 Headset as /devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0/input18
[   13.850124] input: sof-essx8336 HDMI/DP,pcm=5 as /devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0/input19
[   13.850177] input: sof-essx8336 HDMI/DP,pcm=6 as /devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0/input20
[   13.850228] input: sof-essx8336 HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0/input21

[ 13.722791] sof-audio-pci-intel-icl 0000:00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-jsl-es8336-ssp0.tplg
[ 13.723073] sof-essx8336 sof-essx8336: ASoC: Parent card not yet available, widget card binding deferred
Ugh, same issue as in #2 . You have a board that isn't supported by the sof yet.
Found an interesting message just now about why ES8336 support sucks so bad in linux<EMAIL_ADDRESS>As I suspected these chips were developed specifically for Windows.

@gnickm It is working on Manjaro for some reason. I wonder if they patched something

On Manjaro
sudo dmesg | grep sof
[sudo] password for manjaro:
[    1.169687] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    1.169690] software IO TLB: mapped [mem 0x000000006997f000-0x000000006d97f000] (64MB)
[    6.758550] sof-audio-pci-intel-icl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    6.758723] sof-audio-pci-intel-icl 0000:00:1f.3: enabling device (0000 -> 0002)
[    6.759208] sof-audio-pci-intel-icl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[    6.759542] sof-audio-pci-intel-icl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    6.768454] sof-audio-pci-intel-icl 0000:00:1f.3: use msi interrupt mode
[    6.814964] sof-audio-pci-intel-icl 0000:00:1f.3: NHLT_DEVICE_I2S detected, ssp_mask 0x1
[    6.814983] sof-audio-pci-intel-icl 0000:00:1f.3: hda codecs found, mask 4
[    6.823771] sof-audio-pci-intel-icl 0000:00:1f.3: Firmware info: version 2:1:1-3964a
[    6.823783] sof-audio-pci-intel-icl 0000:00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:19:1
[    6.823789] sof-audio-pci-intel-icl 0000:00:1f.3: warn: FW ABI is more recent than kernel
[    6.823804] sof-audio-pci-intel-icl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[    6.924390] sof-audio-pci-intel-icl 0000:00:1f.3: Firmware info: version 2:1:1-3964a
[    6.924408] sof-audio-pci-intel-icl 0000:00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:19:1
[    6.924416] sof-audio-pci-intel-icl 0000:00:1f.3: warn: FW ABI is more recent than kernel
[    6.973812] sof-essx8336 sof-essx8336: quirk mask 0x0
[    6.973825] sof-essx8336 sof-essx8336: quirk SSP0
[    6.981739] sof-audio-pci-intel-icl 0000:00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:19:1
[    6.981751] sof-audio-pci-intel-icl 0000:00:1f.3: warn: topology ABI is more recent than kernel
[    6.982076] sof-essx8336 sof-essx8336: ASoC: Parent card not yet available, widget card binding deferred
[    7.069796] sof-essx8336 sof-essx8336: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3
[    7.069809] sof-essx8336 sof-essx8336: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4
[    7.087922] input: sof-essx8336 Headset as /devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0/input13
[    7.088065] input: sof-essx8336 HDMI/DP,pcm=5 as /devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0/input14
[    7.088173] input: sof-essx8336 HDMI/DP,pcm=6 as /devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0/input15
[    7.088272] input: sof-essx8336 HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0/input16

@giovannicaligaris Weird, I thought the Parent card not yet available meant it didn't work... What does aplay -l and arecord -l give you?

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofessx8336 [sof-essx8336], device 0: ES8336 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofessx8336 [sof-essx8336], device 5: HDMI 1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofessx8336 [sof-essx8336], device 6: HDMI 2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofessx8336 [sof-essx8336], device 7: HDMI 3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Good news, I figured out!
For some reason your setup-sof.sh script messes something up with the sof folders.
I started from scratch and all I did was install your custom kernel and install firmware-sof-signed on Debian. Restarted and then on the terminal type alsamixer and with F6 selected the sof sound card. Increased all the volumes and now there is sound!
Thanks a lot man. Your kernel now makes my tablet usable.

apt-cache policy firmware-sof-signed
firmware-sof-signed:
  Installed: 2.1.1-1
  Candidate: 2.1.1-1
  Version table:
 *** 2.1.1-1 500
        500 http://deb.debian.org/debian bookworm/non-free amd64 Packages
        500 http://deb.debian.org/debian unstable/non-free amd64 Packages
        100 /var/lib/dpkg/status

Actually, setup-alsa.sh has to be run at least once.

Can you show me how you built the kernel?

Can you show me how you built the kernel?

@giovannicaligaris https://github.com/gnickm/sof-essx8336-debian-fix/blob/version/1.1.0/build-kernel.sh

@gnickm which file did you add CONFIG_SND_SOC_INTEL_SOF_ES8336_MACH=m


Branch: shooterHopperFix

Useful Information

What version of Python are you using? Which OS?

Fixed in #94


Added API of Pixel Encounter

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

https://pixelencounter.com/Api

Thanks for the contribution @XzaR90!


Bug Icon functions should be split up

The bug icon contains a number of functions, which might be more easily found by users, if they are split up and some of them added to a new download icon.
For example, the bug icon could contain these items:

Reset your local view state and reload the page (I could argue that this could go right on the toolbar)
Report a bug (and this could actually go on a support type page with a field for user input -maybe on settings)

Add a download icon

to include these items:

Save raw data as JSON
Save canvas as SVG (does not include search highlighting)

In my mind a JSON file or an SVG may not be about troubleshooting.  Perhaps a user wants to pipe his JSON to another app or maybe he wants to just send the SVG to another user without inviting them to the instance.

closed https://github.com/weaveworks/service-ui/issues/416#issuecomment-297406233

Still an issue. But see considerations of why it was put there in #2080


Portfolio remove naa n

Fixed the NaaN issue. Prompt user to sign in when wallet is not connected.

Again, cherry picking these changes into main! TY


TapableLabel doesn't respond to tap delegate when matched string is neither phone number or link.

I am trying to underline and highlight a certain text and use tapableLabel. However when I set cuteAttributes to certain text in the label and desire to tap it, it doesn't call the delegate method despite the label being the delegate of the view controller. Please let me know what I am doing wrong.

Hello @mohsinka , is indicatorLbl frame's height equal to content height?

Hello @mohsinka , could you provide a screenshot for indicatorLbl's constraints in Storyboard?

Hello, could you remove the height constraint and try ?

Awesome! It did the trick for me. Thank you so much!

Hi @mohsinka, I make it that it will response to tap action whether you had set the height constraint for label or not. 😃

@qiuncheng cool, i'll take the update and check :)


DOC: show the escape backslash

Before this PR, the char doesn't render:

I tested that there are no further shenanigans with backquotes:

Codecov Report

Merging #2144 (2d0d326) into main (2e10901) will increase coverage by 0.00%.
Report is 1 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main    #2144   +/-   ##
=======================================
  Coverage   94.29%   94.30%
=======================================
  Files         320      320
  Lines       61947    61947
=======================================
+ Hits        58416    58417    +1
+ Misses       3531     3530    -1

Files Changed
Coverage Δ

src/query/query_parser/query_parser.rs
92.82% <ø> (ø)

... and 1 file with indirect coverage changes


timezone error

the time returned was correct.

the time returned [ RowDataPacket {  '@@global.time_zone': '+08:00',  '@@session.time_zone': '+08:00',  'now()': 2017-03-24T03:03:14.000Z } ] was wrong.

import mysql from 'mysql';
import Connection from 'mysql/lib/Connection';
import Promise from 'bluebird';
import config from './config';

Promise.promisifyAll([Connection], {multiArgs: false});
const conn = mysql.createConnection({
  host     : config.mysql_addr,
  port     : config.mysql_port,
  user     : config.mysql_user,
  password : config.mysql_passwd,
  database : config.mysql_db,
  timezone : '+08:00'
});
conn.connect();

conn.queryAsync('select @@global.time_zone, @@session.time_zone, now();').then((data) => {
  console.log(data);
});
export default conn;

when i change the timezone to 08:00, then the returned time was correct.

I'm puzzled now .... who can help me? Thanks!

i run it on ubuntu 16.04.

@buddy-yao  The behavior looks correct to me. I think you are finding that the serialized date does not match the date returned from MySQL command line client. That is to be expected as the serialized representation calls toJSON() on the date object which is internally uses toISOString(). If that serialized date is used to create a new javascript Date object on a client in the same time zone as the server, the date will match what you see from your direct query to MySQL.
Perhaps a fiddle will help:
http://jsfiddle.net/buckbito/qpfxv01q/7/
Date.prototype.toJSON(): https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toJSON

@bbito Thank you very much! But I have to  invoke toLocalString() method manually. So, what's the usage of connection option timezone? Is it useless?

Hi @buddy-yao I guess what @bbito said explains why I wasn't seeing your issue: you were actually referring to the way in which JavaScript stringifies dates, nothing this module does. The point of the timezone option is because the JavaScript Date objects understand the offset the date belongs to (for .toLocalString() to function for example), and the MySQL protocol responses include no time zone information. Thus the timezone option is how you tell this module what time zone those are in so it can then construct the Date object correctly.

thanks

I had this problem too, so what are the conclusions and solutions?


upload docker image

keep the docker images as artefacts for each master build

Upload to where?

github actions as build artefacts, as we don't want every master build being published to a container registry

added moac but I still need to stop the images being built for every pull request

Why are we building moac on every build now rather than only when the files change? What are we trying to do exactly, there is not much information in the jira... (eg when to upload the images, every PR, every build, release branch?)

At the moment we just want the images to be uploaded on master, i have now addressed that issue with an if statement in the image.yaml file.

Why are we building moac on every build now rather than only when the files change? What are we trying to do exactly, there is not much information in the jira... (eg when to upload the images, every PR, every build, release branch?)

At the moment we just want the images to be uploaded on master, i have now addressed that issue with an if statement in the image.yaml file.

Can we not keep the old moac yaml and avoid building moac and the image everytime? Takes extra 12 minutes to do it which isn't massive, but less would be better :)

Why are we building moac on every build now rather than only when the files change? What are we trying to do exactly, there is not much information in the jira... (eg when to upload the images, every PR, every build, release branch?)

At the moment we just want the images to be uploaded on master, i have now addressed that issue with an if statement in the image.yaml file.

Can we not keep the old moac yaml and avoid building moac and the image everytime? Takes extra 12 minutes to do it which isn't massive, but less would be better :)

It's done in parallel to the other jobs  :slightly_smiling_face:


[TASK] Clean up the code with Rector

Just the Rector changes, and some reundancy removal related to those, but nothing more.

coverage: 38.583% (-0.04%) from 38.622%
when pulling 43e100d73098e6386a6aa4e5d71c38566cb72927 on cleanup/rector
into b56f7c6976379575a8ee179e6d1aeee49037f2e7 on main.


chore: migrate dev environment to nodejs22

Summary
Changes

Please provide a summary of what's being changed

This PR adds support for Node.js 22 and switches the development environment to the same version.
Todos:

[x] Manually update aws-cdk and aws-cdk-lib in the workspace
[x] Update default runtime for e2e tests here
[x] Add new runtime key/val here
[x] Remove the patch added here
[x] Run the e2e tests again

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: #3246

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

e2e tests for this branch are green https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/11938706833

Amazing work @dreamorosi! Approved!


moved jest config to package.json ; Add to SDK test coverage

Still in draft
Description of changes proposed in this pull request:

Moved jest config options into package.json (that way we are 100% typescript ✔ )
Working on adding to the test suite

Checks:

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submission:

[ ] Have you successfully ran tests with your changes locally?
[ ] Have you lint your code locally prior to submission?

Changes to Existing Features:

[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, if applicable?

I suggest you either close this pr or you merge restructure first into this branch to avoid any conflicts.
I think almost everything changed and your feedback has been implemented. The only think that I have not added is the jest.config part of your pr. Since I think we don't need jest anyway, I propose to completely remove it for now.
What do you think @ElmoArmy?

I suggest you either close this pr or you merge restructure first into this branch to avoid any conflicts.
I think almost everything changed and your feedback has been implemented. The only think that I have not added is the jest.config part of your pr. Since I think we don't need jest anyway, I propose to completely remove it for now.
What do you think @ElmoArmy?

Definitely will go with closing and take a look at the refactor. Thanks for the update.


The pod ring text is misleading for DaemonSet resource

Describe the bug
The pod ring text on the DaemonSet resource node shows "Scaled to 0" when there are 2 pods running
To Reproduce

Create a DaemonSet resource with the below yaml:

kind: DaemonSet
apiVersion: apps/v1
metadata:
  name: example
  labels:
    backstage.io/kubernetes-id: <entity-name>
spec:
  selector:
    matchLabels:
      app: httpd
  template:
    metadata:
      labels:
        app: httpd
        backstage.io/kubernetes-id: test-backstage
    spec:
      containers:
        - name: httpd
          image: >-
            image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest
          ports:
            - containerPort: 8080
              protocol: TCP
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: Always
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      dnsPolicy: ClusterFirst
      securityContext: {}
      schedulerName: default-scheduler
  updateStrategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 1
      maxSurge: 0
  revisionHistoryLimit: 10

Wait for the pods to be up and running

Expected behavior
The pod ring text should show the correct pod info
Screenshots

Additional context
NA

I am working on a feature that adds visualization of the DeamonSets on Topology, so I will handle this as part of my PR


Hallucinations in chapter title generation after some time

Hello, First of all, thank you for an awesome project and making source code and models available. I really appreciate it.
I was able to run the demo_asr.py and demo_vid2seq.py. I tested HowTo100M + VidChapters-7M + YouCook2 and VidChapters-7M models with it.
On a few videos I tested, VidChapters-7M seems to work better. However, after some time, it starts to repeat the chapter name for rest of the video. I know its not using ChatGPT behind the scene, and term Hallucination is not a perfect fit for the title.
Here is an example:
input video: https://www.youtube.com/watch?v=jARPzYkjp3g
output:
[
    {'sentence': 'The four pillars of happiness.', 'timestamp': [0.0, 14.901636363636365]},
    {'sentence': 'The four pillars of happiness.', 'timestamp': [14.901636363636365, 69.5409696969697]},
    {'sentence': 'Belonging.', 'timestamp': [69.5409696969697, 94.37703030303031]},
    {'sentence': 'Purpose.', 'timestamp': [94.37703030303031,<PHONE_NUMBER>939394]},
    {'sentence': 'Religion.', 'timestamp': [139.0819393939394,<PHONE_NUMBER>4242423]},
    {'sentence': 'Fast casual restaurants.', 'timestamp': [173.85242424242423,<PHONE_NUMBER>1212123]},
    {'sentence': 'The sacramento.', 'timestamp': [213.59012121212123,<PHONE_NUMBER>3939395]},
    {'sentence': 'The sacramento.', 'timestamp': [243.39339393939395,<PHONE_NUMBER>4545453]},
    {'sentence': 'The sacramento.', 'timestamp': [268.22945454545453,<PHONE_NUMBER>151515]},
    {'sentence': 'The sacramento.', 'timestamp': [307.9671515151515,<PHONE_NUMBER>6363634]},
    {'sentence': 'The sacramento.', 'timestamp': [342.73763636363634,<PHONE_NUMBER>1212124]},
    {'sentence': 'The sacramento.', 'timestamp': [377.50812121212124,<PHONE_NUMBER>3939395]},
    {'sentence': 'The sacramento.', 'timestamp': [407.31139393939395,<PHONE_NUMBER>6666666]},
    {'sentence': 'The sacramento.', 'timestamp': [437.11466666666666,<PHONE_NUMBER>727273]},
    {'sentence': 'The sacramento.', 'timestamp': [461.9507272727273,<PHONE_NUMBER>1515156]},
    {'sentence': 'The sacramento.', 'timestamp': [471.88515151515156, 491.754]}
]

Another example:
Input: https://www.youtube.com/watch?v=PRpr0_Iz4dI
Output:
[
	{'sentence': 'Intro.', 'timestamp': [0.0, 7.774242424242424]},
	{'sentence': 'Why we hate the new logos.', 'timestamp': [7.774242424242424,<PHONE_NUMBER>6363636]},
	{'sentence': 'Why people are missing the bigger picture.', 'timestamp': [116.61363636363636,<PHONE_NUMBER>4545453]},
	{'sentence': "Why people aren't logical.", 'timestamp': [174.92045454545453,<PHONE_NUMBER>6363635]},
	{'sentence': "Why people aren't logical.", 'timestamp': [244.88863636363635,<PHONE_NUMBER>9999993]}
]

Do you know if I can do something to improve it a little?

Hey, I guess the easiest short-term fix is merging the repeated chapters but I haven't tried that extensively.

@antoyang Thank you for the reply. I tried this, and is not very good. It leaves more than ~50% of the video with the same chapter at the end.
I currently settled on the following approach:

Chapterize
Detect if hallicunations are present (search for chapter titles from bottom to top).
If they are, create a different video from where hallucination started.
Chapterize second part of the video
Merge chapters (add split time to all the times of the second parts' chapters).

This somewhat works. However another issue is that models are highly sensitive to visual features. Splitting video just 10 sec apart gives 100% different results. I did not expect this.
Most likely, I am going to use something different to solve my problem.

@iUnknownAdorn could you please share the code of your solution to the hallucination problem? And what else did you use to solve it?


Models can have multiple modes of operation

For example, a "KMeans clustering model can predict target labels but also transform to reduce dimension of the original space."

Was fixed in bbd7a43cb59d24bbd3dca770d4e7980230cb672b.


Fix incorrect default value for timeout_ms

We just discovered that timeout_ms defaults to 3000 instead of 5000. This PR fixes that problem and cleans up some stray whitespace.

Good catch, thanks!


improve multiline support

Multiline command support is currently even worse than bash...
In readline, if I go to a second line, it starts a prompt for the second line, on which I can't go back to the first line.
Here, when I go to a second line, and I press arrow up, it just  clears all lines and goes back to the previous command...

A temporary fix for this has been implemented in commit 035605e706021481f5853a6873cbd175584794b0. I'll keep this issue open for now, as this isn't a great fix.


Template document replicated in documents list

All of the templates in the included screenshot are the same document ( and link to the same page )

Fixed in ab16c8ff4f566558bd5b1425d890ab0535859f0e


TypeScript compilation issues

Hey @hdeshev,
I’m going through the installation instructions, but the TypeScript compilation seems to be failing. Specifically when I run grunt ng-sample I get the following error:
Running "ts:build" (ts) task
Compiling...
Using the custom compiler : node_modules/typescript/bin/tsc
/Users/tj/dev/nativescript/nativescript-angular/ng-sample/src/angular2/typings/zone/zone.d.ts(1,1): error TS6053: File '/Users/tj/dev/nativescript/nativescript-angular/ng-sample/src/angular2/typings/es6-shim/es6-shim.d.ts' not found.

Any idea what’s up here?
Thanks.

I had forgotten to add a gitignored file, and I had to add a tiny regex hack to get rid of the es6-shim error. The build should be fine now.


User Documentation Annex

Subsections:

[x] #181
[x] #182
[x] #183
[ ] #184

Some comments
anexosAAG.pdf

I will keep in mind those comments before closing this issue. Thanks!


Short solution needed: "Mysql and Lua usage example" (lua-mysql)

Please help us write most modern and shortest code solution for this issue:
Mysql and Lua usage example (technology: lua-mysql)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Mysql and Lua usage example


Add support to update an identity provider

There are migrations to Create and Delete an identity provider (idp) but no migration for changes of an existing idp. Sometimes it is necessary to update the configuration of an idp and it would be more convenient to have an update migration than to delete and recreate the idp.

Released with https://github.com/mayope/keycloakmigration/releases/tag/0.2.29 please verify if this works for you :) Thanks for the contribution ❤


Test

Remove duplicated code in fixed_horizon_delta()
updated tests to reflect new method signature for fixed_horizon_delta()

Coverage decreased (-0.1%) to 76.194% when pulling c2e8d478231389e4380db20b882dc6ce05ae593f on s4826:test into 7249b4c80eef0cfc9e26a91322cdddf6af2e5097 on zalando:dev.

:+1:

This resolves #81 .


Can we use/call SQL store procedure?

DataTables.Queryable operates on an IQueryable. There is nothing built-in for working with stored procedures.


Allow to choose the stage in which the heron systems run

This can improve interoperability with other plugins.
See this discussion about ggrs: https://github.com/jcornaz/heron/discussions/168

I'll take this one!
As a note for future reference, i found this issue https://github.com/bevyengine/bevy/issues/2160 and rfc in the main bevy repo https://github.com/bevyengine/rfcs/pull/33 which describes this issue in more detail for the whole bevy ecosystem.


multiple partType in outline

(as seen in buda-base/public-digital-library#211)
bdr:MW1KG8321_89F02B has multiple partType:
   bdo:partType  bdr:PartTypeText , bdr:PartTypeVolume .

It's an interesting case, what happens here is a hash collision:
$ echo -n "O1KG83211KG51470" |md5sum
89f02b188f2c36d6b4406b0738bb01c2  -
$ echo -n "O1KG83211KG50154" |md5sum
89f02bfaeae71b31f51f7213c3394afd  -

we take the first 6 digits so that creates the problem. The good news is that this type of collision can only happen in one file (because the outline node IDs are prefixed with the instance ID), but we need to detect them.

should be fixed

why not use 16 instead of 6 or all 32?

Well, for these we control the colisions, the editor can use more digits to be sure to avoid them


user.wholesaler.created_at throws error on Account page

Great extension! We're hoping to make good use of it. I am working with the 0.60.x branch.
When logged in as a wholesaler and going to "My Account," the extension throws the error: undefined method `created_at' for "#Wholesaler:0xb57f85a4":Wholesaler
This comes from line 4 of spree_wholesale-bab7a33485ad/app/views/hooks/_wholesale_customer.html.erb:

<%= t('wholesale_customer_since', { :time => @user.wholesaler.created_at }) %>

To get around the issue, I am just replacing @user.wholesaler.created_at with @user.created_at
Is it normal that my Wholesaler objects do not include a "created_at" field?

Hi sorry for the delay, I just got back from vacation :)
This is a strange bug as wholesalers should have a created at field... Have you tried running the upgrade generator?  rails g spree_wholesale:upgrade
This generator should reset the wholesalers' created at fields...

I'm a big fan of vacations :-)
I think you are right: that I had never run that. But, when I ran the
migration, I got the error:
Mysql2::Error: Can't DROP 'created_at'; check that column/key exists: ALTER
TABLE wholesalers DROP created_at
I am wondering whether there is an error in the UpgradeSpreeWholesale
migration - or maybe it is just an error for me since I am inexplicably
missing those db columns - but I wanted to check with you in case I am
missing something:
def self.up
remove_column :wholesalers, :created_at # I THINK I SHOULD DELETE THIS
LINE
remove_column :wholesalers, :updated_at # AND THIS ONE
add_column :wholesalers, :created_at, :datetime
add_column :wholesalers, :updated_at, :datetime
Wholesaler.all.each do |wholesaler|
wholesaler.created_at = wholesaler.user.created_at
wholesaler.save
end
end
def self.down
remove_column :wholesalers, :created_at
remove_column :wholesalers, :updated_at
end
Thanks,
Patrick
On Thu, Feb 9, 2012 at 11:44 AM, Spencer Steffen <
<EMAIL_ADDRESS>
wrote:

Hi sorry for the delay, I just got back from vacation :)
This is a strange bug as wholesalers should have a created at field...
Have you tried running the upgrade generator?
rails g spree_wholesale:upgrade
This generator should reset the wholesalers' created at fields...

Reply to this email directly or view it on GitHub:
https://github.com/citrus/spree_wholesale/issues/12#issuecomment-3890732

Commenting out those two lines should allow you to add the created_at and updated_at columns... give it a try and let me know how it goes :)

OK ... I went ahead and commented out those lines and it seems to work without problems. Thanks for your help!


Child component of Vue-multiselect

I am using Vue-multiselect to create four different types of dropdown. I have to use CDNs due how the project has been set up at work.
I have reproduced these four menus to show you what I am aiming for. See repl.it link below. The problem I am having is that I am unable to create child components inside the Vue-multiselect component which is registered inside the main #app component. I prefer not to have all of the four Vue-multiselect component's data, methods etc inside the main #app. Is there any way of doing something like this?
Vue.component('multiselect-child', {
	components: {
  		Multiselect: VueMultiselect.default
	},
	template: "#multiselect-child-template",
	data: () => ({
	...
	}),
	methods: {
	}
});

const vm = new Vue({
	components: {
		MultiselectChild
	},
	el: '#app',
	data: () => ({
	...
	}),
	methods: {
	}
});

Reproduction Link
https://repl.it/@rjlevy/Vue-multi-select-dropdown-option-slots-working-check
Steps to reproduce
I would like to make a child component so that each component has its own data, template, methods etc.
Expected behaviour
I was expecting individual child components, together with their data and methods, to render inside the Vue-multiselect component which is registered inside the main #app component
Actual behaviour
At the moment I am only able to register the Vue-multiselect component inside #app which means I have to have 4 separate options arrays in #app's data: optionsSingle, optionsSingleColour, optionsSingleIcons, optionsMultipleIcons.
I am quite new to Vue so any help would be greatly appreciated.
Many thanks
Roland

Issue now resolved
After doing some research I have resolved this by using mixins. The data for all the different types of menus are now stored outside the main app's data and instead, inside the mixin.
The Vue-multiselect component is registered as a child inside its parent, called MultiselectParent. This parent component is customisable using props which are passed down to the Vue-multiselect component.
Here is the solution I came up with
https://repl.it/@rjlevy/Vue-multiselect-parent-component-mixins-working
I this makes sense. Still so much to learn!


[Support] Storybook + Angular 6 multiple apps (nrwl/nx)

Bug or support request summary
I would like to setup storybook in my monorepo to be able to develop and tests shared components across all applications.
I have an issue concerning the import of the styles because storybook is using the property projects[0].root to resolve the paths of all styles from projects[0].architect.build.styles but my styles are also specifying the full path. So I see some errors like:
ERROR in multi ./apps/appName/libs/core/theme.scss ./apps/appName/apps/appName/src/styles.scss
Module not found: Error: Can't resolve 'C:\Users\user\dev\projects\frontend\monorepo\apps\appName\apps\crt\src\styles.scss' in 'C:\Users\user\dev\projects\frontend\monorepo'
 @ multi ./apps/appName/libs/core/theme.scss ./apps/appName/apps/appName/src/styles.scss +1

and my angular.json contain
...
"projects": {
    "appName": {
      "root": "apps/appName/",
      "sourceRoot": "apps/appName/src",
      ....
      "architect": {
        "build": {
            ...
            "styles": [
              "libs/core/theme.scss",
              "apps/appName/src/styles.scss"
            ],
...

Dependencies

@angular/*: 6.0.7
@storybook/*: 4.0.0-alpha.13

I think @rhalff was able to work arround this.

I've reported the same problem here : #3864

Does anyone managed to get it work ?

I will close this one in favor of #3864, also @marshallmick007 PRed a fix.
@jogelin, the angular builder is still relevant IMO.


Removes embedded Okta Groups

The current value for local.okta_groups is fixed and a mix of AWS and Github groups.
This change proposes separating AWS groups into a dedicate list and supporting custom groups in order to accommodate different needs. However, it still offers a default group AWSPlatformAdmins to avoid having to always pass a group name.

I'd like to put this on hold until support for SSO permission sets has been merged until the AWS provider.
While it's just okta groups it doesn't make sense to be part of this module; if it's Okta groups together with permission sets then it makes sense.

On the one hand I agree with you that its better to add support for Okta groups i.c.w. SSO permission sets so the full solution is implemented, but on the other hand not merging this makes the migration of the Geldmaat inception harder. If we are not going to merge this, are we then going to document that the creation of Okta groups is manual for now and remove this from the state? Maybe we should have a short call about this today! :-)

We have decided to remove the Okta Groups from the module and manage them separately until we can implement the full solution including SSO permission set assignments.

Hi @fgoncalves-io, @shoekstra, @marwinbaumannsbp.
In the interest of getting the AWS SSO resources merged, please go give a thumbs up to 15808
We've completed most of the work for supporting the AWS SSO and AWS SSO Identity Store resources and datasources in Terraform. The 15322 [WIP] PR encompasses all of that work. But, the contribution guide for the repo recommends submitting small pull requests with the minimum required resources, so we've submitted 15808 as our initial PR with just data.aws_sso_instance, data.aws_sso_permission_set, and aws_sso_permission_set. Once that's merged, we will submit PRs for all of the other resources and data sources since they depend on that initial PR.


EUCA-12819 Fix changelog day-of-the-week errors that cause "bogus date" errors

Only some of the errors are incorrect days of the week, so this is instead fixed in commit 0a303ae.


Rust and WebAssembly Working Group Meeting #22

Our next meeting will be Thursday, October 11th at 17:00 UTC.
Add agenda items here: https://paper.dropbox.com/doc/RustWebAssembly-WG-dcXi5F7Bqlvg10zd7dKve
We use Zoom for video meetings, so make sure you've downloaded the client! (It's free, but you have to sign up.) Here is our meeting room: https://zoom.us/j/625862582
Anyone interested in Rust and WebAssembly is invited to join! Yes, that includes you!

Starting in ten minutes! See y'all soon :)

Use this zoom meeting today: https://zoom.us/s/251613476


Update example to latest gloo-worker crate

I started using the current example and realised it was out of date so have updated it.

Thanks!


Creating a StorageService using ResourceManagementClient fails with "Accepted"

When creating a StorageService using the following code, it throws with CloudException.Message == "Accepted". The reason is likely due to line 404 of ResourceOperations.cs:
// ... Submit request...
if (statusCode != HttpStatusCode.OK && statusCode != HttpStatusCode.Created)
{ // ... throw... }
This line should probably include Accepted (202) as a valid result.
Repro code:
var armClient = new ResourceManagementClient(azureCreds);
                var id = new ResourceIdentity()
                {
                    ResourceProviderApiVersion = "2014-06-01",
                    ResourceProviderNamespace = "Microsoft.ClassicStorage",
                    ResourceName = "<storage service name>",
                    ResourceType = "storageAccounts"
                };

                var properties = @"{""accountType"": """ + "Standard-LRS" + @"""}";

                var rsc = new BasicResource()
                {
                    Location = this.Location,
                    Properties = properties
                };

                rsp = armClient.Resources.CreateOrUpdate(this.ResourceGroup, id, rsc);

// throws "Accepted" error

This is expected at this time. Once Storage is generally available in ARM, this will light up.


Common: refactor shared source files

This PR dissolves the ScottPlot.Common package and instead tactically imports specific .cs files directly from ScottPlot4 into ScottPlot5.
ScottPlot5 now uses all ScottPlot4's palettes.
Extends recent work:

#2027
#2018
#2009
#1967
#1963
#1956

this comment is for testing the Discord web hook


Update README.md dependencies

Add Arduino Http Client to ThingsBoard SDK installation dependecies.

LGTM, thanks!


Add authorizer interface to allow custom LWM2M client authorization

Since we merged registrationStore with observationStore, we doesn't have a way to customize LWM2M client authorization anymore.
So we add a new interface responsible to do that : Authorizer.

:gift: for @msangoi, now the Authorizer does not depend on SecurityStore anymore. The securityStore is set as constructor of the BasicAuthorizer

:santa: I renamed BasicAuthorizer in DefaultAuthorizer too :christmas_tree:

👍


WIP: Investigate verify rc linux failures

@github-actions crossbow submit verify-rc-source-integration-linux-ubuntu-18.04-amd64

Did you find out anything here?

No, I didn't. I did run the job twice and it finished successfully in both cases.


Fix the disabled icon issue in the collaborator list

Scope of changes
Fix the disabled icon issue in the collaborator list
Type of change

[x] bug fix
[ ] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria
https://app.shortcut.com/rotational/story/11224/make-the-new-collaborator-button-disabled-for-a-wrong-permission
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report
Base: 44.63% // Head: 44.64% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (aeeefe7) compared to base (f01ad56).
Patch coverage: 100.00% of modified lines in pull request are covered.

:exclamation: Current head aeeefe7 differs from pull request most recent head 8e40b37. Consider uploading reports for the commit 8e40b37 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #896   +/-   ##
=======================================
  Coverage   44.63%   44.64%
=======================================
  Files         666      666
  Lines       24151    24154    +3
  Branches     1519     1519
=======================================
+ Hits        10781    10784    +3
  Misses      11996    11996
  Partials     1374     1374

Flag
Coverage Δ

unittests
44.64% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ors/DeleteCollaborator/DeleteCollaboratorModal.tsx
65.51% <ø> (ø)

...eb/gds-user-ui/src/components/Collaborators/lib.ts
50.00% <ø> (ø)

...orators/EditCollaborator/EditCollaboratorModal.tsx
75.67% <100.00%> (ø)

.../components/Collaborators/useSafeDisableButton.tsx
100.00% <100.00%> (+12.50%)
:arrow_up:

web/gds-admin-ui/src/utils/index.js
44.05% <0.00%> (-0.70%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Support fileops for Go on linux

Suport for network ops is added through #228, we need support for fileops as well

To be more precise, we need to add E2E test to run both on macOS/Linux and for Linux to work we probably need to alter the current Go Linux hooks added in #228.


Browse page updates

pending:

[x] update the other filters on the page to add to the query. for example, the license filter should be added to the query instead of executed client-side for this browse page only
[x] the sort should be executed as part of the query, i.e. {"sort": "name"} instead of executed client side
[x] implement paging with the continuation token
[x] load data on initial page load

I'm trying to pass the correct query values to apply the filters, but i can't find some properties.
Looking at the schema at https://github.com/clearlydefined/service/blob/master/schemas/definitions-find.json , i can't find the correct properties for:

Source Location (Presence, Absence)
Release Date (Presence, Absence)

Also, i've tried building a query with
{"type":"maven","license":"apache-2.0"}
But it doesn't return any value.

Source Location (Presence, Absence)

Let's remove this filter from the browse page for now

Release Date (Presence, Absence)

Instead of presence/absence, we should add these as new filters where the user chooses a date
the api supports releasedAfter and releasedBefore

Also, i've tried building a query with
{"type":"maven","license":"apache-2.0"}

try against the prod-api
I am seeing results there. Also, make sure to use the proper SPDX casing
{
 "type": "maven", "license": "Apache-2.0"
}

see preview https://deploy-preview-454--clearlydefined.netlify.com/browse
I think this is in good shape to move forward

Maybe there's some work pending, but checking into the deploy preview, looks like then when making a search the results doesn't show up

@storrisi it is deploying now. that link should start to work shortly

I'm going to release these updates now

thanks @jeffmcaffer I'll go through your comments and open a new PR


Why is uri a required field for server_uri in the ExtAuthZ Proto?

Description
As per the ExtAuthZ Filter Docs both the uri as well as cluster are marked as REQUIRED. Why do we need an explicit uri if a cluster is being provided? I can't find any instances in the code where we are using uri. Could it be deprecated/removed to avoid the confusion?

cc @ggreenway @pradeepcrao @esmet

I think in this case it's because it's re-using a proto message that used in multiple contexts, and this field was required in some other context when using this message. I agree it shouldn't be needed here.


RxRelay instead of subjects?

https://github.com/JakeWharton/RxRelay

I don't want to add another dependency if we can avoid it, and the use of Subjects are entirely internal.

Alright, just threw it up as a suggestion in case.


100% test coverage

Not sure if pipe-dream, but sure would be nice to achieve.

Didn't achieve 100% per se, but close-enough that I'm happy with for now.


Scaling breaks "The S3 repository has backups from another cluster" blocked status

Steps to reproduce

juju deploy s3-integrator
juju deploy postgresql-k8s --config profile=testing --channel edge --trust
configure s3-integrator to use bucket with backups from another cluster
juju integrate s3-integrator postgresql-k8s
as it should be, cluster became in The S3 repository has backups from another cluster blocked status

juju scale-application postgresql-k8s 2
after scale, cluster loose it's blocked status and became active idle

Expected behavior
Cluster should keep it's blocked status The S3 repository has backups from another cluster even after scaling.
Actual behavior
See step 7.
Versions

Operating system: Ubuntu 24.04 LTS

Juju CLI: 3.5.2-genericlinux-amd64

Juju agent: 3.5.2

Charm revision: 327

microk8s: MicroK8s v1.30.0 revision 6783
Log output

Juju debug log: debug-log

Additional context

From the work on Point In Time Recovery, i can suggest to refactor logic of this blocked message. Now, The S3 repository has backups from another cluster message sets in PostgreSQLBackups._on_s3_credential_changed by can_use_s3_repository func and it's supposed not to be overridden by any of events. But it's better to keep this status in app_peer_data and set this message in PostgresqlOperatorCharm._set_active_status function as it works with blocked status Move restored cluster to another S3 bucket introduced by the PITR work in the PR referenced above.

This is a valid bugreport and lets keep it opened, however we should focus on removal this blocking message completely (managing timelines during recovery) and not fixing this issue. @marceloneppel ACK?

@taurus-forever
Timelines management will:

allow us not to use Move restored cluster to another S3 bucket logic
allow user to see all the lifespan of cluster (not just separated to different S3 buckets after each restore) and effectively navigate through different timelines of it
imply WAL archiving refactor, that will fix issues like this (not sure if there is the same bug)

But, error The S3 repository has backups from another cluster is different as it indicates that pgBackRest stanza is configured for another cluster. From the quick research, pgBackRest does not support such scenario. Also, it may cause some errors like same timelines from different clusters will conflict with each other. Anyway, this will require deeper research and it's not related to the PITR.

@taurus-forever: @Zvirovyi is right. The message that is gone after scaling the cluster is related to pointing the cluster to a backup repository from another cluster, not from a different timeline of the same cluster.