Prometheus - disable creating Kublet Endpoints

We don't monitor kubelets via Prometheus in scale tests, thus we can disable creation of the Endpoints object for kubelets.
An alternative would be to wait for the Kubelet Endpoints object to be created before running tests.
But, for now, disabling the Kubelet Endpoints object creation is simply a better solution.
Ref. https://github.com/kubernetes/kubernetes/issues/75284

/lgtm
/approve

/assign @krzysied
/assign @wojtek-t
Looks like Prow missed Wojtek's approval, could you re-approve?

/approve


Make titlecasing for finding title configurable

New feature to optionally disable titlecasing for the title of findings.
This implements/fixes https://github.com/DefectDojo/django-DefectDojo/issues/9241

recalculated settings hash to fix failing unit tests

I do understand your fears of wrong hashcodes.
However enabling this configuration option would allow DefectDojo to be used with so many other languages other than English out of the box. Titlecasing only works in English and causes errors in most other languages.
Do you maybe have an idea how to make the config more "hidden" or harder to accidentally change? I can also include documentation about the implications of changing this config (in code and in the official docs)
In the end it would be sad to limit DefectDojo to English findings only, especially if this missing config is the only thing holding it back. (for German e.g.)
Thank you for your thoughts!

Another idea could be to always create the titlecase version of the title of the finding right before it get's hashed, no matter the current setting. Therfore, even if the setting is changed just to play with it, the resulting hash will still be the same.

Just to be sure I understand this correctly, are you saying something like this?
orignial_title = self.title
 # Title Casing
from titlecase import titlecase
self.title = titlecase(self.title[:511])
...
>> Do the hash code stuff
...
if not settings.FINDING_TITLECASING_ENABLED:
    self.title = original_title

I had a different solution in mind when writing my comment but I now realize that that wouldn't have worked.
So yes, something like you wrote could solve the hashing issue:
...

orignial_title = self.title
 # Title Casing
from titlecase import titlecase
self.title = titlecase(self.title[:511])

...

if dedupe_option:
    if (self.hash_code is not None):
        deduplicationLogger.debug("Hash_code already computed for finding")
    else:
        self.hash_code = self.compute_hash_code()
        deduplicationLogger.debug(
            "Hash_code computed for finding: %s", self.hash_code)
        if not settings.FINDING_TITLECASING_ENABLED:
            self.title = original_title

...

Closed as stale

Since this PR has been closed, can I assume that such a feature will not be approved in the future? Otherwise I could update this PR with the changes discussed above.

@StephanPillhofer The PR was closed as stale as part of a general review of PRs which hadn't seen activity in a while.
Such a feature could be considered in the future. The key issue is that such a change would need to happen in the 'view' layer of DefectDojo - in the Django templates so that the title change is only done for UI operations and the title stored in the DB is left unchanged. If the PR changes how titles are stored in the DB, there's some seriously negative side effects for existing DefectDojo instances.
Due to the fact that title is frequently used in the deduplication hash codes, making a change to how those are stored is a problem for existing calculated dedup hashes for anyone already using DefectDojo.  For people with large numbers of findings, recalculating hashes can represent a significant time/resource issue. The largest one I know of with public numbers is:

(full deck here)
I understand that in your case, you're current running with the titlecase code commented out so a change wouldn't impact your instance but most users won't be in that situation. We could wrap those lines in an if but there's an on going support issue for a new DD_something setting for a small portion of the community with may be impacted by this.
So, we're open to a PR which addresses the issue your having but it would have to consider the impact on the other members of the community currently using DefectDojo - especially because its very possible to make a change which appears to not have any side effects but actually breaks deduplication for users silently or at least with no easy to notice warning.
As DefectDojo has gained popularity over the years, we've had to be more careful about changes which impact those currently using the applications.
Hope that helps explain our thinking around this.


Added error for numeric literals larger than 2^53 - 1

Fixes #29863
Is there a better check for a numeric literal being too large than Number(text) >= Math.pow(2, 53) - 1? This performance difference should be negligible given that only literals of length 16 or more will go through Number.

Better way would be using Number.isSafeInteger(), but it is not available in IE11 😭 (funny that this code uses unsafe integer Math.pow(2, 53) itself, but haven't seen cases when this won't work as expected).
Also looks like there are no tests for error messages related to "negative numbers". Are they needed here?

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER

@AnyhowStep as I said - not available in IE11 (both Number.isSafeInteger() and related constants)

Just copy paste that constant into the TS source code. It's one or two lines at most and gets rid of the "unsafe" pow(2, 53)

@typescript-bot test this
@typescript-bot user test this
@typescript-bot pack this

Turns out this breaks more than we thought. For example, it breaks the Azure SDK with the integer<PHONE_NUMBER>00000000: https://github.com/Azure/azure-sdk-for-js/blob/dcd9a29b083a63fa1c9888aca4a5da6acda425a6/sdk/servicebus/service-bus/src/util/utils.ts#L106
(@bterlson @ramya-rao-a)
The thing that's interesting is that while any operation on that number is lossy, I believe that the numeric literal hasn't lost any precision. That's because the mantissa 621355968 can be accurately represented.

I guess you can shave off the trailing 0s and see if the number fits, but I'm increasingly convinced that this has more value as a lint rule, and that putting it into TypeScript with the intent of only catching a subset of suspicious code would be worse than having it built into ESLint.

In that case I'll close this PR and add a quickfix to add an n to numeric literal if it's all /\d+/ digits and >= 2 ** 53. Thanks!

https://github.com/microsoft/TypeScript/pull/33300


local-path-provisioner failing to start because of missing clusterrole object

Version:
v0.10.0-alpha1
Describe the bug
local-path-provisioner reports missing clusterrole object, even if the manifest is configured with correct clusterrole and clusterrolebinding.
This error is seen intermittently.
ERROR: logging before flag.Parse: E1009 21:47:05.681843       1 leaderelection.go:252] error retrieving resource lock kube-system/rancher.io-local-path: endpoints "rancher.io-local-path" is forbidden: User "system:serviceaccount:kube-system:local-path-provisioner-service-account" cannot get resource "endpoints" in API group "" in the namespace "kube-system": RBAC: clusterrole.rbac.authorization.k8s.io "local-path-provisioner-role" not found

root@ip-172-31-2-107:~# cat /var/lib/rancher/k3s/server/manifests/local-storage.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: local-path-provisioner-service-account
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:
  name: local-path-provisioner-role
  namespace: kube-system
rules:
- apiGroups: [""]
  resources: ["nodes", "persistentvolumeclaims"]
  verbs: ["get", "list", "watch"]
- apiGroups: [""]
  resources: ["endpoints", "persistentvolumes", "pods"]
  verbs: ["*"]
- apiGroups: [""]
  resources: ["events"]
  verbs: ["create", "patch"]
- apiGroups: ["storage.k8s.io"]
  resources: ["storageclasses"]
  verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: local-path-provisioner-bind
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: local-path-provisioner-role
subjects:
- kind: ServiceAccount
  name: local-path-provisioner-service-account
  namespace: kube-system
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: local-path-provisioner
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app: local-path-provisioner
  template:
    metadata:
      labels:
        app: local-path-provisioner
    spec:
      serviceAccountName: local-path-provisioner-service-account
      containers:
      - name: local-path-provisioner
        image: rancher/local-path-provisioner:v0.0.11
        imagePullPolicy: IfNotPresent
        command:
        - local-path-provisioner
        - start
        - --config
        - /etc/config/config.json
        volumeMounts:
        - name: config-volume
          mountPath: /etc/config/
        env:
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
      volumes:
        - name: config-volume
          configMap:
            name: local-path-config
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: local-path
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"
provisioner: rancher.io/local-path
volumeBindingMode: WaitForFirstConsumer
reclaimPolicy: Delete
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: local-path-config
  namespace: kube-system
data:
  config.json: |-
        {
                "nodePathMap":[
                {
                        "node":"DEFAULT_PATH_FOR_NON_LISTED_NODES",
                        "paths":["/var/lib/rancher/k3s/storage"]
                }
                ]
        }
root@ip-172-31-2-107:~#

To Reproduce

