[bug] Spacing Not Working Through Wrapping Component Returning Children

Describe the bug
export const ShowWhenAuthed = ({ children }: RequireAuthProps) => {
  const [{ isAuthed, isInitializing }] = useAuth()

  if (isInitializing || isAuthed !== true) return null

  // TS yells when it's just children although that's valid
  return children
}

const Foo = () => {
  return (
    <YStack space="$4">
      <YStack>
        <Text>Hello</Text>
      </YStack>
      <ShowWhenAuthed>
        <YStack>
          <Text>Hello</Text>
        </YStack>
      </ShowWhenAuthed>
      <YStack>
        <Text>Hello</Text>
      </YStack>
    </YStack>
  )
}

When I do this, the spacing spans are not added. It's like the wrapping component doesn't factor it in.

There should be 2 spaces here right?

Yeah, it's really hard to reproduce easily. I have a bunch of little things I could show you live similar to this

Yea this is a know issue, one of the oldest open issues just because we can't do anything about it. Once gap comes we'll be good. Closing in favor of the old issue for now.


Certificate pinner doesn't work if host name has capital letters

If certificate pinner is set for host "www.HOST.com" if doesn't apply to the calls that has endpoint "www.host.com".
The CertificatePinner.findMatchingPins() should ignore the case because http doesn't care if the name is in uppercase or not.
Tested with OkHttp 2.7.5.

Why not pass lowercased hostname to the CertificatePinner?
On Tue, 7 Jun 2016, 12:54 jkauppin<EMAIL_ADDRESS>wrote:

If certificate pinner is set for host "www.HOST.com" if doesn't apply to
the calls that has endpoint "www.host.com".
The CertificatePinner.findMatchingPins() should ignore the case because
http doesn't care if the name is in uppercase or not.
Tested with OkHttp 2.7.5.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/2609, or mute the thread
https://github.com/notifications/unsubscribe/AA7B3IzOgks5lleB9tk7MCZNIQYknE4mks5qJT_WgaJpZM4Ivv_6
.

Yes, that was the fix on the app. However that feels unsafe since a small typo in the host will disable the certificate pinning. From http point of view capital letters has no meaning.

Yeah, we should fix this.


module: remove system paths from search

Fixes #1390

Committed at https://github.com/atom/electron/commit/4983ef77bd3382c6c05e31a33b95621abbe5bc69.


Proper msg caching

This PR replaces the default 100 cabinet message limit imposed by Arikawa, to the message limit specified in the user config. This prevents loading more messages than necessary since Cabinet retrieves from API if things are missing, wasting half of the messages being sent if using the default config (of 50 messages).
Somewhat unrelated but still applies: also added a limit of 100 to MessagesLimit

Since I'm considering #444, this issue should be resolved along with it.


Bubble'z popper

PR Description 📜
I added a simple bubble-popping game using HTML, CSS, and Javascript.
By moving the cursor onto the bubbles they blast. If you miss the 10 chances the game will end.
Fixes #4212

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & [CODE OF CONDUCT](ht
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Chandu6702 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@kunjgit please review and merge this PR

@kunjgit please review and merge this PR

@kunjgit please review and merge this PR

Thank you  @Chandu6702 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


pgbouncer of type r missing

Looks like only rw and ro types are supported. Is that because 'r' cannot be supported or because of overlooking that type?

@gsimko this doesn't look like an issue, are you still having this issue ?

Closing due to no activity

I also have this issue. Does pgbouncer don't support type r?

@sxd sorry I didn't notice your reply earlier. I reported this because it's an issue for me for sure. I want to be able to reach both the primary and replica databases, and neither ro nor rw can do that.


It is no longer possible to update Kubernetes version since Rancher 2.6.4

Rancher Server Setup

Rancher version: v2.6.5
Installation option (Docker install/Helm Chart):

Docker (single Node install on AWS EC2 instance)
Docker version: 20.10.12
OS: Ubuntu 20.04.4 CIS AMI

Information about the Cluster

Kubernetes version: 1.21.10
Cluster Type (Local/Downstream):

Downstream (1x etcd, 1x controller, 3x Worker)
Infrastructure Provider = Rancher provisioning the nodes using AWS node driver
Hosted: RKE Cluster - Amazon EC2
OS on each node: Flatcar

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

Admin

Describe the bug
Cluster goes into Error state during a Kubernetes update.
To Reproduce

Provision an EC2 instance and install Rancher in version 2.6.4 or 2.6.5 (docker single node install)
Deploy a Kubernetes Cluster in Rancher
Edit the cluster configuration and increase the Kubernetes version to initiate an update

Result

The update process starts, the controller node is shown as cordoned in the Rancher UI, but after a short time we get the following error and the cluster goes into error state.
Host xxxxx-controller-1 failed to report Ready status with error: [controlplane] Error getting node xxxxx-controller-1:  "xxxxxxx-controller-1" not found

Expected Result
The controller node should be successfully updated at some point and in the Rancher UI the cordoned should disappear at the controller node and update the next node until the whole cluster is updated. After that, the cluster should be available again normally.
Screenshots

Additional context
We have already tried different Rancher version and Kubernetes versions. We noticed that this problem only appears in Rancher 2.6.4 and higher.

Rancher 2.6.3
Kubernetes Cluster 1.21.10 to 1.21.12
-> No Problems

Rancher 2.6.4
Kubernetes Cluster 1.21.10 to 1.21.12

Update does not work

Rancher 2.6.4
Kubernetes Cluster 1.22.4 to 1.22.5

Update does not work

Rancher 2.6.5
Kubernetes Cluster 1.21.13
Update Kubernetes Cluster to 1.22.4

Update does not work

Hi @Aransh,
sorry for my late feedback.
I took a close look at the kubelet logs, but we didn't seem to have the same problem as you.
The network plugin was loaded successfully
0715 07:33:41.508511   10522 docker_service.go:242] "Hairpin mode is set" hairpinMode=hairpin-veth I0715 07:33:41.671158   10522 plugins.go:168] "Loaded network plugin" networkPluginName="cni" I0715 07:33:41.671892   10522 docker_service.go:257] "Docker cri networking managed by the network plugin" networkPluginName="cni"
On the node itself, I also see that all required CNI files are in the directory /etc/cni/net.d
ip-1XX-1XX-1XX-XXX /etc/cni/net.d # ls 10-canal.conflist  calico-kubeconfig
All docker containers have been updated to the new version (1.21.13)
CONTAINER ID   IMAGE                                 COMMAND                  CREATED             STATUS             PORTS     NAMES 92c0ea5c4191   rancher/hyperkube:v1.21.13-rancher1   "/opt/rke-tools/entr…"   About an hour ago   Up About an hour             kube-proxy 022cc8af964d   rancher/hyperkube:v1.21.13-rancher1   "/opt/rke-tools/entr…"   About an hour ago   Up About an hour             kubelet 7dbbad92f3cf   rancher/hyperkube:v1.21.13-rancher1   "/opt/rke-tools/entr…"   About an hour ago   Up About an hour             kube-scheduler c1120d751f21   rancher/hyperkube:v1.21.13-rancher1   "/opt/rke-tools/entr…"   About an hour ago   Up About an hour             kube-controller-manager 9a4563b63229   rancher/hyperkube:v1.21.13-rancher1   "/opt/rke-tools/entr…"   About an hour ago   Up About an hour             kube-apiserver
When I look at the logs of the containers, I see a few errors in between, but in the end all containers are started successfully.
I will take a closer look at the individual errors.
In the Rancher logs I see at the beginning that it checks the node list and finds the controller node:
2022/07/15 07:33:01 [DEBUG] Checking node list for node [playground-controller-1], try #1 2022/07/15 07:33:01 [DEBUG] [controlplane] Found node by name playground-controller-1 2022/07/15 07:33:01 [INFO] [controlplane] Now checking status of node playground-controller-1, try #1 2022/07/15 07:33:01 [DEBUG] Checking node list for node [playground-controller-1], try #1 2022/07/15 07:33:01 [INFO] cluster [c-hm4s5] provisioning: [controlplane] Processing controlplane hosts for upgrade 1 at a time 2022/07/15 07:33:01 [INFO] cluster [c-hm4s5] provisioning: Processing controlplane host playground-controller-1 2022/07/15 07:33:01 [DEBUG] [controlplane] Found node by name playground-controller-1
In the further process it updates all containers and at the end it checks the node list again. It looks like it does not find the node anymore:
2022/07/15 07:34:08 [DEBUG] Checking node list for node [playground-controller-1], try #4 2022/07/15 07:34:09 [DEBUG] 2022/07/15 07:34:09 http: TLS handshake error from <IP_ADDRESS>:63801: EOF 2022/07/15 07:34:13 [DEBUG] Checking node list for node [playground-controller-1], try #5 2022/07/15 07:34:18 [ERROR] Failed to upgrade hosts: playground-controller-1 with error [[controlplane] Error getting node playground-controller-1:  "playground-controller-1" not found]