Start k3s master
run yaml file for nginx pv

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: nginxpv
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginxpv
spec:
  selector:
    matchLabels:
      app: nginxpv
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: nginxpv
    spec:
      containers:
      - image: nginx
        name: nginxpv
        volumeMounts:
        - name: nginxpv
          mountPath: /usr/share/nginx/html
      volumes:
      - name: nginxpv
        persistentVolumeClaim:
          claimName: nginxpv```

**Expected behavior**
pv should be created and mounted within the pod.

**Actual behavior**
pod is on pending state and pv is not created.
local-path-provisioner is showing error in the logs above.

To test later; have not observed this issue again after attempting to reproduce multiple times.
QA to try a couple more times and if we don't repro we should close.

Unable to re-produce this issue. Closing for now.

Same issue after upgrading to v0.10.0.

Reopen to re-test with upgrade from v0.9.1 to v0.10.0 cc: @ShylajaDevadiga something to look at as medium priority

I am not seeing issues upgrading from v0.9.1 to v0.10.0. @pierredavidbelanger could you please provide commands used to install and upgrade so that we could reproduce the issue?
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v0.9.1 sh -s - server

Upgrade
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v0.10.0 sh -s - server

root @TEST:~# k3s -v
k3s version v0.10.0 (f9888ca3)
root @TEST:~# k3s kubectl  get pods
NAME                      READY   STATUS    RESTARTS   AGE
nginxpv-bd865776b-vvldk   1/1     Running   0          7m29s
root @TEST:~# kubectl get events -n kube-system  |grep replicaset/local
9m30s       Normal   SuccessfulCreate    replicaset/local-path-provisioner-58fb86bdfd          Created pod: local-path-provisioner-58fb86bdfd-8n4tx
root @TEST:~#
root @TEST:~# k3s kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM             STORAGECLASS   REASON   AGE
pvc-d0a449a6-fb7a-43aa-973f-e64e6db7f556   10Mi       RWO            Delete           Bound    default/nginxpv   local-path              11m
root @TEST:~# k3s kubectl get pvc
NAME      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
nginxpv   Bound    pvc-d0a449a6-fb7a-43aa-973f-e64e6db7f556   10Mi       RWO            local-path     11m
root @TEST:~#

@pierredavidbelanger is you local path provisioner installed from previous versions manually ?

@tux-00 no it was not; I never added / edited something in the manifests folder. I do not have proof (as the folder has been populated since by the 0.10 version) but I am confident that all I had in there was the stock coredns and traefik.

@ShylajaDevadiga here are the exact cmd I used (from my git history):
At the time I ran this, 0.9.1 was the latest:
curl -sfL https://get.k3s.io | sh -s - server --data-dir /mnt/k3s --disable-agent --http-listen-port 6080 --storage-endpoint 'sqlite://./state.db'

curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION='v0.10.0' sh -s - \
  server --data-dir /mnt/k3s --disable-agent --http-listen-port 6080 \
  --storage-endpoint 'postgres://postgres:postgres@localhost/k3s?sslmode=disable'

In both cases, --data-dir /mnt/k3s is because I mount an EFS there, and --http-listen-port 6080 because I am behind a SSL termination LB (an AWS ALB).

@pierredavidbelanger Thank you for that. Could you also share the logs with postgres with focus on token creation? At this time we have tested postgres as storage-endpoint. Also wanted to mention we are not advertising usage of --disable-agent as we see kubectl does not list the nodes without agent.

@ShylajaDevadiga I have since terminated all instances of this cluster, but I may still have CW logs somewhere. If only you could tel me what I should search for , a pattern, something. The logs are HUGE, because I configured dockerd log driver to put everything there :roll_eyes:

@ShylajaDevadiga I am sorry I do not find anything related to token creation, but I got this, a complete (short) session recorded between two restart of the server instance (indeed, postgress container logs where sent to CW Logs, and its data persisted on EFS):
This user must also own the server process.
The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... UTC
creating configuration files ... ok
running bootstrap script ... ok
sh: locale: not found
2019-10-23 17:30:48.883 UTC [26] WARNING: no usable system locales were found
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
Success. You can now start the database server using:
pg_ctl -D /var/lib/postgresql/data -l logfile start
****************************************************
WARNING: No password has been set for the database.
This will allow anyone with access to the
Postgres port to access your database. In
Docker's default configuration, this is
effectively any other container on the same
system.
Use "-e POSTGRES_PASSWORD=password" to set
it in "docker run".
****************************************************
waiting for server to start....2019-10-23 17:31:32.416 UTC [45] LOG: starting PostgreSQL 12.0 on x86_64-pc-linux-musl, compiled by gcc (Alpine 8.3.0) 8.3.0, 64-bit
2019-10-23 17:31:32.418 UTC [45] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-10-23 17:31:32.554 UTC [46] LOG: database system was shut down at 2019-10-23 17:31:22 UTC
2019-10-23 17:31:32.641 UTC [45] LOG: database system is ready to accept connections
done
server started
/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
2019-10-23 17:31:32.682 UTC [45] LOG: received fast shutdown request
waiting for server to shut down....2019-10-23 17:31:32.695 UTC [45] LOG: aborting any active transactions
2019-10-23 17:31:32.697 UTC [45] LOG: background worker "logical replication launcher" (PID 52) exited with exit code 1
2019-10-23 17:31:32.697 UTC [47] LOG: shutting down
2019-10-23 17:31:32.870 UTC [45] LOG: database system is shut down
done
server stopped
PostgreSQL init process complete; ready for start up.
2019-10-23 17:31:32.953 UTC [1] LOG: starting PostgreSQL 12.0 on x86_64-pc-linux-musl, compiled by gcc (Alpine 8.3.0) 8.3.0, 64-bit
2019-10-23 17:31:32.953 UTC [1] LOG: listening on IPv4 address "<IP_ADDRESS>", port 5432
2019-10-23 17:31:32.953 UTC [1] LOG: listening on IPv6 address "::", port 5432
2019-10-23 17:31:32.967 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-10-23 17:31:33.083 UTC [54] LOG: database system was shut down at 2019-10-23 17:31:32 UTC
2019-10-23 17:31:33.120 UTC [1] LOG: database system is ready to accept connections
2019-10-23 17:32:57.950 UTC [61] FATAL: role "root" does not exist
2019-10-23 17:33:51.719 UTC [65] ERROR: unrecognized configuration parameter "databases"
2019-10-23 17:33:51.719 UTC [65] STATEMENT: show databases;
2019-10-23 17:48:27.802 UTC [139] FATAL: role "root" does not exist
... SKIP A COUPLE OF DUPLICATE LINES ...
2019-10-23 17:58:33.711 UTC [264] FATAL: role "root" does not exist
2019-10-23 17:58:52.982 UTC [270] FATAL: database "k3s" does not exist
2019-10-23 17:59:06.052 UTC [272] ERROR: relation "key_value" does not exist at character 22
2019-10-23 17:59:06.052 UTC [272] STATEMENT: SELECT COUNT(*) FROM key_value
2019-10-23 17:59:31.960 UTC [400] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:31.960 UTC [400] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/edit, 57) already exists.
2019-10-23 17:59:31.960 UTC [400] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:31.977 UTC [407] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:31.977 UTC [407] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/admin, 56) already exists.
2019-10-23 17:59:31.977 UTC [407] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:31.997 UTC [405] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:31.997 UTC [405] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 170) already exists.
2019-10-23 17:59:31.997 UTC [405] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.015 UTC [408] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.015 UTC [408] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 170) already exists.
2019-10-23 17:59:32.015 UTC [408] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.020 UTC [399] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.020 UTC [399] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 170) already exists.
2019-10-23 17:59:32.020 UTC [399] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.037 UTC [399] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.037 UTC [399] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/admin, 56) already exists.
2019-10-23 17:59:32.037 UTC [399] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.046 UTC [411] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.046 UTC [411] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/edit, 314) already exists.
2019-10-23 17:59:32.046 UTC [411] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.049 UTC [406] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.049 UTC [406] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/admin, 56) already exists.
2019-10-23 17:59:32.049 UTC [406] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.057 UTC [399] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.057 UTC [399] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/admin, 56) already exists.
2019-10-23 17:59:32.057 UTC [399] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.126 UTC [416] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.126 UTC [416] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 320) already exists.
2019-10-23 17:59:32.126 UTC [416] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.144 UTC [418] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.144 UTC [418] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/admin, 56) already exists.
2019-10-23 17:59:32.144 UTC [418] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.231 UTC [406] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.231 UTC [406] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/admin, 56) already exists.
2019-10-23 17:59:32.231 UTC [406] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.399 UTC [418] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.399 UTC [418] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/admin, 56) already exists.
2019-10-23 17:59:32.399 UTC [418] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 17:59:32.723 UTC [422] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 17:59:32.723 UTC [422] DETAIL: Key (name, prev_revision)=(/registry/clusterroles/admin, 56) already exists.
2019-10-23 17:59:32.723 UTC [422] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:48:40.786 UTC [581] LOG: could not receive data from client: Connection reset by peer
2019-10-23 18:48:41.078 UTC [589] ERROR: relation "key_value" does not exist at character 22
2019-10-23 18:48:41.078 UTC [589] STATEMENT: SELECT COUNT(*) FROM key_value
2019-10-23 18:49:25.854 UTC [693] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:25.854 UTC [693] DETAIL: Key (name, prev_revision)=(/registry/replicasets/kube-system/local-path-provisioner-58fb86bdfd, 6611) already exists.
2019-10-23 18:49:25.854 UTC [693] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:25.952 UTC [690] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:25.952 UTC [690] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:25.952 UTC [690] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:25.963 UTC [695] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:25.963 UTC [695] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:25.963 UTC [695] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:25.985 UTC [690] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:25.985 UTC [690] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:25.985 UTC [690] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:26.020 UTC [696] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:26.020 UTC [696] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:26.020 UTC [696] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:26.065 UTC [696] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:26.065 UTC [696] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:26.065 UTC [696] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:26.149 UTC [696] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:26.149 UTC [696] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:26.149 UTC [696] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:26.314 UTC [696] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:26.314 UTC [696] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:26.314 UTC [696] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:26.651 UTC [697] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:26.651 UTC [697] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:26.651 UTC [697] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:27.295 UTC [696] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:27.295 UTC [696] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:27.295 UTC [696] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:28.580 UTC [697] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:28.580 UTC [697] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:28.580 UTC [697] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:31.147 UTC [696] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:31.147 UTC [696] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:31.147 UTC [696] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:36.286 UTC [696] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:36.286 UTC [696] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:36.286 UTC [696] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 18:49:46.541 UTC [697] ERROR: duplicate key value violates unique constraint "kine_name_prev_revision_uindex"
2019-10-23 18:49:46.541 UTC [697] DETAIL: Key (name, prev_revision)=(/registry/deployments/kube-system/local-path-provisioner, 6616) already exists.
2019-10-23 18:49:46.541 UTC [697] STATEMENT: INSERT INTO kine(name, created, deleted, create_revision, prev_revision, lease, value, old_value)
values($1, $2, $3, $4, $5, $6, $7, $8) RETURNING id
2019-10-23 19:06:01.554 UTC [1] LOG: received smart shutdown request
2019-10-23 19:06:01.598 UTC [1] LOG: background worker "logical replication launcher" (PID 60) exited with exit code 1
2019-10-23 19:06:01.598 UTC [55] LOG: shutting down
2019-10-23 19:06:02.544 UTC [1] LOG: database system is shut down```