This is still relevant, latest rancher is still broken for me

Still relevant also for us.

This is still relevant, latest rancher is still broken for me

Hi @Aransh,
It looks like we are affected by the following bug. As a result of the change introduced via Rancher RKE in RKE 1.3.5, the hostname-override flag is no longer set for the kubelet in clusters with the AWS Cloud Provider configured.
When the kubelet container is created by RKE v1.3.5 the kubernetes.io/hostname label of the node is set to the EC2 instance's hostname, typically of the form ip-<private ip>.<region>.<internal>. In our case the hostname configured by the AWS cloud provider and the kubernetes/hostname don`t match.
We were able to solve the problem with existing clusters as follows:

Check hostname from all nodes
kubectl describe node <NODE NAME> | grep name
If a node's kubernetes.io/hostname  is the same value as Hostname , it must be changed back to the name of the node. The kubernetes.io/hostname should be the same as the node name shown in the AWS Console → EC2 → Instances.
Edit all nodes where the wrong kubernetes.io/hostname  is set.

> kubectl edit node <NODE NAME>
apiVersion: v1
kind: Node
metadata:
     labels:
        kubernetes.io/hostname: <NODE NAME>

Force a reconcile for the cluster. For example: Edit your cluster and change the values of the snapshot interval and click save.

In some cases it happens that after step 4 the update still does not pass successfully. If this is the case, perform the following steps:

Change the kubernetes.io/hostname  of all nodes to the same name as Hostname.
Force a reconcile of your Cluster.

Hopefully this helps you @Aransh .

Hey @killerquitsche
Thank you very very much for the detailed explanation!
In our case we are deploying rancher using terraform, so your solution is much too manual for us...
But I'm glad to know you were able to pinpoint the issue and pass it along, hopefully it'll be officially resolved soon!

I believe this is similar to the issue I opened here https://github.com/rancher/rke/issues/3091


home-assistant: 2021.2.3 -> 2021.3.0

Motivation for this change
https://www.home-assistant.io/blog/2021/03/03/release-20213/
Things done

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

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

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

          Outdated dependencies
┏━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━┓
┃ Package             ┃ Current ┃ Wanted ┃
┡━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━┩
│ HAP-python          │ 3.1.0   │ 3.3.2  │
│ accuweather         │ 0.0.11  │ 0.1.0  │
│ adext               │ 0.3     │ 0.4.1  │
│ aioshelly           │ 0.5.4   │ 0.6.1  │
│ bellows             │ 0.21.0  │ 0.22.0 │
│ httplib2            │ 0.18.1  │ 0.19.0 │
│ pillow              │ 8.0.1   │ 8.1.1  │
│ plexapi             │ 4.3.1   │ 4.4.0  │
│ py-cpuinfo          │ 5.0.0   │ 7.0.0  │
│ pyinsteon           │ 1.0.8   │ 1.0.9  │
│ pylutron            │ 0.2.6   │ 0.2.7  │
│ pymyq               │ 3.0.3   │ 3.0.4  │
│ python-telegram-bot │ 13.0    │ 13.1   │
│ pytile              │ 5.1.1   │ 5.2.0  │
│ pyvera              │ 0.3.11  │ 0.3.13 │
│ sentry-sdk          │ 0.19.5  │ 0.20.3 │
│ sqlalchemy          │ 1.3.20  │ 1.3.23 │
│ subarulink          │ 0.3.11  │ 0.3.12 │
│ xknx                │ 0.17.0  │ 0.17.1 │
│ zigpy-znp           │ 0.3.0   │ 0.4.0  │
└─────────────────────┴─────────┴────────┘

Nice job on the tests by the way.

      Outdated dependencies

I already have some on my todo list. Some updates will require aiohttp-3.7.4.

      Outdated dependencies

I already have some on my todo list. Some updates will require aiohttp-3.7.4.

Already in staging.
https://github.com/NixOS/nixpkgs/pull/114556

Oh, I was not playing attention to this PR. You already updated the some of dependencies.
I will close #115020.

Already merged and rebased this on top.

Down to
          Outdated dependencies
┏━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━┓
┃ Package             ┃ Current ┃ Wanted ┃
┡━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━┩
│ HAP-python          │ 3.1.0   │ 3.3.2  │
│ httplib2            │ 0.18.1  │ 0.19.0 │
│ pillow              │ 8.0.1   │ 8.1.1  │
│ py-cpuinfo          │ 5.0.0   │ 7.0.0  │
│ python-telegram-bot │ 13.0    │ 13.1   │
│ pytile              │ 5.1.1   │ 5.2.0  │
│ sentry-sdk          │ 0.19.5  │ 0.20.3 │
│ sqlalchemy          │ 1.3.20  │ 1.3.23 │
└─────────────────────┴─────────┴────────┘

Already in staging:

httplib2
pillow
sqlalchemy
py-cpuinfo

We might not want all users of the Home Assistant package to have to test so many components. Maybe we can create a new package called home-assistantWithTests which sets doCheck = true and tests as much as possible -- so that maintainers notice when something breaks.

Or we document (e.g. in the wiki), how users can disable tests.
{ pkgs, ... }:

{
  services.home-assistant = {
    enable = true;
    package = pkgs.home-assistant.overrideAttrs (old: {
      doCheck = false;
      doInstallCheck = false;
    });
  };
}

I would use overridePythonAttrs and only set doCheck = false.

I guess it's enough to document this as an example for the package option and by mentioning in the option's description that otherwise building might take a long time.
We should also the default package one that doesn't run the tests.