Logs provided does not give much details on the issue. I would suggest to run without --disable-agent.

With v0.10.1 updating to use --default-local-storage-path /tmp/k3s resulted in the pvc and 'local-path-provisoner' pod loading successfully.
With --disable-agent option the pods will be in pending state as there are no nodes available. Attach a worker node to fix the pending state.
Related issue https://github.com/rancher/k3s/issues/963
Closing for now.


404 error

i using android studio( implementation 'org.jsoup:jsoup:1.11.2'  )
i haved  Rebuild project Tried several times is the following error
error is
org.gradle.internal.resource.transport.http.HttpRequestException: Could not GET 'https://dl.google.com/dl/android/maven2/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.pom'.
i  using google open this link produced 404 .

I'm very sorry for the reason I set up my own proxy

I'm very sorry for the reason I set up my own proxy


Update README.md

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--aem--abhishek-pawale.hlx.live/
After: https://test--aem--abhishek-pawale.hlx.live/

not correct


BERT4Rec tutorial

Added BERT4Rec tutorial

" Item embeddings from these sequences are fed to multi-head self-attention to acquire user sequence latent representation"
That's not exactly true. Embeddings are fed into transformer blocks which have more login inside then just multi-head self-attention

"After one or several stacked attention blocks, resulting embeddings are used to predict the next item."
Ambiguous.
resulting embeddings are used to predict all items in the sequence. Each item is being predicted based only on previous items information.

About main differences in the table. Let's go further.

You didn't specify losses. Original implementations of these models had different losses.
Some of the differences are conceptual (target and attention direction). They cannot be excluded from model. But other (losses, activation functions, transformer blocks) could be a subject of change. Try to explicitly emphasize it. It really is important.

Let's add to RecTools implementation section references for our implementations (which implementations we took as goals, what we changed). Let'a also emphasize that we included number of negatives as a hyper-perameter.

Let's remove def recommend from basic usage section.
We merge recos with items only once. No need for a separate method

In losses section please add you description of what's happening. What is the difference between losses?

Let's remove TODO: Add category item features embeddings
We will add them afterwards

Transformer models -> Transformer models tutorial

Categorical feature embeddings are dealt with separately from id embeddings and are concatenated after weight update.

They are not concatenated. They are summed up.
Why "after weight update"?

You can just write "Categorical feature embeddings are summed up with other embeddings for each item if they are present in the model."


show_doc errors on Python 3.10 union sub-type hints

show_doc errors out when using Python 3.10 union sub-type hints. This occurs with typing.List List[Tensor|int] or list list[Tensor|int]
Minimal reproducible code and error:
from __future__ import annotations
from nbdev.showdoc import *

def test(l:list[float|int]):
    return l

show_doc(test)