I tried the following, but it results in the tests not finding aiohttp_cors.
diff --git a/nixos/modules/services/misc/home-assistant.nix b/nixos/modules/services/misc/home-assistant.nix
index 1f2e13f3732..7d0a031be72 100644
--- a/nixos/modules/services/misc/home-assistant.nix
+++ b/nixos/modules/services/misc/home-assistant.nix
@@ -183,8 +183,14 @@ in {
     };

     package = mkOption {
-      default = pkgs.home-assistant;
-      defaultText = "pkgs.home-assistant";
+      default = pkgs.home-assistant.overridePythonAttrs (oldAttrs: {
+        doCheck = false;
+      });
+      defaultText = literalExample ''
+        pkgs.home-assistant.overridePythonAttrs (oldAttrs: {
+          doCheck = false;
+        }
+      '';
       type = types.package;
       example = literalExample ''
         pkgs.home-assistant.override {

hass # [    5.818279] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds
hass # [    5.819942] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up http
hass # [    5.825566] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Error during setup of component http
hass # [    5.826350] hass[722]: Traceback (most recent call last):
hass # [    5.826836] hass[722]:   File "/nix/store/gvzp61ynjg1c9dr2jba4ja2swlbmm90l-homeassistant-2021.3.0/lib/python3.8/site-packages/homeassistant/setup.py", line 213, in _async_setup_component
hass # [    5.828039] hass[722]:     result = await task
hass # [    5.828470] hass[722]:   File "/nix/store/gvzp61ynjg1c9dr2jba4ja2swlbmm90l-homeassistant-2021.3.0/lib/python3.8/site-packages/homeassistant/components/http/__init__.py", line 210, in async_setup
hass # [    5.830821] hass[722]:     server = HomeAssistantHTTP(
hass # [    5.831271] hass[722]:   File "/nix/store/gvzp61ynjg1c9dr2jba4ja2swlbmm90l-homeassistant-2021.3.0/lib/python3.8/site-packages/homeassistant/components/http/__init__.py", line 316, in __init__
hass # [    5.832405] hass[722]:     setup_cors(app, cors_origins)
hass # [    5.833560] hass[722]:   File "/nix/store/gvzp61ynjg1c9dr2jba4ja2swlbmm90l-homeassistant-2021.3.0/lib/python3.8/site-packages/homeassistant/components/http/cors.py", line 26, in setup_cors
hass # [    5.834864] hass[722]:     import aiohttp_cors
hass # [    5.835553] hass[722]: ModuleNotFoundError: No module named 'aiohttp_cors'
hass # [    5.836764] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of system_log. Setup failed for dependencies: http
hass # [    5.838257] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for system_log: Could not set up all dependencies.
hass # [    5.839609] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 1: {'image', 'lovelace', 'device_automation', 'auth', 'person', 'search', 'system_log', 'onboarding', 'frontend', 'websocket_api', 'api', 'config', 'http'}
hass # [    5.867062] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up lovelace
hass # [    5.874013] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up device_automation
hass # [    5.874873] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.0 seconds
hass # [    5.876540] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of image. Setup failed for dependencies: http
hass # [    5.877624] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for image: Could not set up all dependencies.
hass # [    5.878799] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of auth. Setup failed for dependencies: http
hass # [    5.879682] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for auth: Could not set up all dependencies.
hass # [    5.881515] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of websocket_api. Setup failed for dependencies: http
hass # [    5.883960] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for websocket_api: Could not set up all dependencies.
hass # [    5.885806] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of api. Setup failed for dependencies: http
hass # [    5.886679] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for api: Could not set up all dependencies.
hass # [    5.888477] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of config. Setup failed for dependencies: http
hass # [    5.890927] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for config: Could not set up all dependencies.
hass # [    5.892819] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of person. Setup failed for dependencies: image
hass # [    5.894459] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for person: Could not set up all dependencies.
hass # [    5.895397] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of search. Setup failed for dependencies: websocket_api
hass # [    5.896604] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for search: Could not set up all dependencies.
hass # [    5.897987] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds
hass # [    5.899008] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of onboarding. Setup failed for dependencies: auth, http, person
hass # [    5.900292] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for onboarding: Could not set up all dependencies.
hass # [    5.901780] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of frontend. Setup failed for dependencies: api, auth, config, http, onboarding, search, system_log, websocket_api
hass # [    5.903498] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: Could not set up all dependencies.
hass # [    5.904973] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'binary_sensor', 'mqtt'}
hass # [    5.957993] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
hass # [    5.958908] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds
hass # [    5.960115] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of mqtt. Setup failed for dependencies: http
hass # [    5.961802] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for mqtt: Could not set up all dependencies.
hass # [    5.963800] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of mqtt. Setup failed for dependencies: http
hass # [    5.964682] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform mqtt.binary_sensor: Could not set up all dependencies.
hass # [    5.966991] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 0.20s
hass # [    5.967995] hass[722]: 2021-03-03 23:58:00 WARNING (MainThread) [homeassistant.bootstrap] Detected that frontend did not load. Activating safe mode
hass # [    5.970798] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Starting in safe mode
hass # [    5.971548] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_0) [homeassistant.loader] Loaded homeassistant from homeassistant.components.homeassistant
hass # [    5.973184] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_1) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification
hass # [    5.974796] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up homeassistant
hass # [    5.976160] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant took 0.0 seconds
hass # [    5.978032] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up persistent_notification
hass # [    5.979673] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setup of domain persistent_notification took 0.0 seconds
hass # [    5.982186] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_1) [homeassistant.loader] Loaded http from homeassistant.components.http
hass # [    5.983808] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_0) [homeassistant.loader] Loaded safe_mode from homeassistant.components.safe_mode
hass # [    5.985548] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_3) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
hass # [    5.987764] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_1) [homeassistant.loader] Loaded api from homeassistant.components.api
hass # [    5.988971] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_2) [homeassistant.loader] Loaded auth from homeassistant.components.auth
hass # [    5.990722] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_0) [homeassistant.loader] Loaded config from homeassistant.components.config
hass # [    5.992177] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_3) [homeassistant.loader] Loaded device_automation from homeassistant.components.device_automation
hass # [    5.993794] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_1) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
hass # [    5.995001] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_2) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
hass # [    6.000162] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_0) [homeassistant.loader] Loaded person from homeassistant.components.person
hass # [    6.000976] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_3) [homeassistant.loader] Loaded image from homeassistant.components.image
hass # [    6.001750] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_1) [homeassistant.loader] Loaded search from homeassistant.components.search
hass # [    6.003573] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_2) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
hass # [    6.005409] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_0) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
hass # [    6.007899] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_3) [homeassistant.loader] Loaded cloud from homeassistant.components.cloud
hass # [    6.008720] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_1) [homeassistant.loader] Loaded webhook from homeassistant.components.webhook
hass # [    6.010566] hass[722]: 2021-03-03 23:58:00 INFO (SyncWorker_2) [homeassistant.loader] Loaded alexa from homeassistant.components.alexa
hass # [    6.012345] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Domains to be set up: {'image', 'cloud', 'device_automation', 'auth', 'lovelace', 'person', 'search', 'webhook', 'api', 'config', 'alexa', 'onboarding', 'frontend', 'websocket_api', 'system_log', 'safe_mode', 'persistent_notification', 'http'}
hass # [    6.015901] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Setting up logging: {'system_log'}
hass # [    6.016635] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up http
hass # [    6.018337] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Error during setup of component http
hass # [    6.020910] hass[722]: Traceback (most recent call last):
hass # [    6.021378] hass[722]:   File "/nix/store/gvzp61ynjg1c9dr2jba4ja2swlbmm90l-homeassistant-2021.3.0/lib/python3.8/site-packages/homeassistant/setup.py", line 213, in _async_setup_component
hass # [    6.023949] hass[722]:     result = await task
hass # [    6.024384] hass[722]:   File "/nix/store/gvzp61ynjg1c9dr2jba4ja2swlbmm90l-homeassistant-2021.3.0/lib/python3.8/site-packages/homeassistant/components/http/__init__.py", line 210, in async_setup
hass # [    6.026205] hass[722]:     server = HomeAssistantHTTP(
hass # [    6.026791] hass[722]:   File "/nix/store/gvzp61ynjg1c9dr2jba4ja2swlbmm90l-homeassistant-2021.3.0/lib/python3.8/site-packages/homeassistant/components/http/__init__.py", line 316, in __init__
hass # [    6.028530] hass[722]:     setup_cors(app, cors_origins)
hass # [    6.029462] hass[722]:   File "/nix/store/gvzp61ynjg1c9dr2jba4ja2swlbmm90l-homeassistant-2021.3.0/lib/python3.8/site-packages/homeassistant/components/http/cors.py", line 26, in setup_cors
hass # [    6.031272] hass[722]:     import aiohttp_cors
hass # [    6.031698] hass[722]: ModuleNotFoundError: No module named 'aiohttp_cors'
hass # [    6.032261] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of system_log. Setup failed for dependencies: http
hass # [    6.033141] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for system_log: Could not set up all dependencies.
hass # [    6.033976] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 1: {'cloud', 'image', 'device_automation', 'auth', 'lovelace', 'webhook', 'person', 'search', 'system_log', 'alexa', 'onboarding', 'frontend', 'websocket_api', 'api', 'config', 'http'}
hass # [    6.035361] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up device_automation
hass # [    6.036074] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.0 seconds
hass # [    6.036845] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setting up lovelace
hass # [    6.037484] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds
hass # [    6.038243] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of image. Setup failed for dependencies: http
hass # [    6.039171] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for image: Could not set up all dependencies.
hass # [    6.039995] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of auth. Setup failed for dependencies: http
hass # [    6.040861] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for auth: Could not set up all dependencies.
hass # [    6.041664] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of webhook. Setup failed for dependencies: http
hass # [    6.042631] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for webhook: Could not set up all dependencies.
hass # [    6.043465] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of alexa. Setup failed for dependencies: http
hass # [    6.044353] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for alexa: Could not set up all dependencies.
hass # [    6.045184] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of websocket_api. Setup failed for dependencies: http
hass # [    6.046142] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for websocket_api: Could not set up all dependencies.
hass # [    6.047063] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of api. Setup failed for dependencies: http
hass # [    6.047959] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for api: Could not set up all dependencies.
hass # [    6.048780] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of config. Setup failed for dependencies: http
hass # [    6.049675] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for config: Could not set up all dependencies.
hass # [    6.050509] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of person. Setup failed for dependencies: image
hass # [    6.051456] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for person: Could not set up all dependencies.
hass # [    6.052311] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of cloud. Setup failed for dependencies: http, webhook, alexa
hass # [    6.053262] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for cloud: Could not set up all dependencies.
hass # [    6.054071] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of search. Setup failed for dependencies: websocket_api
hass # [    6.055005] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for search: Could not set up all dependencies.
hass # [    6.055954] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of onboarding. Setup failed for dependencies: auth, http, person
hass # [    6.056956] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for onboarding: Could not set up all dependencies.
hass # [    6.057795] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of frontend. Setup failed for dependencies: api, auth, config, http, onboarding, search, system_log, websocket_api
hass # [    6.058952] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: Could not set up all dependencies.
hass # [    6.059784] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'safe_mode', 'persistent_notification'}
hass # [    6.060690] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of safe_mode. Setup failed for dependencies: frontend, cloud
hass # [    6.061661] hass[722]: 2021-03-03 23:58:00 ERROR (MainThread) [homeassistant.setup] Setup failed for safe_mode: Could not set up all dependencies.
hass # [    6.062478] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 0.06s
hass # [    6.063211] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.core] Starting Home Assistant
hass # [    6.063888] hass[722]: 2021-03-03 23:58:00 INFO (MainThread) [homeassistant.core] Timer:starting

@GrahamcOfBorg eval

I tried the following, but it results in the tests not finding aiohttp_cors.

No idea why it doesn't work.
Another suggestion: add an argument doCheck to the expression, so that we can just use override. You pick what you prefer.

Two open test issues remain:
___________________ test_fetching_without_verify_ssl[pyloop] ___________________
[gw3] linux -- Python 3.8.8 /nix/store/yl69v76azrz4daiqksrhb8nnmdiqdjg9-python3-3.8.8/bin/python3.8

aioclient_mock = <tests.test_util.aiohttp.AiohttpClientMocker object at 0x7fff6f657460>
hass = <homeassistant.core.HomeAssistant object at 0x7fff6f71ae20>
hass_client = <function hass_client.<locals>.auth_client at 0x7fff6f667ca0>

    async def test_fetching_without_verify_ssl(aioclient_mock, hass, hass_client):
        """Test that it fetches the given url when ssl verify is off."""
        aioclient_mock.get("https://example.com", text="hello world")

        await async_setup_component(
            hass,
            "camera",
            {
                "camera": {
                    "name": "config_test",
                    "platform": "generic",
                    "still_image_url": "https://example.com",
                    "username": "user",
                    "password": "pass",
                    "verify_ssl": "false",
                }
            },
        )
        await hass.async_block_till_done()

        client = await hass_client()

        resp = await client.get("/api/camera_proxy/camera.config_test")

>       assert resp.status == 200
E       AssertionError: assert 500 == 200
E        +  where 500 = <ClientResponse(http://<IP_ADDRESS>:43291/api/camera_proxy/camera.config_test) [500 Internal Server Error]>\n<CIMultiDictP...harset=utf-8', 'Content-Length': '26', 'Date': 'Thu, 04 Mar 2021 08:06:56 GMT', 'Server': 'Python/3.8 aiohttp/3.7.3')>\n.status

tests/components/generic/test_camera.py:76: AssertionError

__________________ test_fetching_url_with_verify_ssl[pyloop] ___________________
[gw3] linux -- Python 3.8.8 /nix/store/yl69v76azrz4daiqksrhb8nnmdiqdjg9-python3-3.8.8/bin/python3.8

aioclient_mock = <tests.test_util.aiohttp.AiohttpClientMocker object at 0x7fff6f62dc10>
hass = <homeassistant.core.HomeAssistant object at 0x7fff6f6c2c40>
hass_client = <function hass_client.<locals>.auth_client at 0x7fff6f7dc040>

    async def test_fetching_url_with_verify_ssl(aioclient_mock, hass, hass_client):
        """Test that it fetches the given url when ssl verify is explicitly on."""
        aioclient_mock.get("https://example.com", text="hello world")

        await async_setup_component(
            hass,
            "camera",
            {
                "camera": {
                    "name": "config_test",
                    "platform": "generic",
                    "still_image_url": "https://example.com",
                    "username": "user",
                    "password": "pass",
                    "verify_ssl": "true",
                }
            },
        )
        await hass.async_block_till_done()

        client = await hass_client()

        resp = await client.get("/api/camera_proxy/camera.config_test")

>       assert resp.status == 200
E       AssertionError: assert 500 == 200
E        +  where 500 = <ClientResponse(http://<IP_ADDRESS>:38267/api/camera_proxy/camera.config_test) [500 Internal Server Error]>\n<CIMultiDictP...harset=utf-8', 'Content-Length': '26', 'Date': 'Thu, 04 Mar 2021 08:06:56 GMT', 'Server': 'Python/3.8 aiohttp/3.7.3')>\n.status

tests/components/generic/test_camera.py:103: AssertionError

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

24 packages built:

home-assistant
python37Packages.accuweather
python37Packages.adext
python37Packages.alarmdecoder
python37Packages.bellows
python37Packages.plexapi
python37Packages.pyvera
python37Packages.zha-quirks
python37Packages.zigpy-znp
python38Packages.accuweather
python38Packages.adext
python38Packages.alarmdecoder
python38Packages.bellows
python38Packages.plexapi
python38Packages.pyvera
python38Packages.zha-quirks
python38Packages.zigpy-znp
python39Packages.accuweather
python39Packages.adext
python39Packages.alarmdecoder
python39Packages.bellows
python39Packages.pyvera
python39Packages.zha-quirks
python39Packages.zigpy-znp

building of '/nix/store/a8hlrwq6vy08asviqib3wh78lzpmiryn-homeassistant-2021.3.0.drv!out' from .drv file timed out after 3600 seconds

The aarch64 ofborg builder seems to timeout near the end of the tests. I have a raspberrypi4 here, but could someone else give the nixos test on aarch64 a try?

Just as reference. No action needed and not need to be part of this PR. I simply want to avoid duplicate work like it happen yesterday.
New dependencies according to component-packages.nix:

aiolyric: #115125
pyplaato: #115124
pyrituals: #115119
mullvad-api: #115113

Package updates (https://github.com/NixOS/nixpkgs/pull/115016#issuecomment-790086395)

HAP-python: #115087

building of '/nix/store/a8hlrwq6vy08asviqib3wh78lzpmiryn-homeassistant-2021.3.0.drv!out' from .drv file timed out after 3600 seconds

The aarch64 ofborg builder seems to timeout near the end of the tests. I have a raspberrypi4 here, but could someone else give the nixos test on aarch64 a try, too?

There is a problem I can reproduce on aarch64, where a test times out, maybe multiple.

tests/components/zha/test_discover.py::test_group_probe_cleanup_called[pyloop]

There is a problem I can reproduce on aarch64, where a test times out, maybe multiple.

I'm stuck on a Raspberry Pi at 99 %. I guess that the timeout is coming as well.
builder for '/nix/store/5952fjjxy1hlgij5rmdrcdkkx4biwg17-python3.7-zigpy-znp-0.4.0.drv' failed with exit code 1; last 10 log lines:

  final      = True
  input      = b''
  self       = <encodings.utf_8.IncrementalDecoder object at 0x7ff5f367d0>

  /nix/store/dxmx8nx86d45g3wnp6xvrs8l8wsclc1r-python3-3.7.10/lib/python3.7/codecs.py:319: Failed
  =========================== short test summary info ============================
  FAILED tests/application/test_requests.py::test_request_concurrency[FormedLaunchpadCC26X2R1]
  ERROR tests/tools/test_nvram.py::test_nvram_write[ResetZStack3CC2531] - Faile...
  ============== 1 failed, 334 passed, 1 error in 260.87s (0:04:20) ==============
[...]
[1/0/2 built (1 failed), 0.0 MiB DL] building homeassistant-2021.3.0 (pytestCheckPhase): ........................................................................ [ 99%]

My current progress is this:
diff --git a/pkgs/servers/home-assistant/default.nix b/pkgs/servers/home-assistant/default.nix
index 1e5ea0f7532..b6260e238e6 100644
--- a/pkgs/servers/home-assistant/default.nix
+++ b/pkgs/servers/home-assistant/default.nix
@@ -132,6 +132,7 @@ in with py.pkgs; buildPythonApplication rec {
     asynctest
     pytest-aiohttp
     pytest-rerunfailures
+    pytest-timeout
     pytest-xdist
     pytestCheckHook
     requests-mock
@@ -287,6 +288,8 @@ in with py.pkgs; buildPythonApplication rec {
   ];

   pytestFlagsArray = [
+    "-vvv"
+    "--timeout 60"
     # limit amout of runners to reduce race conditions
     "-n auto"
     # retry racy tests that end in "RuntimeError: Event loop is closed"
@@ -304,6 +307,11 @@ in with py.pkgs; buildPythonApplication rec {
     "tests/components"
     # pyotp since v2.4.0 complains about the short mock keys, hass pins v2.3.0
     "tests/auth/mfa_modules/test_notify.py"
+  ] ++ lib.optionals (stdenv.isAarch64) [
+    # tests get stuck on aarch64
+    "tests/components/zha/test_discover.py"
+    "tests/components/zwave/test_init.py"
+    "tests/components/zwave/test_climate.py"
   ];

   disabledTests = [

Sadly the timeout never triggers, it just gets stuck at 99%.

builder for '/nix/store/5952fjjxy1hlgij5rmdrcdkkx4biwg17-python3.7-zigpy-znp-0.4.0.drv' failed with exit code 1; last 10 log lines:

  final      = True
  input      = b''
  self       = <encodings.utf_8.IncrementalDecoder object at 0x7ff5f367d0>

  /nix/store/dxmx8nx86d45g3wnp6xvrs8l8wsclc1r-python3-3.7.10/lib/python3.7/codecs.py:319: Failed
  =========================== short test summary info ============================
  FAILED tests/application/test_requests.py::test_request_concurrency[FormedLaunchpadCC26X2R1]
  ERROR tests/tools/test_nvram.py::test_nvram_write[ResetZStack3CC2531] - Faile...
  ============== 1 failed, 334 passed, 1 error in 260.87s (0:04:20) ==============
[...]
[1/0/2 built (1 failed), 0.0 MiB DL] building homeassistant-2021.3.0 (pytestCheckPhase): ........................................................................ [ 99%]

Can't reproduce on aarch64, nor on x86_64.

Can't reproduce on aarch64, nor on x86_64.

First time I saw it was on the Raspberry today. x86_64 is fine for me.

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

24 packages built:

home-assistant
python37Packages.accuweather
python37Packages.adext
python37Packages.alarmdecoder
python37Packages.bellows
python37Packages.plexapi
python37Packages.pyvera
python37Packages.zha-quirks
python37Packages.zigpy-znp
python38Packages.accuweather
python38Packages.adext
python38Packages.alarmdecoder
python38Packages.bellows
python38Packages.plexapi
python38Packages.pyvera
python38Packages.zha-quirks
python38Packages.zigpy-znp
python39Packages.accuweather
python39Packages.adext
python39Packages.alarmdecoder
python39Packages.bellows
python39Packages.pyvera
python39Packages.zha-quirks
python39Packages.zigpy-znp

Disabled tests in the modules default package.
Meanwhile:

https://github.com/home-assistant/core/releases/tag/2021.3.1
https://github.com/home-assistant/core/releases/tag/2021.3.2

Still debugging aarch64 test issues.

========== 6904 passed, 5 skipped, 3251 warnings in 340.45s (0:05:40) ==========

The esphome component seriously needs to get their warnings in order. Several instances like these:
../../nix/store/nzcla6pyq2ngiacm6vzaj6m7siblhvg4-python3.8-aioesphomeapi-2.6.5/lib/python3.8/site-packages/aioesphomeapi/api_options_pb2.py:19: 32 warnings
  /nix/store/nzcla6pyq2ngiacm6vzaj6m7siblhvg4-python3.8-aioesphomeapi-2.6.5/lib/python3.8/site-packages/aioesphomeapi/api_options_pb2.py:19: DeprecationWarning: Call to deprecated create function FileDescriptor(). Note: Create unlinked descriptors is going to go away. Please use get/find descriptors from generated code or query the descriptor_pool.
    DESCRIPTOR = _descriptor.FileDescriptor(

I've identified the two tests that get stuck on aarch64, I guess we should report them upstream and ask them to test aarch64 as well.

https://github.com/home-assistant/core/issues/47527


KAFKA-3459: Returning zero task configurations from a connector does not properly clean up existing tasks

@hachikuji @ewencp Can you take a look when you have time?

@Ishiihara How much trouble would it be to add a unit test?

@hachikuji Unit test added. Please take another look.

@hachikuji Updated to public void putTaskConfigs(String connector, List<Map<String, String>> configs).

@Ishiihara Left a couple minor comments, but mostly LGTM. Thanks for trying to push through the refactor I suggested. It looks like it worked out well for DistributedHerder, but maybe a little awkward for StandaloneHerder. Considering the complexity of the former, that might be a good trade.

@Ishiihara Same as @hachikuji, few minor comments but mostly LGTM.

@ewencp Addressed review comments. PTAL.

LGTM, thanks @Ishiihara!


Can I disable the day view and just use the month view?

I had not given any preferences to move to a particular view, but when a specific date is clicked it opens the day view of that field.

You can disable that with this option. Something like on-drill-down-click="false" should do the trick.

I tried to use on-drill-down-click="false" on the calendar directive but it didn't disable the day view. Is there anything I might be missing?

That option has been renamed to on-view-change-click, see the demo for an example: http://mattlewis92.github.io/angular-bootstrap-calendar/#?example=disabling-views

Wow mattlewis92 thanks .. that was Super fast and it worked too.

No problem, happy to help :smile:

While we are at it, can I ask one more question. Is there any way to permanently disable the Slidebox. I have tried using vm.isCellOpen = false but it is not working as I thought it would. I must say your calendar is quite good. The only reason I want to disable the slider is because if I have many events the alot of screenspace is taken by the slidebox.

Not currently, I've created new issue for it: https://github.com/mattlewis92/angular-bootstrap-calendar/issues/292


Error

return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x81 in position 4296: character maps to
How to fix this error?

file_handle = open(names + ".txt",encoding='utf-8')

f = open(names + "out.txt", 'w',encoding='utf-8')


Attribute missing from /heroStats

'pro_bans' attribute missing in Crystal Maiden's response object as of today.

That probably means it's 0

Shouldn't the response contain pro_ban with the value as 0? Or should I be checking this for all attributes returned?

I made a fix to the SQL to always return a value (even if 0) for the pro_picks/pro_bans field.
I haven't done the same for the public pick stats, but hopefully those will never be 0.


Use test unit gem explicitly

Because Ruby 2.2 does not provide minitest with test-unit compatibility layer.

Thanks!

Wow, thank you for so fast merging!


Replace deleteItem with removeCartItem

Fixes #50

updated tests to use removeCartItem
removed old deleteItem code

It should be ready to go, let me know if there's something I missed (tests are passing 👍)


[GOBBLIN-1868] Introduce FlowExecutionUtil & SharedFlowMetricsContainer for sharing between Orchestrator & DagManager

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[X] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1868

Description

[X] Here are some details about my PR, including screenshots (if applicable):
Create a Helper class FlowCompilationValidationHelper to contain functionality re-used between the DagManager and Orchestrator when launching executions of a flow spec. In the common case, the Orchestrator receives a flow to orchestrate, performs necessary validations, and forwards the execution responsibility to the DagManager. The DagManager's responsibility is to carry out any flow action requests. However, with launch executions now being stored in the DagActionStateStore, on restart or leadership change the DagManager has to perform validations before executing any launch actions the previous leader was unable to complete.
We tried to have the DagManager refer to the Orchestrator to avoid duplicating code in a previous commit, but introduced a circular dependency between the DagManager and Orchestrator and was unable to work in runtime. This class is utilized to store the common functionality. It is stateful, requiring all stateful pieces to be passed as input from the caller upon instantiating the helper.
Note: We expect further refactoring to be done to the DagManager in later stage of multi-active development so we do not attempt major reorganization as abstractions may change.

Also creates a class, SharedFlowMetricsSingleton to store shared metrics between the  DagManager and Orchestrator.
Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Deploys locally and service starts

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3731 (41de9f6) into master (2087426) will decrease coverage by 1.76%.
Report is 1 commits behind head on master.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3731      +/-   ##
============================================
- Coverage     47.08%   45.33%   -1.76%
+ Complexity    10859     2137    -8722
============================================
  Files          2144      413    -1731
  Lines         84748    17956   -66792
  Branches       9410     2184    -7226
============================================
- Hits          39907     8140   -31767
+ Misses        41221     8949   -32272
+ Partials       3620      867    -2753

see 1735 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


updated word in index

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey @Kartik2220
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


plotFormula can be replaced by plotFunction

I recently started using mathjs for plotFormula (#27)
Using a minimal custom package of math.js still five-folds the size of the final package. I would like to keep it small. It can be implemented by the user by using plotFunction (#26) this way:
<script src="https://cdnjs.cloudflare.com/ajax/libs/mathjs/3.18.0/math.min.js"></script>

var compiled = math.compile("sin(x1*5) + sin(x3*5)")
plot.plotFunction(function(x1, x3) {
    return compiled.eval({"x1": x1, "x3": x3})
})

So I'm doing exactly that in plotFormula from now on. If mathjs was never linked it will throw an error to the console, explaining what to do and what the alternative (plotFunction with javascript syntax) is.


intel gpu opecl beignet1.1.1   run error

compile sucessfully
run error
Initializing... DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 ASSERTION FAILED: !(ctx->getErrCode() == OUT_OF_RANGE_IF_ENDIF && ctx->getIFENDIFFix())   at file /build/beignet-5qGeBM/beignet-1.1.1/backend/src/backend/gen_program.cpp, function virtual gbe::Kernel* gbe::GenProgram::compileKernel(const gbe::ir::Unit&, const string&, bool), line 197 追踪与中断点陷阱 (核心已转储)

intensity must be between 8 and 32. 1 is invalid
Note that the default intensity is 16
westeast@hacker-diy:~/win7e/go/opencl$ ./opencl -d 0 -p 1 -I 8
Intensity set to 8
Initializing...
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
ASSERTION FAILED: !(ctx->getErrCode() == OUT_OF_RANGE_IF_ENDIF && ctx->getIFENDIFFix())
  at file /build/beignet-5qGeBM/beignet-1.1.1/backend/src/backend/gen_program.cpp, function virtual gbe::Kernel* gbe::GenProgram::compileKernel(const gbe::ir::Unit&, const string&, bool), line 197

Can anyone give me some advice?  I do not know how to sovle this problem.


[Bug]: Dynamo DB: The secret key is getting displayed on the review page.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Dynamo DB: The secret key is getting displayed on the review page after the user configures staging

Steps To Reproduce
Steps:

Create a new dynamo datasource
configure staging also

Observe - On the review page, the user can see the "AWS Secret Access Key"
Public Sample App
No response
Issue video log
No response
Version
1.9.6

@AnandShahs123 can you check this behaviour against release and let me know what should be the expected output here?

secret key should not be displayed @ayushpahwa

Will be fixed along with #20522


Mount failing with segfault after updating Ubuntu 22.04

After updating Ubuntu 22.04 my existing use of google-drive-ocamlfuse stopped working.
Running
google-drive-ocamlfuse -debug  -label<EMAIL_ADDRESS><EMAIL_ADDRESS>results in exit code 0 (zero) and no output what so ever. No mount. It results in the following entries in journalctl:
apr 15 19:49:47 MyHost kernel: google-drive-oc[137048]: segfault at 2f ip 00007502abf9d7fd sp 00007ffe9d1e0e48 error 4 in libc.so.6[7502abe28000+195000] likely on CPU 0 (core 0, socket 0)
apr 15 19:49:47 MyHost kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 <c5> fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

Version
apt-cache showpkg google-drive-ocamlfuse
Package: google-drive-ocamlfuse
Versions:
0.7.32-0ubuntu1~bpo22.04.1 (/var/lib/apt/lists/ppa.launchpadcontent.net_alessandro-strada_ppa_ubuntu_dists_jammy_main_binary-amd64_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/ppa.launchpadcontent.net_alessandro-strada_ppa_ubuntu_dists_jammy_main_binary-amd64_Packages
                  MD5: 65ec543c92cc50e7d73349b8f27366d8
 Description Language: en
                 File: /var/lib/apt/lists/ppa.launchpadcontent.net_alessandro-strada_ppa_ubuntu_dists_jammy_main_i18n_Translation-en
                  MD5: 65ec543c92cc50e7d73349b8f27366d8

Reverse Depends:
Dependencies:
0.7.32-0ubuntu1~bpo22.04.1 - libc6 (2 2.35) libcurl3-gnutls (2 7.66.0) libfuse2 (2 2.8) libgmp10 (2 2:6.2.1+dfsg) libsqlite3-0 (2 3.25.0) zlib1g (2 1:1.1.4) fuse (0 (null))
Provides:
0.7.32-0ubuntu1~bpo22.04.1 -
Reverse Provides:

In /var/log/apt/history.log I found
Start-Date: 2024-04-15  09:30:49
Commandline: aptdaemon role='role-commit-packages' sender=':1.80410'
Install: linux-tuxedo-6.5-headers-6.5.0-10031:amd64 (6.5.0-10031.35, automatic), linux-image-6.5.0-10031-tuxedo:amd64 (6.5.0-10031.35, automatic), linux-modules-6.5.0-10031-tuxedo:amd64 (6.5.0-10031.35, automatic), linux-modules-extra-6.5.0-10031-tuxedo:amd64 (6.5.0-10031.35, automatic), linux-headers-6.5.0-10031-tuxedo:amd64 (6.5.0-10031.35, automatic)
Upgrade: tuxedo-drivers:amd64 (4.3.2, 4.4.0), google-drive-ocamlfuse:amd64 (0.7.30-1ubuntu1~bpo22.04.1, 0.7.32-0ubuntu1~bpo22.04.1), linux-tuxedo-22.04:amd64 (<IP_ADDRESS>27.96, <IP_ADDRESS>31.101), linux-headers-tuxedo-22.04:amd64 (<IP_ADDRESS>27.96, <IP_ADDRESS>31.101), chromium:amd64 (1:123.0.6312.105-1tux1, 1:123.0.6312.122-1tux1), linux-image-tuxedo-22.04:amd64 (<IP_ADDRESS>27.96, <IP_ADDRESS>31.101), tuxedo-tomte:amd64 (2.28.0, 2.29.0), linux-tuxedo-22.04-edge:amd64 (<IP_ADDRESS>27.96, <IP_ADDRESS>31.101)
End-Date: 2024-04-15  09:32:31

Would be interesting to see if I could downgrade to 0.7.30-1ubuntu1~bpo22.04.1

Sure, you can find old versions here: https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu/pool/main/g/google-drive-ocamlfuse/
But if you know how to use gdb, and you could send me the stack trace of the segmentation fault, I think I can fix the issue (I thought it was the @ character, but I can't reproduce the error on my machine). Thanks!

I am having a similar result with no output from the command, no mount, and exit code 0.  I too have a script to automatically parse the .gdfuse folder with formatted tags, create directories and mount them.  My drives and shared folders on one account are mounting fine but another account is failing silently.

Sure, you can find old versions here: https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu/pool/main/g/google-drive-ocamlfuse/
But if you know how to use gdb, and you could send me the stack trace of the segmentation fault, I think I can fix the issue (I thought it was the @ character, but I can't reproduce the error on my machine). Thanks!

Is there a easy way to invoke gdb and output a usable file over command line? I am actually having the exact issue @Roland-Brown-Trimble mentions, however it must have a record somewhere.

I can invoke gdb if I get some more guidance. I haven't used it for decades.

I also seem be experience the same or similar issues. In my journalctl output the following is present:
Apr 16 07:56:08 X systemd[1]: google-drive-ocamlfuse-X.service: Main process exited, code=dumped, status=11/SEGV
Apr 16 07:56:08 X systemd[1]: google-drive-ocamlfuse-X.service: Failed with result 'core-dump'.

It only failed to mount since I updated on Sunday.
$ sudo apt show google-drive-ocamlfuse
Package: google-drive-ocamlfuse
Version: 0.7.32-0ubuntu1~bpo22.04.1
Priority: optional
Section: ocaml
Maintainer: Alessandro Strada<EMAIL_ADDRESS>Installed-Size: 8,322 kB
Depends: libc6 (>= 2.35), libcurl3-gnutls (>= 7.66.0), libfuse2 (>= 2.8), libgmp10 (>= 2:6.2.1+dfsg), libsqlite3-0 (>= 3.25.0), zlib1g (>= 1:1.1.4)

I have two mountpoints configured.
One is for my standard Google Drive storage. I seemed to get this one running successfully by adding the -debug flag (tried twice and worked twice, restart in between). What really confused me is that the command still exited immediately (even though -debug implies -f), but the mountpoint is perfectly accessible.
The other one is a shared team directory. I successfully mounted this one using the -debug -s -f flags and the command runs in the foreground as expected.

I think the problem is caused by this issue: astrada/ocamlfuse#26. I thought I included the fix in the Ubuntu package but I probably missed it. I will release a new package when I get home.

I could mount via '-d' (debug) flag here too, however I see no core-dumps in the journal at all (tried with grep). Additionally, it doesn't "detach" here, e.g. I don't see a command prompt after '-d' argument. It just works.
As there aren't hundreds of bug reports as a result of new release, could this be a CPU/package versions specific thing?

As there aren't hundreds of bug reports as a result of new release, could this be a CPU/package versions specific thing?

I don't know, but I have Ubuntu 22.04 on Intel as the majority of users experiencing this issue, it seems. And I am unable to reproduce it.  As I am not a C programmer, it's super easy for me to introduce a bug like that. Instead of -d you can use as a workaround the -f option that keeps also the process in foreground and doesn't dump tons of text on the console while running.

I can invoke gdb if I get some more guidance. I haven't used it for decades.

@cbarreholm, to enable saving core dumps on disk, run in a bash shell:
ulimit -c unlimited

Then, run google-drive-ocamlfuse, and you should see a core dump in /var/lib/apport/coredump/ (on Ubuntu). Then you can run gdb:
gdb $(which google-drive-ocamlfuse) [path of the core dump file]

From the gdb console, run:
bt

to get the stack trace. Thanks!

I think the problem is caused by this issue: astrada/ocamlfuse#26. I thought I included the fix in the Ubuntu package but I probably missed it. I will release a new package when I get home.

I updated this morning and it seems to have fixed the issue for me. Thank you very much

Updated to 0.7.32-0ubuntu3
Problem solved. :heavy_check_mark:
(Side note. I followed the instructions to create core dump before upgrading, but nothing ended up in /var/lib/apport/coredump/)

@cbarreholm thanks for your feedback!

As there aren't hundreds of bug reports as a result of new release, could this be a CPU/package versions specific thing?

I don't know, but I have Ubuntu 22.04 on Intel as the majority of users experiencing this issue, it seems. And I am unable to reproduce it.  As I am not a C programmer, it's super easy for me to introduce a bug like that. Instead of -d you can use as a workaround the -f option that keeps also the process in foreground and doesn't dump tons of text on the console while running.

Interestingly, I created the same issue via 'opam install google-drive-ocamlfuse' and running it. It works perfectly with -d or -f , disappears without a trace otherwise. This is kde neon (22.04 Ubuntu based)
I used the package on this page https://ocaml.org/p/google-drive-ocamlfuse


add: jeeehaan

Description

Related Issues

Changes Proposed

Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@jeeehaan Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!


Any help on getting this to work in the UK?

How impactful is the issue
 Critical
Describe the bug

My dms aren't being unsent; code isn't working for me
How to reproduce the bug

Using the code as intended
Logs

(Paste the file here.)
Unable to.
Screenshots

Desktop (please complete the following information):

Windows, Chrome, Latest stable release, UK/EU version
Additional context

(Write your answer here.)

Apologies for not being able to get the logs file, I am not too proficient in technology

Hello,
I'll need the exact steps you took that resulted in the bug, as well as a description less vague than "it's not working".
For the logs file, when you open an issue there is a step-by-step guide that explains how you can retrieve those, if you can point to me what it is that you don't understand maybe I can guide you in getting the logs.


Code could be simplified

This
String char = new String.fromCharCode(text.codeUnitAt(i));
      String nextChar = (i + 1 == text.length
          ? null
          : new String.fromCharCode(text.codeUnitAt(i + 1)));

could be replaced with
final char = text[i];
final nextChar = i + 1 == text.length ? null : text[i + 1];

I agree, but this isn't really an issue.


Establish a proper design system

Should have a direct mapping between theme colors for light and dark modes for convenience

too annoying


FW/kvm: always print the vCPU register state on failure

This is to help debugging why the test failed, most often when writing new tests and trying to figure out why they're not behaving as expected. That includes KVM_EXIT_FAIL_ENTRY cases when we set up the state incorrectly.
Now, for every failure, we'll get something like:
    - level: info
      text: |1
       I> Register dump:
       rax = 0x0000000000000001 rbx = 0x0000000000000000 rcx = 0x0000000000000000 rdx = 0x0000000000000600
       rsi = 0x0000000000000000 rdi = 0x0000000000000000 rsp = 0x00000000005ff000 rbp = 0x00000000005ff000
       r8  = 0x0000000000000000 r9  = 0x0000000000000000 rcx = 0x0000000000000000 r11 = 0x0000000000000000
       r12 = 0x0000000000000000 r13 = 0x0000000000000000 r14 = 0x0000000000000000 r15 = 0x0000000000000000
       rip = 0x0000000000300006 rflags = 0x0000000000000002 []
       cs  = 0x0008 base = 0x000000000000 limit = 0x000fffff s=1 type=R-Xa dpl=0 db=0 g=1 l=1 present
       ds  = 0x0010 base = 0x000000000000 limit = 0x000fffff s=1 type=RW-a dpl=0 db=1 g=1 l=0 present
       es  = 0x0010 base = 0x000000000000 limit = 0x000fffff s=1 type=RW-a dpl=0 db=1 g=1 l=0 present
       fs  = 0x0000 base = 0x000000000000 limit = 0x0000ffff s=1 type=RW-a dpl=0 db=0 g=0 l=0 present
       gs  = 0x0000 base = 0x000000000000 limit = 0x0000ffff s=1 type=RW-a dpl=0 db=0 g=0 l=0 present
       ss  = 0x0010 base = 0x000000000000 limit = 0x000fffff s=1 type=RW-a dpl=0 db=1 g=1 l=0 present
       cr0 = 0xe0000011 cr2 = 0 cr3 = 0x0000000000201000 cr4 = 0x00000020 efer = 0x500 xcr0 = 0x000001
       gdt: base = 0x0000000000200000 limit = 0x0017
       ldt: base = 0x0000000000000000 limit = 0xffff

Sorry, minor update: adding a space for every line.


Add tests

I can do this

go right ahead :)

You must fork the repo, push the change to your own repo, and then submit a pull request.

Closing this for being too generic.


Unable to resolve module @react-navigation/material-top-tabs

bundling failed: Error: Unable to resolve module `@react-navigation/material-top-tabs` from `node_modules/react-native-collapsible-tab-view/lib/module/MaterialTopTabsCollapsibleTabView.js`: @react-navigation/material-top-tabs could not be found within the project.

I used it without the integration with react-navigation, but the above error occurs.

bundling failed seems like a weird message, and looks related to building the project, not using it.
Can you explain step by step what you did to receive this error?

@andreialecu it seems to happen because we are exporting createMaterialCollapsibleTopTabNavigator  and MaterialTopTabsCollapsibleTabView  even if react-navigation isen't installed. So, react-navigation is not added as a dependency, it will break the build.
It's easy to reproduce:

Create a new expo project
Add react-native-collapsible-tab-view and the peers (without react-navigation)
Copy the quick start code
expo start should error
add the @react-navigation/... peers
expo start works

Note that the quick start code does not use the navigator. So it should work.
I think the solution is to conditionally export createMaterialCollapsibleTopTabNavigator  and MaterialTopTabsCollapsibleTabView , but I was not successful.
The other option is to remove the peerDependenciesMeta , @andreialecu what you think?

I see. I don't use expo so I wasn't familiar with that error signature.
Normally if the material tab files are not imported there shouldn't be any error but I suspect that typescript is interfering. I will take a look in a couple of hours, currently away for a bit.

Thanks @andreialecu! But don't worry, it's not a priority

I'm still on mobile but I figured out what the problem is. It's related to these exports:
https://github.com/PedroBern/react-native-collapsible-tab-view/blob/e58a5f5a18eed700fb741c931c6493ba8e852907/src/index.tsx#L9
They should be in a separate file instead of the index. Perhaps one named navigation.tsx so that end users would imported them from "react-native-collapsible-tab-view/navigation" instead.

Upon further investigation, the problem with my proposed approach above is that because of the path structure of the published package, the imports would end up looking like:
import { createMaterialCollapsibleTopTabNavigator } from "react-native-collapsible-tab-view/lib/module/navigation"

Which isn't a great experience...
There's a proposal here that would allow rewriting the imports so that react-native-collapsible-tab-view/navigation would work, but I'm not sure if react native and the metro bundler can use it:
https://nodejs.org/api/packages.html#packages_package_entry_points
Alternatives:

Could make the peer non optional, but users still need to ensure it's installed in their projects. Peers usually just show a warning while installing, which most users ignore. And having it non-optional isn't a great approach for people that don't need react-navigation integration.

Could publish a separate npm package just with the react-navigation integration. Might be do-able, but would need restructuring this project to be a monorepo (via yarn workspaces, for example).

@andreialecu thanks for the help. Did a quick modification, adding a navigation.tsx to export the navigator, published the @beta version to test, and didn't work. Need to import from .../lib/module/navigation, and something was broken, because the navigator stopped working in my project.
Seems like the best alternative is the 2 you have pointed, I will look into it in the future, but as right now I don't have much time, I will follow the alternative 1.

As it isn't an optional dependency anymore (in v1.4.2), I'm closing. When there is some extra time, I will look into refactoring into a monorepo.

Good job guys!!!


squid: 5.4.1 -> 5.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/squid/versions.
meta.description for squid is: "A caching proxy for the Web supporting HTTP, HTTPS, FTP, and more"
meta.homepage for squid is: "http://www.squid-cache.org"
meta.changelog for squid is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.6 with grep in /nix/store/8z72z50zg3xglz9kcrxqd6173gwjpfqj-squid-5.6
found 5.6 in filename of file in /nix/store/8z72z50zg3xglz9kcrxqd6173gwjpfqj-squid-5.6

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
squid

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8z72z50zg3xglz9kcrxqd6173gwjpfqj-squid-5.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A squid https://github.com/r-ryantm/nixpkgs/archive/32cd729fbade41bd1610e448a9af5a8c162b1a81.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8z72z50zg3xglz9kcrxqd6173gwjpfqj-squid-5.6
ls -la /nix/store/8z72z50zg3xglz9kcrxqd6173gwjpfqj-squid-5.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

squid (squid4)

Maintainer pings
cc @fpletz @7c6f434c for testing.

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

1 package built:

squid


issue 323 comcol page logo bottom padding

This PR Closes #323

Bootstrap 4 has css classes for margin and padding. Please use those instead of hardcoding a number. The reason for that is: if you theme it later, everything will scale nicely.

This is now in place.


ttnn.prod and ttnn.sum do not have keepdim parameter

ttnn.prod and ttnn.sum do not have keepdim parameter as analogues torch function do:
https://docs.tenstorrent.com/tt-metal/latest/ttnn/ttnn/api/ttnn.sum.html
https://pytorch.org/docs/stable/generated/torch.sum.html

sum should already work.
Remaining work should be to work on prod.

sum should already work.
Remaining work should be to work on prod.

@bbradelTT  : do we also need to support keepdim for prod_nc & prod_all?

@asandhupatlaTT you would need to plumb through keepdim from Python to C++ invoke.
Looking at ttnn/cpp/ttnn/operations/reduction/prod/prod_pybind.hpp, ttnn/cpp/ttnn/operations/reduction/prod/prod.cpp, and how generic reductions deal with the keepdim parameter, you shouldn't need to.


add qtbase's bin path to phatomjs2

Motivation for this change
Phantomjs2 fails to load within selenium, as reported in https://github.com/NixOS/nixpkgs/issues/29144
This aplies the fix proposed by @7c6f434c in that ticket.
Things done

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

[ ] NixOS
[ ] macOS
[x] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

(push -f to fix commit message)


Create a proper API

Okay, here's some API designs.

Endpoint
Description

/
Web interface

/api
API

Right now, we only deal with repositories, but we could eventually deal with other things later on. That would break the database, but that's another subject entirely. Matters revolving around repositories should be in /api/repos.

Endpoint
Method
Description

/api/repos
GET
List of all repositories

/api/repos
POST
Create a repository

/api/repos/{url}
GET
Get this repository

/api/repos/{url}
DELETE
Delete this repository

This architecture was inspired from azure/architecture/best-practices/api-design.
Note that there's no way to edit a repository. Changing a repo's URL is going to break a lot of things, including our IPNS record, and dealing with it would be more problematic than what's worth. There's also no mass DELETE on /api/repos for obvious reasons, but that could be implemented fairly easily if necessary.
The API is also unsecured at the moment. Ideally, a front-end would be separate from this project and offer some real user authentication and a payment gateway.

Since this is a rather heavy change, I created the branch feature/api to work on it. The develop branch will remain stable until the API is completed and the interface is updated.

Reworked the API in https://github.com/Permaweb/Host/commit/0d36814eb1b0e06aa6245c0cc1d8965aa4ed5743.

A problem with using the URL as a primary key is that Git URLs contain slashes, and they're navigated by the router, invalidating the match. https://stackoverflow.com/q/57257035/5083247
I'm currently getting around this by using base64, but I feel like this makes the API non-standard and I don't really like that. On the other hand, I have to use the Git URL because that's what users will remember, not the IPNS / IPFS / Key hashes or the internal UUID. Passing it inside the body or as an argument could work, but GET requests aren't supposed to contain a body, and using an argument doesn't make sense, that would also make the API non-standard.

Problem was solved here.

Merged in develop.


Verifying Vector::remove

For reasons unknown Vector::remove() does not verify and is currently marked as unsafe.  I've boiled it down to this:
type uint is (int x) where x >= 0
type Vector is { int[] items, uint length } where length <= |items|

// Check if two array subranges are equal
property equals(int[] l, int l_start, int[] r, int r_start, int length) -> bool:
    // Arrays must be big enough to hold subrange
    |l| >= (l_start + length) && |r| >= (r_start + length) &&
    // All items in subrange match
    all { k in 0..length | l[l_start+k] == r[r_start+k] }

native function remove(int[] src, uint ith) -> (int[] result)
// Element to be removed must be within bounds
requires ith < |src|
// Resulting array has one less element
ensures |result| == |src| - 1
// All elements that were above that removed are preserved
ensures equals(src,ith+1,result,ith,|result|-ith)

function remove(Vector vec, uint ith) -> (Vector result)
// Index must be within array bounds
requires ith >= 0 && ith < vec.length:
    // Remove item from underlying array
    int[] items = remove(vec.items,ith)
    //
    uint n = vec.length - 1
    uint m = n - ith
    //
    assert |vec.items| >= (ith + 1 + m)
    assert equals(vec.items,ith+1,items,ith,m)
    // Done
    return { items: items, length: n }

This variation seems to verify:
    uint n = vec.length - 1
    uint m = |items| - ith

Yes, this lemma helps:
native function lemma(int[] l, uint i, int[] r, uint j, uint n, uint m)
requires |l| == |r| + 1
requires n <= m && m <= |r|
requires i <= |l| && j <= |r|
requires equals(l,i,r,j,m)
ensures equals(l,i,r,j,n)

Have boiled the lemma down to this, now added to std::array:
// A simple lemma which establishes that, if two arrays are equal for
// a given range, then they are also equal for subranges.
native public function lemma_equals<T>(T[] l, uint i, T[] r, uint j, uint n, uint m)
requires n <= m
requires equals<T>(l,i,r,j,m)
ensures equals<T>(l,i,r,j,n)

The definition of equals<T>() meant that I didn't need everything in the first version.  Adding this lemma does indeed allow it to verify now.

@utting You might interested in this, since it shows an unexpected requirement for a lemma.  In principle, I should add proper syntax.

Unfortunately, I cannot seem to verify this lemma.  It must a trigger or something.  This is my best guess at this stage:
function lemma_equals<T>(T[] l, uint l_start, T[] r, uint r_start, uint n, uint m)
requires n <= m
requires equals<T>(l,l_start,r,r_start,m)
ensures equals<T>(l,l_start,r,r_start,n):
    //
    if n < m:
        assert |l| >= l_start+m
        assert |r| >= r_start+m
        assert l[l_start+(m-1)] == r[r_start+(m-1)]
        lemma_equals<T>(l,l_start,r,r_start,n,m-1)
    else:
        assume equals<T>(l,l_start,r,r_start,n)

I think I'm done with it for now.

Perhaps unsurprisingly, this simplifier variation does verify:
// Check if two array subranges are equal
property equals(int[] l, int[] r, int length) -> bool:
    // Arrays must be big enough to hold subrange
    |l| >= length && |r| >= length &&
    // All items in subrange match
    all { k in 0..length | l[k] == r[k] }

function lemma_equals(int[] l, int[] r, uint n, uint m)
requires n <= m
requires equals(l,r,m)
ensures equals(l,r,n):
    skip

Again, its the problem relating to instantiating arrays of the form arr[s+k].


errors when user quits

I keep getting this kind of error when a user quits (on master):
ERROR:tornado.application:Exception in callback functools.partial(<function wrap.<locals>.null_wrapper at 0xb6c87e84>, <pydle.features.rfc1459.parsing.RFC1459Message object at 0xb6cad56c>)
Traceback (most recent call last):
  File "/home/flavi0/.local/lib/python3.4/site-packages/tornado/ioloop.py", line 600, in _run_callback
    ret = callback()
  File "/home/flavi0/.local/lib/python3.4/site-packages/tornado/stack_context.py", line 275, in null_wrapper
    return fn(*args, **kwargs)
  File "/home/flavi0/.local/lib/python3.4/site-packages/pydle-0.8.0-py3.4.egg/pydle/features/rfc1459/client.py", line 719, in on_raw_quit
    self._destroy_user(nick)
TypeError: _destroy_user() missing 1 required positional argument: 'channel'

Should be fixed now, thanks for reporting!

Don't know if it's directly related, but now I get this, so reopening:
ERROR:tornado.application:Exception in callback functools.partial(<function wrap.<locals>.null_wrapper at 0xb6c39e84>, <pydle.features.rfc1459.parsing.RFC1459Message object at 0xb6c514ec>)
Traceback (most recent call last):
  File "/home/flavi0/.local/lib/python3.4/site-packages/tornado/ioloop.py", line 600, in _run_callback
    ret = callback()
  File "/home/flavi0/.local/lib/python3.4/site-packages/tornado/stack_context.py", line 275, in null_wrapper
    return fn(*args, **kwargs)
  File "/home/flavi0/.local/lib/python3.4/site-packages/pydle-0.8.0-py3.4.egg/pydle/features/rfc1459/client.py", line 719, in on_raw_quit
    self._destroy_user(nick)
  File "/home/flavi0/.local/lib/python3.4/site-packages/pydle-0.8.0-py3.4.egg/pydle/features/rfc1459/client.py", line 106, in _destroy_user
    if status in ch['modes'] and nickname in ch['modes'][status]:
NameError: name 'nickname' is not defined

Seems like some code didn’t survive refactoring properly, apologies!
That issue should be fixed now as well.


Replace enum_primitive by num-derive

The former isn't maintained anymore which brings in outdated
dependencies.

Thanks! Released as 0.44

Thanks ! :)