Error:
Traceback (most recent call last):

  Cell In [3], line 1
    show_doc(test)

  File ~/python3.9/site-packages/nbdev/showdoc.py:191 in show_doc
    else:return renderer(sym or show_doc, name=name, title_level=title_level)

  File ~/python3.9/site-packages/nbdev/showdoc.py:127 in __init__
    try: self.sig = signature_ex(sym, eval_str=True)

  File ~/python3.9/site-packages/fastcore/basics.py:350 in signature_ex
    ann = type_hints(obj)

  File ~/python3.9/site-packages/fastcore/basics.py:318 in type_hints
    return {k:_eval_type(v,glb,loc) for k,v in ann.items()}

  File ~/miniconda3/envs/fastai/lib/python3.9/site-packages/fastcore/basics.py:318 in <dictcomp>
    return {k:_eval_type(v,glb,loc) for k,v in ann.items()}

  File ~/python3.9/site-packages/fastcore/basics.py:311 in _eval_type
    res = eval_type(t, glb, loc)

  File ~python3.9/site-packages/fastcore/basics.py:304 in eval_type
    if '|' in t: return Union[eval_type(tuple(t.split('|')), glb, loc)]

  File ~/python3.9/site-packages/fastcore/basics.py:306 in eval_type
    if isinstance(t,(tuple,list)): return type(t)([eval_type(c, glb, loc) for c in t])

  File ~/python3.9/site-packages/fastcore/basics.py:306 in <listcomp>
    if isinstance(t,(tuple,list)): return type(t)([eval_type(c, glb, loc) for c in t])

  File ~/python3.9/site-packages/fastcore/basics.py:305 in eval_type
    return eval(t, glb, loc)

  File <string>:1
    list[float
              ^
SyntaxError: unexpected EOF while parsing

However, using optional list[Optional[float]] or union Union list[Union[float, int]]works.
from typing import Union
from nbdev.showdoc import *

def test(
    l:list[Union[float, int]] # test comment
):
    return l

show_doc(test)

Using user-defined generic types renders the table, but displays list[T] as the type, not list[int, float] (or something similar).
from typing import TypeVar
from nbdev.showdoc import *

T = TypeVar('T', int, float)

def test(
    l:list[T] # test comment
):
    return l

show_doc(test)

Here's a minimal repro:
from fastcore.basics import eval_type
eval_type('list[float|int]', {}, {})

The issue is that fastcore's backport of py310-style annotations (e.g. float|int) doesn't support generic types, see this line: https://github.com/fastai/fastcore/blob/86337bad16a65f23c5335286ab73cd4d6425c586/fastcore/basics.py#L304

I wonder if we should be evaluating types for show_doc at all? If we don't, we would avoid https://github.com/fastai/nbdev/issues/1116 too:. cc @jph00

It would be worth trying removing eval and seeing how that changes, for instance, the fastai and nbdev docs


Update to pacackge:web

is there any option to upgrade this package to new package:web of flutter 3.19

is there any issue ?

Not really, but is necessary if you want to compile in wasm your project
"To run Flutter applications on the web using WebAssembly, you need to migrate all code — from the application and all dependencies — to use the new JavaScript Interop mechanism and the package:web. The legacy JavaScript and browser libraries remain unchanged and supported for compiling to JavaScript code. However, compiling to WebAssembly requires a migration."

I think this is done, with version 0.0.6


Kernal Unable to Shutdown on Closing the File

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
NOTE: similar to the closed issue #9442 .
Hi! This problem exists in vscode jupyter extension v2023.1.2000312134 and the pre-released v2023.2.1000381022. Closing the notebook in the vscode window does not shutdown the kernal.
vscode version: 1.75.0
When doing this:

Set this setting to 'verbose'
"jupyter.loggingLevel": "verbose"
Open a notebook
Run a cell
Clear the jupyter output window after the cell finishes running
Close the notebook
Send back the output from the jupyter output tab again.

where the notebook is put in path /home/UNAME_MASKED/projects/PROJ_NAME_MASKED/notebooks/data/test_shutdown.ipynb and the following commands are run:
import torch
torch.randn([1000,1000,1000]).to('cuda:4')

No outputs showed during clearing, saving or closing.

However, copying the notebook to my user directory (~/), and then repeating the test steps, makes the notebook successfully shutdown on close.
In this case, here's the outputs when closing the tag:
info 13:38:33.725: Disposing kernel .jvsc74a57bd0bc647066252c151e8b77172140ebafaaf9f6fd759b9f41976512ca56a38c2bc9./home/UNAME_MASKED/miniconda3/envs/sc/python./home/UNAME_MASKED/miniconda3/envs/sc/python.-m#ipykernel_launcher for notebook /home/UNAME_MASKED/test_shutdown.ipynb due to selection of another kernel or closing of the notebook
info 13:38:33.725: Dispose Kernel '/home/UNAME_MASKED/test_shutdown.ipynb' associated with '/home/UNAME_MASKED/test_shutdown.ipynb'
debug 13:38:33.726: Cancel pending cells
debug 13:38:33.726: Shutdown session - current session, called from Error:
	at Bp.shutdownImplementation (/home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2000312134/out/extension.node.js:17:134167)
	at Bp.dispose (/home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2000312134/out/extension.node.js:17:128671)
	at /home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2000312134/out/extension.node.js:17:302456
	at Zm.dispose (/home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2000312134/out/extension.node.js:17:302664)
	at _v.onDidChangeSelectedNotebooks (/home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2000312134/out/extension.node.js:17:478382)
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at C.$acceptNotebookAssociation (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:98:90730)
	at l.N (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:11239)
	at l.M (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:10957)
	at l.H (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:10044)
	at l.G (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:9022)
	at /home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:7810
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at p.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:14861)
	at /home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:122:15815
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at p.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:14861)
	at t.E (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:18927)
	at /home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:16915
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at h.acceptChunk (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:12592)
	at /home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:11879
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at d.t (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:28518)
debug 13:38:33.727: shutdownSession c43509ad-fa20-4b7b-b9e3-d4d0c73afa79, .jvsc74a57bd0bc647066252c151e8b77172140ebafaaf9f6fd759b9f41976512ca56a38c2bc9./home/UNAME_MASKED/miniconda3/envs/sc/python./home/UNAME_MASKED/miniconda3/envs/sc/python.-m#ipykernel_launcher - start
debug 13:38:33.727: Session can be shutdown .jvsc74a57bd0bc647066252c151e8b77172140ebafaaf9f6fd759b9f41976512ca56a38c2bc9./home/UNAME_MASKED/miniconda3/envs/sc/python./home/UNAME_MASKED/miniconda3/envs/sc/python.-m#ipykernel_launcher
info 13:38:33.727: Dispose Kernel process 136351.
debug 13:38:33.743: Kernel got disposed, hence there is no longer a kernel associated with /home/UNAME_MASKED/test_shutdown.ipynb
debug 13:38:33.745: Disposing request as the cell was deleted /home/UNAME_MASKED/test_shutdown.ipynb
debug 13:38:33.754: Cancel executions after closing notebook /home/UNAME_MASKED/test_shutdown.ipynb
debug 13:38:33.757: Storing Preferred remote kernel for /home/UNAME_MASKED/test_shutdown.ipynb is undefined
debug 13:38:33.794: Disposed Kernel process 136351.
debug 13:38:33.794: shutdownSession c43509ad-fa20-4b7b-b9e3-d4d0c73afa79, .jvsc74a57bd0bc647066252c151e8b77172140ebafaaf9f6fd759b9f41976512ca56a38c2bc9./home/UNAME_MASKED/miniconda3/envs/sc/python./home/UNAME_MASKED/miniconda3/envs/sc/python.-m#ipykernel_launcher - shutdown complete
debug 13:38:33.796: Shutdown session - get restart session
debug 13:38:33.796: Shutdown session -- complete
debug 13:38:34.314: KernelProcess Exit Exit - undefined /home/UNAME_MASKED/miniconda3/envs/sc/lib/python3.8/site-packages/traitlets/traitlets.py:2412: FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use 'hmac-sha256' instead of '"hmac-sha256"' if you require traitlets >=5.
  warn(
/home/UNAME_MASKED/miniconda3/envs/sc/lib/python3.8/site-packages/traitlets/traitlets.py:2366: FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use '23078666-3236-480e-a3d6-28187eb88f39' instead of 'b"23078666-3236-480e-a3d6-28187eb88f39"'.
  warn(

VS Code Version
1.75.0
Jupyter Extension Version
v2023.1.2000312134
Jupyter logs
No response
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
None

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

Please close the notebook and provide the logs

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

Please close the notebook and provide the logs

Thanks, sure.
NOTE: After closing all notebooks and reloading vscode, I find the problem disappeared. Here are the log outputs. However, I am pretty sure the problem exists in some situations, maybe when I have too many notebooks opened. When I find this problem the next time, I will reopen the issue and provide the complete logs. Thank you!
Here are the logs when I tried to reproduce the issue but failed. I am not sure it is helpful or not, so I attach them here ayway.
reload vscode and open the notebook
too long for github, needed?

run the cells
too long for github, needed?

clear all outputs, save and close
info 13:28:23.231: Disposing kernel .jvsc74a57bd0bc647066252c151e8b77172140ebafaaf9f6fd759b9f41976512ca56a38c2bc9./home/UNAME_MASKED/miniconda3/envs/sc/python./home/UNAME_MASKED/miniconda3/envs/sc/python.-m#ipykernel_launcher for notebook /home/UNAME_MASKED/projects/PNAME_MASKED/notebooks/MERFISH/test_shutdown.ipynb due to selection of another kernel or closing of the notebook
info 13:28:23.231: Dispose Kernel '/home/UNAME_MASKED/projects/PNAME_MASKED/notebooks/MERFISH/test_shutdown.ipynb' associated with '/home/UNAME_MASKED/projects/PNAME_MASKED/notebooks/MERFISH/test_shutdown.ipynb'
debug 13:28:23.232: Cancel pending cells
debug 13:28:23.233: Shutdown session - current session, called from Error:
	at Bp.shutdownImplementation (/home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:134167)
	at Bp.dispose (/home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:128671)
	at /home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:302456
	at Zm.dispose (/home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:302664)
	at _v.onDidChangeSelectedNotebooks (/home/UNAME_MASKED/.vscode-server/extensions/ms-toolsai.jupyter-2023.1.2010391206/out/extension.node.js:17:478382)
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at C.$acceptNotebookAssociation (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:98:90730)
	at l.N (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:11239)
	at l.M (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:10957)
	at l.H (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:10044)
	at l.G (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:9022)
	at /home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:106:7810
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at p.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:14861)
	at /home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:122:15815
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at p.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:14861)
	at t.E (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:18927)
	at /home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:16915
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at h.acceptChunk (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:12592)
	at /home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:11879
	at f.invoke (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
	at d.fire (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
	at d.t (/home/UNAME_MASKED/.vscode-server/bin/e2816fe719a4026ffa1ee0189dc89bdfdbafb164/out/vs/workbench/api/node/extensionHostProcess.js:72:28518)
debug 13:28:23.234: shutdownSession 2e1f899c-233b-490d-a004-bfbd5d3ac1c1, .jvsc74a57bd0bc647066252c151e8b77172140ebafaaf9f6fd759b9f41976512ca56a38c2bc9./home/UNAME_MASKED/miniconda3/envs/sc/python./home/UNAME_MASKED/miniconda3/envs/sc/python.-m#ipykernel_launcher - start
debug 13:28:23.234: Session can be shutdown .jvsc74a57bd0bc647066252c151e8b77172140ebafaaf9f6fd759b9f41976512ca56a38c2bc9./home/UNAME_MASKED/miniconda3/envs/sc/python./home/UNAME_MASKED/miniconda3/envs/sc/python.-m#ipykernel_launcher
info 13:28:23.234: Dispose Kernel process 132864.
debug 13:28:23.250: Kernel got disposed, hence there is no longer a kernel associated with /home/UNAME_MASKED/projects/PNAME_MASKED/notebooks/MERFISH/test_shutdown.ipynb
debug 13:28:23.256: Disposing request as the cell was deleted /home/UNAME_MASKED/projects/PNAME_MASKED/notebooks/MERFISH/test_shutdown.ipynb
debug 13:28:23.260: Cancel executions after closing notebook /home/UNAME_MASKED/projects/PNAME_MASKED/notebooks/MERFISH/test_shutdown.ipynb
debug 13:28:23.264: Storing Preferred remote kernel for /home/UNAME_MASKED/projects/PNAME_MASKED/notebooks/MERFISH/test_shutdown.ipynb is undefined
debug 13:28:23.299: Disposed Kernel process 132864.
debug 13:28:23.299: shutdownSession 2e1f899c-233b-490d-a004-bfbd5d3ac1c1, .jvsc74a57bd0bc647066252c151e8b77172140ebafaaf9f6fd759b9f41976512ca56a38c2bc9./home/UNAME_MASKED/miniconda3/envs/sc/python./home/UNAME_MASKED/miniconda3/envs/sc/python.-m#ipykernel_launcher - shutdown complete
debug 13:28:23.302: Shutdown session - get restart session
debug 13:28:23.302: Shutdown session -- complete
debug 13:28:23.585: KernelProcess Exit Exit - undefined /home/UNAME_MASKED/miniconda3/envs/sc/lib/python3.8/site-packages/traitlets/traitlets.py:2412: FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use 'hmac-sha256' instead of '"hmac-sha256"' if you require traitlets >=5.
  warn(
/home/UNAME_MASKED/miniconda3/envs/sc/lib/python3.8/site-packages/traitlets/traitlets.py:2366: FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use '401e7d8c-05c4-4768-bbe4-decaf11f0118' instead of 'b"401e7d8c-05c4-4768-bbe4-decaf11f0118"'.
  warn(

@AaronNing
sorry i missed this
Yes, the logs are requried, please could you save them to a text file and then upload the text files to an issue here

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.

Hello,
I am seeing the same issue. I have set logging to Verbose, then reloaded the window. Here attached you will find the logs.

At 13:00, I have reloaded the window.
I wait one minute. At 13:01, I opened the notebook
I wait one minute. At 13:02, I ran the first cell
I wait one minute. At 13:03, I close the notebook (you will notice there is no entry in logs at 13:03).
I wait one minute. At 13:04 I copy all from Output > Jupyter

Contents of first cell:
import fiftyone as fo
# import json
import ujson as json
from PIL import Image
import numpy as np
import pandas as pd

from pathlib import Path

vscode-jupyter-closing.log
I can still see the kernel running, both in ps -ef, and in Jupyter Power tools > Active jupyter sessions :

Note there is no notebook tab opened.
At this point, I realise I can click Stop button (⏹ ), which generates the following lines in the output:
13:06:50.176 [info] Interrupt kernel execution
13:06:50.176 [debug] Cancel pending cells
13:06:50.178 [info] Interrupt requested ~/ODISE/notebooks/process-iSAID.ipynb
13:06:50.179 [info] Interrupt kernel execution
13:06:50.180 [info] Interrupting kernel: pythonjvsc74a57bd02124a9dfd21b2e4b4b151fbb71e480ecc5b2e888175381ca9a5e114ed5217ff5
13:06:50.181 [info] Interrupting kernel via SIGINT
13:06:50.186 [info] Interrupt requested & sent for ~/ODISE/notebooks/process-iSAID.ipynb in notebookEditor.

So Stop is actually interrupt, not full shut down.

@cipri-tom I'm sorry you are running into this, please could you file a new issue and I'll take a look


Navigation not causing view to appear

Question
What would cause a view not to appear after pushing a screen onto the nav stack?
Problem description
I added debug() to my navigator. On the left is the initial navigation event that happens when the app loads. On the right is after sending a navigation event like this:
environment.navigator.go(to: TabNavigationScreen(), on: screenID)

where screenID is the ID of the screen that has the button. It also happens to be the root screen, i.e. 00000000-0000-0000-0000-000000000000.

I don't have a concise code sample to post, and I'll be making a sample project as my next debugging step, but I wanted to post this in case there was something obvious I was missing. How can I get hasAppeared: false to turn into hasAppeared: true?

Hello, we faced with exact same problem, but cannot come up with solution, @ohitsdaniel could you please help us?

Could you please provide an example navigation tree in which the problem occurs? The iOS Version and device the problem occurred on might help as well.
@ZevEisenberg is using a custom path builder implementation and we solved it by rewriting parts of it.

Oh, I see @ohitsdaniel. So basically when I call .go(to:on:) function nothing happens, but it shows that view has been added to stack, here is our nav tree:
// CheckoutScreen:

Screen(
    content: { (screen: CheckoutScreen) in
        CheckoutView(checkoutState: screen.$checkoutState)
    },
    nesting: {
        AddressListScreen.Builder()
        ReceiversListScreen.Builder()
        PaymentMethodsScreen.Builder()
        PromocodeDescriptionScreen.Builder()
    }
)

// AddressListScreen:

Screen(AddressListScreen.self) {
    AddressListView()
} nesting: {
    AddressScreen.Builder()
}

Specs:
iOS 15.0
swift-composable-navigator 0.2.2

@onl1ner I had a similar setup to yours (although the variable in the screen wasn't a binding/state) and noticed a similar issue when trying to work with the deeplinker.
Basically on startup the app will show AScreen with a variable value of nil to display a loading screen. The deeplinker will parse the link into the following path [AScreen(value: "hello"), BScreen()]. Since the deeplinker uses replace(path:) it will successfully replace AScreen but fails at presenting BScreen. Parsing the link so that the value of AScreen is nil will present BScreen fine. So it seems the issue is with the value changing.
To get around this I overrode the equal function to only compare the presentationStyle.
extension EstablishmentScreen {
    static func == (lhs: Self, rhs: Self) -> Bool {
        lhs.presentationStyle == rhs.presentationStyle
    }
}

probably not the best way to solve it, but its a good temporary work around

Thanks for your input @KenLPham!
My first assumption would also go in a similar direction:
Is $checkoutState optional state that you unwrap in the view layer? I think it's a pretty cool idea to hand down view models/bindings through screens, just wondering how optional state should be filled in the deeplink case.
Maybe it is an issue in the Navigator.Datasource that only emits a new path if there were changes. Is your $checkoutState a reference or a value type? And it is Hashable/Equatable?
I guess we should track this case in a separate issue because it isn't really related to the original poster's question.


Push capacity to metric backends

A part of this issue is to figure out how monitoring backends will handle capacity and then push capacity accordingly. Capacity is mostly static. One option is to treat it just like metrics and push it just once.

Capacity doesn't make sense as a metric. If needed it can be used for computing other metrics eg. currently we export node utilization as node usage divided by node capacity.


Be helpful when generator is not installed

We should be helpful when a user tries to run a generator that is not installed. If it exists on npm, we should show how to install it, if not, we could search the generator list for similar ones and suggest them.
Similar to https://github.com/Homebrew/homebrew-command-not-found.

Also, it'd be useful to suggest troubleshooting information. (basically, run yo doctor)
I believe I've looked at this issue a little while back and realized it was actually rooted into yeoman-environment. We probably should update the way this module find and run generator to allow surfacing these errors to the UI layers.

With the NPM search would we want to somehow find a 'top' result?
Example: I wanted to run yo angular2. It doesn't find one. So I try to search

npm search yeoman-generator generator-

that should get me a pretty good result so I could probably take the top 1 and add some text after it to say "If this doesn't look like what you want try searching..." or similar.
My main question probably is on the time of exeuction. At the minute yo is pretty lightning when it comes to this. I typo something yo angluar2 or similar and bang it lets me know. If you go off and do an npm search isn't that going to keep me waiting for a bit? It seems to take a fair bit of time locally for me anyway so if that's ok and the feature is still wanted would you want it hidden behind a flag or something?
Wondering if https://github.com/yeoman/yo/issues/361 and the generator list might be a speedier search mechanism for this? From my understanding, very limited as I'm a newb :smile: , it seems like reasonably similar implementation to the homebrew-command-not-found as it seems to operate a db or commands and aliases?

Partly fixed with: https://github.com/yeoman/environment/pull/70?

Talking with npm would be an awesome addition though 👌


⚠ Bofrost.be has degraded performance

In 315a10a, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1742 ms

Resolved: Bofrost.be performance has improved in fd2f962 after 17 minutes.


Sample app: Implemented filter for gallery pages

Description of Change
Now you can filter sections in the galleries of the sample app.
It helps to find the needed page by filtering items source.

Focus entry
Input a part of title of the item you are looking for.
Press "Search"
Filtered items appear

API Changes
None
Behavioral Changes
None
PR Checklist

[ ] Has tests (if omitted, state reason in description)
[X] Has samples (if omitted, state reason in description)
[X] Rebased on top of main at time of PR
[X] Changes adhere to coding standard

@jfversluis as requested :)


Incorrect predicate application in EagerTestSession and GraphTestSession

I believe this is a widespread broken pattern in EagerTestSession and GraphTestSession:
        o.asTensor()
            .scalars()
            .forEachIndexed((idx, f) -> assertTrue(predicate.test(o.asTensor().getFloat())));

Notice that f is ignored in the lambda, and o is referenced directly instead. getFloat then returns the zero'th element of the tensor.
@JimClarke5, am I right here?

Where are you seeing this?  I cannot find it in TestSession, EagerTestSession or GraphTestSession.
It may have been something I already fixed when I refactored TestSession a few PRs ago.
The closest I can find to the above is:
TestSession: 1089-1093 in my copy.
  if (isScalar) {
      assertTrue(predicate.test(tensor.getObject()));
    } else {
      tensor.scalars().forEachIndexed((idx, s) -> assertTrue(predicate.test(s.getObject())));
    }

Here's an example in master.

Here's the example I originally looked at.

I have dramatically refactored all this, maybe my version hasn't been pushed yet.
I know the refactor is  in my Layers1 branch (not pushed). I'll check Metrics2, #222, branch to see if it is in there.

The refactor is in Layers1, not yet pushed. I am ready to push this, but have been holding off for other PR's to be approved first.


first pass at email-suppressions

one approach to making sure we don't send emails to people who have suppressed emails via sendgrid:

local EmailSuppressions table with columns for email and suppression_type to store remote sendgrid data locally
sync_suppressions tool to import data from SendGrid
when we check user.prefers_no_email, also check whether the user's email is represented in the EmailSuppressions table
allow database queries like this to export lists of people to email:

SELECT count(*)
FROM   users u
LEFT   JOIN preferences p ON p.owner_id = u.id AND p.owner_type = ‘User’ AND p.name = ‘no_email’
LEFT   JOIN email_suppressions s ON s.email = u.email AND s.suppression_type NOT IN (“news_from_inaturalist”, “transactional_emails”, “account_emails”)
WHERE  (p.value = ‘t’ OR p.id IS NULL)
AND (s.id IS NULL)
AND u.email IS NOT NULL
AND u.suspended_at IS NULL
AND u.site_id = 1
AND u.locale =  ‘en’;

@kueda this is pretty bare bones but wanted to see if you think this is an ok approach before continuting


Update ESRPCodeSigningTask to Version 5; Use WindowsAppSDK-EsrpCodeSigning-Steps.yml From WindowsAppSDKConfig Repository

A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.

/azp run

/azp run

Validated here
https://microsoft.visualstudio.com/ProjectReunion/_build/results?buildId=101713310&view=results


2d segmentation

Hello,  do you have a conf.ini file example for 2d image segmentation ? Can I feed a network with png images and png labels ?

Hi @mariamhrr , at the moment we don't have any concrete example of 2d image segmentation and png format is not supported. Contributions are welcomed!

@mariamhrr @wyli Since the merge of image-loader NiftyNet now fully supports 2D images without having to convert them to NiftyFormat. There is no need to fake 3-dimensional spatial_window_size either (although it is perfectly ok if you do).
NiftyNet currently supports loading images from OpenCV, Scikit-Image and PIL/Pillow, assuming that you have the corresponding libraries installed. You can specify a loader in the config file, or it will automatically try to find one that can handle yout images.
For more information check image_loader.py.
Example configuration file:
[images]
path_to_search = ~/data/test_image_segmentation/
filename_contains = bmp
spatial_window_size = (224, 224)
interp_order = 1
loader = opencv

[masks]
path_to_search = ~/data/test_image_segmentation/
filename_contains = _mask
spatial_window_size = (224, 224)
interp_order = 0
loader = skimage


Lack of testID on native base component types result in Property 'testID' does not exist on type 'IntrinsicAttributes  error

I have gone through these following points

[X]   Check latest documentation: https://docs.nativebase.io/
[X]   Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[X]   Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[X]   Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[X]   For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[X]   For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description

node, npm, react-native, react and native-base version, expo version if used, xcode version
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>xcode 10
Expected behaviour
testID to be declared on all Native base types
Actual behaviour
inside index.d.ts there is no declaration of testID on any of native base types
which result in the following error when adding testID on Native base components

Property 'testID' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes & Readonly<{ children?: ReactNode; }> & Readonly'.

Steps to reproduce
In Typescript project add testID on Container component

Commit https://github.com/GeekyAnts/NativeBase/commit/5d6c1556799aba7549f11a274d1273b63d0e6530

commit: https://github.com/GeekyAnts/NativeBase/commit/5d6c1556799aba7549f11a274d1273b63d0e6530
adds testId in native base components, but testId is supported only for IOS,  accessibilityLabel and accessible fields are also needed for working with android.
Someone please look into this.


Helix unreachable src/scanner.c

Hi,
There seems to be an issue in helix (didn't try with other terminal editor such as vim/nvim), i'm guessing it's from the grammar, i tried to deactivate both lsp and formatter, still had the issue, and there is a src/scanner.c file in the repo.
I installed the grammar by cloning and symlinking the right files to the right place just as explained in the readme.
Updated to master but nothing changed, tried with konsole kitty wezterm and tty.
This is the issue, it's popping whenever it's loading the grammar

It appears to be linked to a specific file in my project

Yes, it is a debugging check in this grammar. It means the grammar contains a bug, as those print statements are placed whenever a situation should be unreachable.
You can silence those messages by removing in the src/scanner.c the #define DEBUG macro. I am thinking about changing how to report unexpected behaviors. Because those messages are annoying, but in the other hand, they are good bug detectors.
I will comment the #define DEBUG in order to distribute only a silent implementation. I will investigate the bug in question, but I need you to give me the content of the file that causes those prints. I need to be able to reproduce it on my machine.

I had no c/cpp compiler, installing one made it so i can update the grammar and resolving this issue.
I curious to know how the grammar was still working before i installed a compiler, just giving that error in stdout.
So it's fixed for me at this point, but that's still wierd

I made a commit that removes the print statement.
"No C compiler" yes it is strange, I know Helix ships its officially supported grammars, already compiled. But this grammar is not yet in the official list, but it will starting from the next Helix release.
Can you give the content (if it's not personal) of the main.typ ? Because it is the only way for me to reproduce the bug.

test.zip
Hopefully you can compile it, if it's not the case just tell me i'll try to put this on a github. There is a template with some macros in it


Updated and now existing firmware code shows errors

Issue Type: Bug
I recently did the suggested updates to the Visual Studio that I was prompted for.   I previously had no problems editing and compiling the firmware code for my MARLIN  software to use with my 3D printer.
Today I opened up the existing code to make a couple minor changes  and the code is listed has having "63 problems with this file" that it did not have previously.
Example " Function call is not allowed in a constant expression"
This is the statement that is generating that error
' #if ENABLED(NOZZLE_CLEAN_FEATURE) '
pretty much every '#if' in the Configuration.h file is now an error.
VS Code version: Code 1.60.2 (7f6ab5485bbc008386c4386d08766667e155244e, 2021-09-22T12:00:31.514Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (4 x 3193)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.90GB (1.94GB free)

Process Argv
--crash-reporter-id b65c05c0-5847-4e64-a0ce-e38de35d5c3d

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

auto-build
mar
2.1.34

cpptools
ms-
1.6.0

platformio-ide
pla
2.3.3

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
vsccppwt:30378364
pythonvssor306:30344512
bridge0708:30335490
pygetstartedt2:30371810
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30364666
pythonvspyt187:30373474
pydsgst2:30361792
vsqsis400:30374798
vsaa593:30376534

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.
Happy Coding!


Create runners/core module for artifact org.apache.beam:runners-core

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

This is strictly creating the module and moving one easy class to it.
Many of the utilities in org.apache.beam.util and subpackages should
move as developments allow.

R: @davorbonaci @jbonofre
I haven't worked too hard at the pom.xml. I also haven't gone through the loop of letting the dependency analysis clean up the deps, but this is the basic idea. Please comment!

Please take another look when you get a chance. The two commits are independent, not to be squashed.

LGTM, modulo resolution of pending comments. (I probably don't need to take another look, unless there's something contentious.)


v7.3: Windows build requirements error (with fix)

I just ran into this while installing via setup.py install on a windows system w/Python 2.7.13:

Processing dependencies for coloredlogs==7.3
Searching for r
Reading https://pypi.python.org/simple/r/
No local packages or working download links found for r
error: Could not find suitable distribution for Requirement.parse('r')
The problem:
setup.py, function: get_install_requires()
You check for win32 to determine if you need to add colorama as a dependency.  The problem is you use install_requires.extend with 'colorama' as the arg.  extend, however, expects an iterable, so it turns "colorama" into ["c", "o", "l", "o", "r", "a", "m", "a"].
The fix:
File: setup.py
Change:
            install_requires.extend('colorama')
to either:
            install_requires.append('colorama')
or:
            install_requires.extend(['colorama'])

Thanks for the clear bug report @btxgit, this has been fixed in version 7.3.1.


--external-downloader-args should be ignored when --external-downloader isn't used

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.09.27. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.09.27

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v https://twitter.com/CrazyByAnittaOf/status/780841028303646720
[debug] System config: []
[debug] User config: ['--external-downloader=aria2c', '--external-downloader-args=--file-allocation=falloc --max-connection-per-server=10 --min-split-size=1M', '--netrc', '--ignore-errors', '--prefer-ffmpeg']
[debug] Command-line args: ['-v', 'https://twitter.com/CrazyByAnittaOf/status/780841028303646720']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.09.27
[debug] Python version 3.5.1 - Darwin-16.0.0-x86_64-i386-64bit
[debug] exe versions: avconv 11.4, avprobe 11.4, ffmpeg 3.1.2, ffprobe 3.1.2, rtmpdump 2.4
[debug] Proxy map: {}
[twitter]<PHONE_NUMBER>03646720: Downloading webpage
[twitter:card]<PHONE_NUMBER>03646720: Downloading webpage
[twitter:card]<PHONE_NUMBER>03646720: Downloading m3u8 information
[debug] Invoking downloader on 'https://video.twimg.com/ext_tw_video/780840843628380161/pu/pl/480x480/1ne3LEaCrDHpwPvG.m3u8'
[download] Destination: Crazy By Anitta - MINHA amoree #MPN #anitta-780841028303646720.mp4
[debug] ffmpeg command line: ffmpeg -y --file-allocation=falloc --max-connection-per-server=10 --min-split-size=1M -headers 'Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Accept-Language: en-us,en;q=0.5
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20150101 Firefox/47.0 (Chrome)
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip, deflate
' -i https://video.twimg.com/ext_tw_video/780840843628380161/pu/pl/480x480/1ne3LEaCrDHpwPvG.m3u8 -c copy -f mp4 -bsf:a aac_adtstoasc 'file:Crazy By Anitta - MINHA amoree #MPN #anitta-780841028303646720.mp4.part'
ffmpeg version 3.1.2 Copyright (c) 2000-2016 the FFmpeg developers
  built with Apple LLVM version 7.3.0 (clang-703.0.31)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/3.1.2 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-opencl --enable-libx264 --enable-libmp3lame --enable-libxvid --enable-libfreetype --enable-libtheora --enable-libvorbis --enable-libvpx --enable-librtmp --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfaac --enable-libass --enable-ffplay --enable-libspeex --enable-libschroedinger --enable-libfdk-aac --enable-libopus --enable-frei0r --enable-libx265 --disable-lzma --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-cflags= --enable-nonfree --enable-vda
  libavutil      55. 28.100 / 55. 28.100
  libavcodec     57. 48.101 / 57. 48.101
  libavformat    57. 41.100 / 57. 41.100
  libavdevice    57.  0.101 / 57.  0.101
  libavfilter     6. 47.100 /  6. 47.100
  libavresample   3.  0.  0 /  3.  0.  0
  libswscale      4.  1.100 /  4.  1.100
  libswresample   2.  1.100 /  2.  1.100
  libpostproc    54.  0.100 / 54.  0.100
Unrecognized option '-file-allocation=falloc'.
Error splitting the argument list: Option not found

ERROR: ffmpeg exited with code 1
  File "/Users/silvior/anaconda/lib/python3.5/runpy.py", line 170, in _run_module_as_main
    "__main__", mod_spec)
  File "/Users/silvior/anaconda/lib/python3.5/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/bin/youtube-dl/__main__.py", line 19, in <module>
    youtube_dl.main()
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 449, in main
    _real_main(argv)
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 439, in _real_main
    retcode = ydl.download(all_urls)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1791, in download
    url, force_generic_extractor=self.params.get('force_generic_extractor', False))
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 705, in extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 776, in process_ie_result
    new_result, download=download, extra_info=extra_info)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 751, in process_ie_result
    return self.process_video_result(ie_result, download=download)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1435, in process_video_result
    self.process_info(new_info)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1699, in process_info
    success = dl(filename, info_dict)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1641, in dl
    return fd.download(name, info)
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 354, in download
    return self.real_download(filename, info_dict)
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/external.py", line 43, in real_download
    self.get_basename(), retval))
  File "/usr/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 162, in report_error
    self.ydl.report_error(*args, **kargs)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 568, in report_error
    self.trouble(error_message, tb)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 530, in trouble
    tb_data = traceback.format_list(traceback.extract_stack())

Description of your issue, suggested solution and other information
When I tried to download a video from twitter, youtube-dl used the args passed to aria2c from ~/.config/youtube-dl/config to ffmpeg causing the above error.

Duplicate of #9268.

This bug makes it impractical to use external-downloader-args in youtube-dl's config,
and easier to miss that downloads have failed when downloading playlists (because ffmpeg would exit with a red error but that would be rapidly buried by the scrolling terminal).
A workaround is to remove external-downloader-args and put those arguments directly into $XDG_CONFIG_HOME/aria2/aria2.conf. Note that aria2c will be expanding this  XDG_CONFIG_HOME environment variable, hence it can be changed to a custom location for a specific youtube-dl's scope in case one does not want to use and modify their user's aria2.conf and youtube-dl's config.


Add resend confirmation email strings

@dcsjapan thanks for comments
I'll wait for @tobscure about https://github.com/flarum/core/pull/862, I think there are gonna be some changes, then I apply your suggestions

Glad to help! And thanks for the PRs, as always!

@dcsjapan  how about now? please let me know if something need to be changed

Looks good!

It will be perfect if the commentary ends with a period like the rest of them! :smile:

@maelsoucaze done :smile:

:+1:


Update ScubaGear Demo video

💡 Summary
In support of demos and the workshop initiatives, CISA has requested the video demo of installing and running the ScubaGear tool to be updated to at least the v1.0.0 version of the tool.
Motivation and context
This is useful because the current version is utilizing the v0.3.0 release and should be updated to at least v1.0.0 as our official first release to avoid confusion. Also the demo should be updated to include an overview of the permissions required since this question has been brought up beforehand.
Implementation notes
recreate and update the demo recording that previews the following:

where to download the tool
noting the permissions needed to run the tool
how to extract the tool
how to run the tool
note the use case and how to use config files
expected pop-ups and time jumps to lower the recording time
review the sample report

Acceptance criteria
How do we know when this work is done?

[ ] New demo includes details listed in implementation notes
[ ] demo is able to be share internally to MITRE and to CISA

assigned this to you @schrolla only because you created the first demo but feel free to reassign!

moving the issue to the next release to update the video with PSGallery installation support coming in the v1.2.0 release.

moved to blocked, awaiting update to readme file with psgallery steps found in issue #987

after meeting with the CDET and PMSS teams the MITRE team is responsible for the following supplemental videos and artifacts:

Updated demo video (video only) with PSGallery install
Associated script for the demo
video of remediation steps to update a policy (one from Entra ID / AAD) and rerun of the tool to show "PASS" results
associated script for the remediation video

the CDET team noted to Roger that a first cut should be out to him for review by the end of this week!

@ahuynhMITRE Any updated status on this issue or when the demo will be available? This issue has been outstanding for a long time. May need to either re-craft to more short term, sprint scoped goals or track another way.

Issue Update:

01 Nov 2024: Received first cut of updated demo on 01 Nov 2024.
04 Nov 2024: Andrew and Roger sent feedback and comments back to the CDET team for adjudication.

current status:

re-recroded demo portions sent to CDET team on 11/6
additional comments sent on 11/9
CDET team noted a turnaround time of week of 11/18

current status according to the CB Publication Dashboard:

12/17 JCDC pubs confirmed that EAD approved the video storyboard and it is now with CISA front office for approval


Ensure tags are always marshalled the same way

This added check ensures it's always alphabetically ordered when
marshalled.

Test code only, inspired by comment: https://github.com/influxdb/influxdb/pull/2696#issuecomment-110534859
Green build, merging now.


Fix matching of edit paths to original file paths on Windows

Fixes #3

Could you try it out and let me know if it works? @pawamoy

Yep, working fine! That's great, thanks 🙂

Could you release something like 0.3.4 🙏 🥺 ?

Certainly. Don't know what I was even waiting for. It is done.

Thanks a lot :blush:


Issue811 sleep efficiency

Closes #811 => added new parameter relyonguider_SleepEfficiency to handle how to calculate sleep efficiency in part 4 (note this is not applied in part 5 where sleep efficiency would always be sleep time / spt). If relyonguider_SleepEfficiency = FALSE (default), then the algorithm do NOT use the user-provided wake up time and the denominator is spt+latency (as proposed here). If relyonguider_SleepEfficiency = TRUE, then the denominator is the guider_spt as in previous GGIR versions.

Checklist before merging:

[ ] Existing tests still work (check by running the test suite, e.g. from RStudio).
[ ] Added tests (if you added functionality) or fixed existing test (if you fixed a bug).
[ ] Updated or expanded the documentation.
[ ] Updated release notes in inst/NEWS.Rd with a user-readable summary. Please, include references to relevant issues or PR discussions.
[ ] Added your name to the contributors lists in the DESCRIPTION and CITATION.cff files.

Codecov Report

Merging #890 (9f89889) into master (36dd97b) will decrease coverage by 0.01%.
The diff coverage is 83.33%.

:exclamation: Current head 9f89889 differs from pull request most recent head 3bf8381. Consider uploading reports for the commit 3bf8381 to get more accurate results

: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             @@
##           master     #890      +/-   ##
==========================================
- Coverage   78.12%   78.11%   -0.01%
==========================================
  Files          91       91
  Lines       12094    12096       +2
==========================================
+ Hits         9448     9449       +1
- Misses       2646     2647       +1

Files Changed
Coverage Δ

R/g.part4.R
80.02% <75.00%> (-0.09%)
:arrow_down:

R/check_params.R
97.61% <100.00%> (ø)

R/load_params.R
99.12% <100.00%> (ø)


Adding Azure App Configuration component

Adds Azure App Configuration component
TODOs

[x] Unify common properties in pom.xml with parent pom.xml
[ ] Add JavaDocs
[x] Ensure this works on JDK 11. (Currently fails when run against it. But works on JDK 8.)

Can one of the admins verify this patch?

Not a fan of the method naming change in #3188. I really want to retain the naming as it was.

@JonathanGiles  Would 'addSetting' be better? I removed KeyValue because they're known as "ConfigurationSettings" now. Or would addConfigurationSetting/updateConfiguartionSetting be better?

I am fine with shortening it in all cases to just <verb>Setting.


there is a memory leak

in -autoSwitchBannerView method, performSelector:withObject:afterDelay will retain self, and cause a memory leak.

Tkx, you can pull a Pull Request


Added a server status message that gets sent out

Added server status information to the message and server data structures. These allow for the leader to send out which servers are bad on heartbeat. This makes it so that every server knows the working list which makes it easier to tell which votes to expect during elections.

disregard checkvotes() change, I misunderstood how raft works.


[ISSUE #3919] fix postgres init sql has error

About #3919
Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

@MiracleDx hi，pls resolve conflicts

Codecov Report

Merging #3920 (d626bf1) into master (443fb4a) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #3920   +/-   ##
=========================================
  Coverage     70.42%   70.42%
- Complexity     6765     6767    +2
=========================================
  Files           923      923
  Lines         25373    25373
  Branches       2310     2310
=========================================
+ Hits          17868    17869    +1
  Misses         6133     6133
+ Partials       1372     1371    -1

Impacted Files
Coverage Δ

...che/shenyu/sync/data/http/HttpSyncDataService.java
85.71% <0.00%> (-4.09%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
63.82% <0.00%> (+1.06%)
:arrow_up:

...ruptor/RegisterClientServerDisruptorPublisher.java
64.70% <0.00%> (+11.76%)
:arrow_up:

...controller/ShenyuClientHttpRegistryController.java
100.00% <0.00%> (+22.22%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature/typed core draft

This is very much WIP. Baby steps towards a typed version of core.
TODO

[x] properly substitute types for patterns in the match compiler.
[ ] fuse elaboration and transformer to avoid inconsistent intermediate states.
[x] Maybe drop cargs again (since they are always bargs_i.capt).

I think this PR is now ready for review. A review should mostly focus on the design (also wrt to how we can also port lifted at some point).
Symbols should be treated as opaque starting from core (in the future). Some backends still use symbol information instead of looking up the information in the declarations section of the core module.

@marzipankaiser I added you as a reviewer since you are most affected by it, since you want to implement type-boxing/unboxing based on typed core.

@fritzladwig this PR could also really help you, since the new representation might be easier to test. We could easily write a parser for this core representation. The parsed trees then could be used in your tests for optimization.

Thanks @phischu for the comments. We should address them in a separate PR


GH-29 Cuckoo PoW

closes #29

can you ignore apps/aecore/c_src/ in .gitignore

the genesis_header should be updated to contain the correct pow_evidence and nonce for cuckoo

@meivantodorov can you still comment the files to name their sources?

Can you actually mine a new genesis block so it will have pow_evidence and the correct nonce

I will try out the code later and then approve

I have speed up finding the new block when we are on dev.


Zigbee Temperature Sensor shows value as Unavailable but value is found in logs

I recently re-added all my zigbee humidity and temperature sensors to ewelink after changing the dead batteries and updated sonoffLAN.
they used to work fine before, but now the shows as unavailable along with other motion sensors.
when i downloaded the diagnostics log, i was able to see the correct values in the json file:
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2024.12.2",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.13.0",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Asia/Beirut",
    "os_name": "Linux",
    "os_version": "5.15.76-v8",
    "supervisor": "2024.11.4",
    "host_os": "Home Assistant OS 9.4",
    "docker_version": "20.10.19",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "alexa_media": {
      "documentation": "https://github.com/alandtse/alexa_media_player/wiki",
      "version": "5.0.4",
      "requirements": [
        "alexapy==1.29.5",
        "packaging>=20.3",
        "wrapt>=1.14.0"
      ]
    },
    "hacs": {
      "documentation": "https://hacs.xyz/docs/configuration/start",
      "version": "1.32.1",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "hisense_tv": {
      "documentation": "https://github.com/sehaas/ha_hisense_tv",
      "version": "22.05.09",
      "requirements": [
        "wakeonlan==2.0.1"
      ]
    },
    "sonoff": {
      "documentation": "https://github.com/AlexxIT/SonoffLAN",
      "version": "3.8.1",
      "requirements": [
        "pycryptodome>=3.6.6"
      ]
    },
    "localtuya": {
      "documentation": "https://github.com/rospogrigio/localtuya/",
      "version": "5.2.1",
      "requirements": []
    }
  },
  "integration_manifest": {
    "domain": "sonoff",
    "name": "Sonoff",
    "codeowners": [
      "AlexxIT"
    ],
    "config_flow": true,
    "dependencies": [
      "http",
      "zeroconf"
    ],
    "documentation": "https://github.com/AlexxIT/SonoffLAN",
    "iot_class": "local_push",
    "issue_tracker": "/api/sonoff/c110612-53b1-4654-a947-08b48a4c04a8",
    "requirements": [
      "pycryptodome>=3.6.6"
    ],
    "version": "3.8.1",
    "is_built_in": false,
    "overwrites_built_in": false
  },
  "setup_times": {
    "null": {
      "setup": 0.0002540170000315811
    },
    "92924c49cdfe2fe36bee6b4307403d4": {
      "wait_import_platforms": -0.0002633910000326978,
      "wait_base_component": -0.0015740489999984675,
      "config_entry_setup": 4.662341347999984
    }
  },
  "data": {
    "version": "ffa7e22",
    "cloud_auth": true,
    "config": null,
    "options": {
      "debug": true,
      "homes": 1,
      "mode": "local"
    },
    "errors": [],
    "device": {
      "uiid": 1770,
      "params": {
        "bindInfos": "***",
        "subDevId": "ac581e25004b1001771",
        "parentid": "1001703b79",
        "battery": 96,
        "supportPowConfig": 1,
        "trigTime": "1734265067717",
        "temperature": "1949",
        "humidity": "5933",
        "timeZone": 2,
        "switch": "off",
        "subDevRssiSetting": {
          "active": 60,
          "duration": 5
        }
      },
      "model": "ZCL_HA_DEVICEID_TEMPERATURE_SENSOR",
      "online": true,
      "local": null,
      "localtype": null,
      "host": null,
      "deviceid": "a4b000d348"
    }
  }
}

You have enabled "mode": "local" for cloud only sensors.

Yes that was the case thank you!


⚠ Bofrost.at has degraded performance

In dfd1dbe, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 916 ms

Resolved: Bofrost.at performance has improved in bc1df10 after 13 minutes.