add fta_users service github repository

Add FTA users service
Provision the github repository for fta users service

Ran Plan for 2 projects:

dir: deployment/cloud workspace: default
dir: deployment/service/fta-users workspace: default

1. dir: deployment/cloud workspace: default
No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

2. dir: deployment/service/fta-users workspace: default
Show Output
data.terraform_remote_state.cloud_deployment: Reading...
data.terraform_remote_state.cloud_deployment: Read complete after 0s
data.google_kms_secret.secrets["docker_username"]: Reading...
data.google_kms_secret.secrets["docker_password"]: Reading...
data.google_kms_secret.secrets["docker_username"]: Read complete after 0s [id=projects/fta-platform/locations/global/keyRings/fta-mstr-kms-main-keyring/cryptoKeys/fta-mstr-kms-main-cryptokey:CiQAVucnPpO3+dUqGbG7KdfdueCDpSsA+meJNdAkPIGDxQRQNxASMwA4ny4N5APvPvsboBth6dp+lR9KpJr+KZoZbnGj/habtlweC1e5PQv6sAwpmyk9ojjgcw==]
data.google_kms_secret.secrets["docker_password"]: Read complete after 0s [id=projects/fta-platform/locations/global/keyRings/fta-mstr-kms-main-keyring/cryptoKeys/fta-mstr-kms-main-cryptokey:CiQAVucnPifGB4MnNecmYsCnSxQRCzbIKukxHQhwRLyT+w1fCksSMgA4ny4NSUtvTYgl066O+xac6ufobge5fSoHJPxeB4DjyCmRZZW+nGio1opHT6dhTCh7]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

  # module.repo_users.github_actions_environment_secret.secret["GITOPS_SSH_PRIVATE_KEY"] will be created
+ resource "github_actions_environment_secret" "secret" {
      + created_at      = (known after apply)
      + environment     = "fta_svc_users_dev"
      + id              = (known after apply)
      + plaintext_value = (sensitive value)
      + repository      = "fta_svc_users"
      + secret_name     = "GITOPS_SSH_PRIVATE_KEY"
      + updated_at      = (known after apply)
    }

  # module.repo_users.github_actions_environment_secret.secret["docker_password"] will be created
+ resource "github_actions_environment_secret" "secret" {
      + created_at      = (known after apply)
      + environment     = "fta_svc_users_dev"
      + id              = (known after apply)
      + plaintext_value = (sensitive value)
      + repository      = "fta_svc_users"
      + secret_name     = "docker_password"
      + updated_at      = (known after apply)
    }

  # module.repo_users.github_actions_environment_secret.secret["docker_username"] will be created
+ resource "github_actions_environment_secret" "secret" {
      + created_at      = (known after apply)
      + environment     = "fta_svc_users_dev"
      + id              = (known after apply)
      + plaintext_value = (sensitive value)
      + repository      = "fta_svc_users"
      + secret_name     = "docker_username"
      + updated_at      = (known after apply)
    }

  # module.repo_users.github_branch.dev[0] will be created
+ resource "github_branch" "dev" {
      + branch        = "dev"
      + etag          = (known after apply)
      + id            = (known after apply)
      + ref           = (known after apply)
      + repository    = "fta_svc_users"
      + sha           = (known after apply)
      + source_branch = "main"
      + source_sha    = (known after apply)
    }

  # module.repo_users.github_repository.repo[0] will be created
+ resource "github_repository" "repo" {
      + allow_auto_merge                        = false
      + allow_merge_commit                      = true
      + allow_rebase_merge                      = true
      + allow_squash_merge                      = true
      + allow_update_branch                     = false
      + archive_on_destroy                      = false
      + archived                                = false
      + auto_init                               = true
      + default_branch                          = (known after apply)
      + delete_branch_on_merge                  = false
      + etag                                    = (known after apply)
      + full_name                               = (known after apply)
      + git_clone_url                           = (known after apply)
      + gitignore_template                      = "Node"
      + has_discussions                         = true
      + has_downloads                           = true
      + has_issues                              = true
      + has_projects                            = true
      + has_wiki                                = true
      + homepage_url                            = "false"
      + html_url                                = (known after apply)
      + http_clone_url                          = (known after apply)
      + id                                      = (known after apply)
      + ignore_vulnerability_alerts_during_read = false
      + is_template                             = false
      + license_template                        = "apache-2.0"
      + merge_commit_message                    = "PR_TITLE"
      + merge_commit_title                      = "MERGE_MESSAGE"
      + name                                    = "fta_svc_users"
      + node_id                                 = (known after apply)
      + primary_language                        = (known after apply)
      + private                                 = (known after apply)
      + repo_id                                 = (known after apply)
      + squash_merge_commit_message             = "COMMIT_MESSAGES"
      + squash_merge_commit_title               = "COMMIT_OR_PR_TITLE"
      + ssh_clone_url                           = (known after apply)
      + svn_url                                 = (known after apply)
      + topics                                  = [
          + "docker",
          + "gcp",
          + "kubernetes",
          + "nodejs",
          + "postgresql",
          + "service",
        ]
      + visibility                              = "public"
      + vulnerability_alerts                    = true
      + web_commit_signoff_required             = false

      + security_and_analysis {
          + secret_scanning {
              + status = "enabled"
            }
          + secret_scanning_push_protection {
              + status = "enabled"
            }
        }
    }

  # module.repo_users.github_repository_environment.environment[0] will be created
+ resource "github_repository_environment" "environment" {
      + can_admins_bypass   = true
      + environment         = "fta_svc_users_dev"
      + id                  = (known after apply)
      + prevent_self_review = false
      + repository          = "fta_svc_users"
    }

Plan: 6 to add, 0 to change, 0 to destroy.

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/service/fta-users

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/service/fta-users

Plan: 6 to add, 0 to change, 0 to destroy.

Plan Summary
2 projects, 1 with changes, 1 with no changes, 0 failed

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

Ran Plan for 2 projects:

dir: deployment/cloud workspace: default
dir: deployment/service/fta_users workspace: default

1. dir: deployment/cloud workspace: default
No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/cloud

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/cloud

2. dir: deployment/service/fta_users workspace: default
Show Output
data.terraform_remote_state.cloud_deployment: Reading...
data.terraform_remote_state.cloud_deployment: Read complete after 0s
data.google_kms_secret.secrets["docker_password"]: Reading...
data.google_kms_secret.secrets["docker_username"]: Reading...
data.google_kms_secret.secrets["docker_username"]: Read complete after 0s [id=projects/fta-platform/locations/global/keyRings/fta-mstr-kms-main-keyring/cryptoKeys/fta-mstr-kms-main-cryptokey:CiQAVucnPpO3+dUqGbG7KdfdueCDpSsA+meJNdAkPIGDxQRQNxASMwA4ny4N5APvPvsboBth6dp+lR9KpJr+KZoZbnGj/habtlweC1e5PQv6sAwpmyk9ojjgcw==]
data.google_kms_secret.secrets["docker_password"]: Read complete after 0s [id=projects/fta-platform/locations/global/keyRings/fta-mstr-kms-main-keyring/cryptoKeys/fta-mstr-kms-main-cryptokey:CiQAVucnPifGB4MnNecmYsCnSxQRCzbIKukxHQhwRLyT+w1fCksSMgA4ny4NSUtvTYgl066O+xac6ufobge5fSoHJPxeB4DjyCmRZZW+nGio1opHT6dhTCh7]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

  # module.repo_users.github_actions_environment_secret.secret["GITOPS_SSH_PRIVATE_KEY"] will be created
+ resource "github_actions_environment_secret" "secret" {
      + created_at      = (known after apply)
      + environment     = "fta_users_dev"
      + id              = (known after apply)
      + plaintext_value = (sensitive value)
      + repository      = "fta_users"
      + secret_name     = "GITOPS_SSH_PRIVATE_KEY"
      + updated_at      = (known after apply)
    }

  # module.repo_users.github_actions_environment_secret.secret["docker_password"] will be created
+ resource "github_actions_environment_secret" "secret" {
      + created_at      = (known after apply)
      + environment     = "fta_users_dev"
      + id              = (known after apply)
      + plaintext_value = (sensitive value)
      + repository      = "fta_users"
      + secret_name     = "docker_password"
      + updated_at      = (known after apply)
    }

  # module.repo_users.github_actions_environment_secret.secret["docker_username"] will be created
+ resource "github_actions_environment_secret" "secret" {
      + created_at      = (known after apply)
      + environment     = "fta_users_dev"
      + id              = (known after apply)
      + plaintext_value = (sensitive value)
      + repository      = "fta_users"
      + secret_name     = "docker_username"
      + updated_at      = (known after apply)
    }

  # module.repo_users.github_branch.dev[0] will be created
+ resource "github_branch" "dev" {
      + branch        = "dev"
      + etag          = (known after apply)
      + id            = (known after apply)
      + ref           = (known after apply)
      + repository    = "fta_users"
      + sha           = (known after apply)
      + source_branch = "main"
      + source_sha    = (known after apply)
    }

  # module.repo_users.github_repository.repo[0] will be created
+ resource "github_repository" "repo" {
      + allow_auto_merge                        = false
      + allow_merge_commit                      = true
      + allow_rebase_merge                      = true
      + allow_squash_merge                      = true
      + allow_update_branch                     = false
      + archive_on_destroy                      = false
      + archived                                = false
      + auto_init                               = true
      + default_branch                          = (known after apply)
      + delete_branch_on_merge                  = false
      + etag                                    = (known after apply)
      + full_name                               = (known after apply)
      + git_clone_url                           = (known after apply)
      + gitignore_template                      = "Node"
      + has_discussions                         = true
      + has_downloads                           = true
      + has_issues                              = true
      + has_projects                            = true
      + has_wiki                                = true
      + homepage_url                            = "false"
      + html_url                                = (known after apply)
      + http_clone_url                          = (known after apply)
      + id                                      = (known after apply)
      + ignore_vulnerability_alerts_during_read = false
      + is_template                             = false
      + license_template                        = "apache-2.0"
      + merge_commit_message                    = "PR_TITLE"
      + merge_commit_title                      = "MERGE_MESSAGE"
      + name                                    = "fta_users"
      + node_id                                 = (known after apply)
      + primary_language                        = (known after apply)
      + private                                 = (known after apply)
      + repo_id                                 = (known after apply)
      + squash_merge_commit_message             = "COMMIT_MESSAGES"
      + squash_merge_commit_title               = "COMMIT_OR_PR_TITLE"
      + ssh_clone_url                           = (known after apply)
      + svn_url                                 = (known after apply)
      + topics                                  = [
          + "docker",
          + "gcp",
          + "kubernetes",
          + "nodejs",
          + "postgresql",
          + "service",
        ]
      + visibility                              = "public"
      + vulnerability_alerts                    = true
      + web_commit_signoff_required             = false

      + security_and_analysis {
          + secret_scanning {
              + status = "enabled"
            }
          + secret_scanning_push_protection {
              + status = "enabled"
            }
        }
    }

  # module.repo_users.github_repository_environment.environment[0] will be created
+ resource "github_repository_environment" "environment" {
      + can_admins_bypass   = true
      + environment         = "fta_users_dev"
      + id                  = (known after apply)
      + prevent_self_review = false
      + repository          = "fta_users"
    }

Plan: 6 to add, 0 to change, 0 to destroy.

:arrow_forward: To apply this plan, comment:atlantis apply -d deployment/service/fta_users

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d deployment/service/fta_users

Plan: 6 to add, 0 to change, 0 to destroy.

Plan Summary
2 projects, 1 with changes, 1 with no changes, 0 failed

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

atlantis apply

Ran Apply for 2 projects:

dir: deployment/cloud workspace: default
dir: deployment/service/fta_users workspace: default

1. dir: deployment/cloud workspace: default
Show Output
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

bucket_name = "fta-mstr-gcs-tfstate"
bucket_self_link = "https://www.googleapis.com/storage/v1/b/fta-mstr-gcs-tfstate"
bucket_url = "gs://fta-mstr-gcs-tfstate"
gsm_iac_secret_data = <sensitive>
iac_repo_fullname = "greyhats13/fta_iac"
iac_repo_http_clone_url = "https://github.com/greyhats13/fta_iac.git"
iac_repo_ssh_clone_url = "git@github.com:greyhats13/fta_iac.git"
main_dns_id = "projects/fta-platform/managedZones/fta-mstr-dns-main"
main_dns_managed_zone_id =<PHONE_NUMBER>482091992
main_dns_name = "fta.blast.co.id."
main_dns_name_servers = tolist([
  "ns-cloud-b1.googledomains.com.",
  "ns-cloud-b2.googledomains.com.",
  "ns-cloud-b3.googledomains.com.",
  "ns-cloud-b4.googledomains.com.",
])
main_dns_zone_name = "fta-mstr-dns-main"
main_dns_zone_visibility = "public"
main_firewall_ids = {
  "icmp" = "projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-icmp"
  "internal" = "projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-internal"
  "rdp" = "projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-rdp"
  "ssh" = "projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-ssh"
}
main_firewall_self_links = {
  "icmp" = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-icmp"
  "internal" = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-internal"
  "rdp" = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-rdp"
  "ssh" = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/firewalls/fta-mstr-vpc-main-allow-ssh"
}
main_nat_id = "fta-platform/asia-southeast2/fta-mstr-vpc-main-router/fta-mstr-vpc-main-nat"
main_pods_secondary_range_name = "pods-range"
main_router_id = "projects/fta-platform/regions/asia-southeast2/routers/fta-mstr-vpc-main-router"
main_router_self_link = "https://www.googleapis.com/compute/v1/projects/fta-platform/regions/asia-southeast2/routers/fta-mstr-vpc-main-router"
main_services_secondary_range_name = "services-range"
main_subnet_ip_cidr_range = "<IP_ADDRESS>/16"
main_subnet_self_link = "https://www.googleapis.com/compute/v1/projects/fta-platform/regions/asia-southeast2/subnetworks/fta-mstr-vpc-main-subnet"
main_vpc_gateway_ipv4 = ""
main_vpc_id = "projects/fta-platform/global/networks/fta-mstr-vpc-main"
main_vpc_self_link = "https://www.googleapis.com/compute/v1/projects/fta-platform/global/networks/fta-mstr-vpc-main"
security_cryptokey_id = "projects/fta-platform/locations/global/keyRings/fta-mstr-kms-main-keyring/cryptoKeys/fta-mstr-kms-main-cryptokey"
security_keyring_id = "projects/fta-platform/locations/global/keyRings/fta-mstr-kms-main-keyring"
security_service_account_email =<EMAIL_ADDRESS>security_service_account_id =<EMAIL_ADDRESS>

2. dir: deployment/service/fta_users workspace: default
Show Output
module.repo_users.github_repository.repo[0]: Creating...
module.repo_users.github_repository.repo[0]: Still creating... [10s elapsed]
module.repo_users.github_repository.repo[0]: Creation complete after 11s [id=fta_users]
module.repo_users.github_branch.dev[0]: Creating...
module.repo_users.github_repository_environment.environment[0]: Creating...
module.repo_users.github_repository_environment.environment[0]: Creation complete after 4s [id=fta_users:fta_users_dev]
module.repo_users.github_actions_environment_secret.secret["GITOPS_SSH_PRIVATE_KEY"]: Creating...
module.repo_users.github_actions_environment_secret.secret["docker_password"]: Creating...
module.repo_users.github_actions_environment_secret.secret["docker_username"]: Creating...
module.repo_users.github_branch.dev[0]: Creation complete after 4s [id=fta_users:dev]
module.repo_users.github_actions_environment_secret.secret["docker_password"]: Creation complete after 7s [id=fta_users:fta_users_dev:docker_password]
module.repo_users.github_actions_environment_secret.secret["GITOPS_SSH_PRIVATE_KEY"]: Creation complete after 8s [id=fta_users:fta_users_dev:GITOPS_SSH_PRIVATE_KEY]
module.repo_users.github_actions_environment_secret.secret["docker_username"]: Creation complete after 8s [id=fta_users:fta_users_dev:docker_username]

Apply complete! Resources: 6 added, 0 changed, 0 destroyed.

Apply Summary
2 projects, 2 successful, 0 failed, 0 errored

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: deployment/cloud workspace: default
dir: deployment/service/fta_users workspace: default


faild build :bash apollo.sh build_opt_gpu;(data_provider.cc: ...has no member named 'count')

Describe the bug
env:

OS: [ubuntu :18.04]
Browser [e.g. chrome]
Version [Apollo:master]
GPU:RTX2080Ti
Nvidia-smi:
Mon Aug 31 16:30:25 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 450.57       Driver Version: 450.57       CUDA Version: 11.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce RTX 208...  Off  | 00000000:01:00.0  On |                  N/A |
|  0%   30C    P8    19W / 280W |    645MiB / 11016MiB |      1%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1427      G   /usr/lib/xorg/Xorg                203MiB |
|    0   N/A  N/A      1795      G   /usr/bin/gnome-shell              185MiB |
|    0   N/A  N/A      4322      G   ...AAAAAAAAA= --shared-files       31MiB |
|    0   N/A  N/A      9432      G   ...token=7462995565156544912       84MiB |
|    0   N/A  N/A     10722      G   ...AAAAAAAAA= --shared-files      135MiB |
+-----------------------------------------------------------------------------+
Question:
when i start command"bash apollo.sh build_opt_gpu",it occurs a error:
"
(08:24:59) ERROR: /apollo/modules/perception/camera/common/BUILD:27:11: C++ compilation of rule '//modules/perception/camera/common:data_provider' failed (Exit 1)
modules/perception/camera/common/data_provider.cc: In member function 'bool apollo::perception::camera::DataProvider::FillImageData(int, int, const uint8_t*, const string&)':
modules/perception/camera/common/data_provider.cc:135:50: error: 'using element_type = class apollo::perception::base::Image8U {aka class apollo::perception::base::Image8U}' has no member named 'count'
     memcpy(rgb_->mutable_cpu_data(), data, rgb_->count() * sizeof(data[0]));
                                                  ^~~~~
modules/perception/camera/common/data_provider.cc:139:50: error: 'using element_type = class apollo::perception::base::Image8U {aka class apollo::perception::base::Image8U}' has no member named 'count'
     memcpy(bgr_->mutable_cpu_data(), data, bgr_->count() * sizeof(data[0]));
                                                  ^~~~~
modules/perception/camera/common/data_provider.cc:143:52: error: 'using element_type = class apollo::perception::base::Image8U {aka class apollo::perception::base::Image8U}' has no member named 'count'
     memcpy(gray_->mutable_cpu_data(), data, gray_->count() * sizeof(data[0]));

"
Anyone can help me for this question?Thanks!

Got it. We will look into this issue right now.

Thanks!
Also,this data_provider.cc once occurd other error:
"
(05:37:08) ERROR: /apollo/modules/perception/camera/common/BUILD:27:11: C++ compilation of rule '//modules/perception/camera/common:data_provider' failed (Exit 1)
In file included from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/cuda_runtime.h:95:0,
                 from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/nppdefs.h:52,
                 from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/nppi.h:60,
                 from modules/perception/camera/common/data_provider.cc:18:
bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/channel_descriptor.h:104:1: error: template with C linkage
 template<class T> __inline__ __host__ cudaChannelFormatDesc cudaCreateChannelDesc(void)
 ^~~~~~~~
bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/channel_descriptor.h:137:1: error: template specialization with C linkage
 template<> __inline__ __host__ cudaChannelFormatDesc cudaCreateChannelDesc<char>(void)

"
i fix the this question,with adding "#include <cuda_runtime.h>"
#include <cuda_runtime.h>
#include <nppi.h>

在nppi.h前加入一条：cuda_runtime.h

Thanks!
Also,this data_provider.cc once occurd other error:
"
(05:37:08) ERROR: /apollo/modules/perception/camera/common/BUILD:27:11: C++ compilation of rule '//modules/perception/camera/common:data_provider' failed (Exit 1)
In file included from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/cuda_runtime.h:95:0,
                 from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/nppdefs.h:52,
                 from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/nppi.h:60,
                 from modules/perception/camera/common/data_provider.cc:18:
bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/channel_descriptor.h:104:1: error: template with C linkage
 template<class T> __inline__ __host__ cudaChannelFormatDesc cudaCreateChannelDesc(void)
 ^~~~~~~~
bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/channel_descriptor.h:137:1: error: template specialization with C linkage
 template<> __inline__ __host__ cudaChannelFormatDesc cudaCreateChannelDesc<char>(void)

"
i fix the this question,with adding "#include <cuda_runtime.h>"
#include <cuda_runtime.h>
#include <nppi.h>

在nppi.h前加入一条：cuda_runtime.h

I am wondering if you haven't pull the latest master ... I cleaned up everything bazel outputs, and can't reproduce your issue.

Thanks!
Also,this data_provider.cc once occurd other error:
"
(05:37:08) ERROR: /apollo/modules/perception/camera/common/BUILD:27:11: C++ compilation of rule '//modules/perception/camera/common:data_provider' failed (Exit 1)
In file included from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/cuda_runtime.h:95:0,
                 from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/nppdefs.h:52,
                 from bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/nppi.h:60,
                 from modules/perception/camera/common/data_provider.cc:18:
bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/channel_descriptor.h:104:1: error: template with C linkage
 template<class T> __inline__ __host__ cudaChannelFormatDesc cudaCreateChannelDesc(void)
 ^~~~~~~~
bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include/channel_descriptor.h:137:1: error: template specialization with C linkage
 template<> __inline__ __host__ cudaChannelFormatDesc cudaCreateChannelDesc<char>(void)

"
i fix the this question,with adding "#include <cuda_runtime.h>"
#include <cuda_runtime.h>
#include <nppi.h>

在nppi.h前加入一条：cuda_runtime.h

I noticed that you use CUDA-11.0, was that inside docker ?

But，lastest master haven't build successfully.

But，lastest master haven't build successfully.

We actually haven't tested master with CUDA-11.0 w/ cuDNN-8 yet. Hopes that We can make compatibility with CUDA-11.0 (w/ cuDNN8) toolkit possible in the next  few days.
Thank you for reporting this issue, and sorry for the inconvenience.

1-in docker. I run nvidiasmi，it appear. but，my Ubuntu is not Rt operation system.
2- Because after I install apollo kernel ，run bash dev_start. sh，it show docker run --gpus all -it .... then ，it stop go on，my computer crashd，ubuntu no any reaction. only，strongly shutdown。
3- i also try 5.5 and pre6 in Ubuntu not RT. it can bootstrap.

1-in docker. I run nvidiasmi，it appear. but，my Ubuntu is not Rt operation system.
2- Because after I install apollo kernel ，run bash dev_start. sh，it show docker run --gpus all -it .... then ，it stop go on，my computer crashd，ubuntu no any reaction. only，strongly shutdown。
3- i also try 5.5 and pre6 in Ubuntu not RT. it can bootstrap.

Got it. Please don't install the old and seemingly unmaintained 4.4 based Apollo-RT kernel if you want to run the simulators only.
We are planning for document upgrade and will warn users of usage for this RT/non-RT kernel case.
Thanks again for reporting.

Thank you.  I look forward to seeing your  upgrade document for simulators.
And can you give a suggest for Cuba version？I will try reinstall nvidia again.
now the perception module of lastest master can use for lgsvl simulator？

nvidia

Theoretically,  as long as NVIDIA Driver >= 440.33, it will be OK. CUDA 10.2 was pre-installed into Apollo docker images. So for CUDA toolkit out of docker, CUDA toolkit >= 10.2 will be OK.
For perception,  I will ask other members of our team for updates. @jeroldchen

@devynliu Of course perception module supports LGSVL simulator, as we have updated the dag file for LGSVL at https://github.com/ApolloAuto/apollo/blob/master/modules/perception/production/dag/dag_streaming_perception_lgsvl.dag. This is the default dag to launch perception module under LGSVL mode.

Thanks. i slove this issue(build),with reinstall nivida driver 440.36 and cuda 10.2.89.

@jeroldchen hello,i now run Apolloolatest master and lgsvl simulator,i can start perception moudule.
1- but the recognition quality with lidar and radar is very bad.example,when other car pass through ,the perception somtimes cannot recognize.
2- and the traffic module cannot start,the log show"Path does not exist: /apollo/bazel-bin/modules/perception/onboard/component/libperception_component_camera.so",Now ,can this question be sloved?
thanks！

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


Multiples Components best practices: sharing bridge?

Hi again.
The context first:
Im using RN as the V in MVC. I've created a JS with a RN component, created a UIView in the obj-c side, and use a RCTRootView (initWithBridge) as a subview.
Everything works fine.
Now the question.
Suppose that I have a two RN components, in two JS files (DetailView.js, SomeOtherView.js).
Is there a way to make a single JS file with the 2 components, so I can use only one bridge and share it. I dont really understand how can I achieve this, and use initWithBridge: moduleName:
Sorry if is a super noob question.
Thanks and regards

Yes, you can create the bridge using
RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL: moduleProvider: launchOptions:];

Then store that in a property somewhere (e.g. in your AppDelegate), and whenever you need to create a root view, say:
RCTRootView *rootView = [[RCTRootView alloc] initWithBridge: moduleName:];

That way the JS code bundle is shared, and each root view runs its own component.

Hi. thanks for the response.
What I dont really get it yet is how I can put multiple JS files in one single bundle?
Where every JS file is an independent component

Please see these two issues, it should address your previous question.
Best practice to integrate existing app with React-Native #995
Forcing view refresh #1049

@finalquest - react-native bundle will do that for you, if you have any questions that aren't answered by this thread or the issues that @ssssssssssss mentioned let me know, closing until then

hey guys, if i take it correctly, if i want to share the same bridge, then i need to bundle all the js files/functions to a big bundle, right? is there a way that i can still share the bridge but download every module every single time?

@dolmens - what's your use case?

@brentvatne say i choose to place the js bundle on server side, and i have many react views, named v1, v2, ..., etc., corresponding to js module m1, m2, ..., etc., and i want to download these modules on demand, in other words, i don't download them only until i show the corresonding views.

@dolmens - Ah, interesting. As far as I know, this is not supported at the moment

Yeah, @brentvatne is right, it's not possible yet... The bridge holds where to require the javascript bundle, the RootView just knows which module to require, but it has to be previously loaded by the bridge.

@brentvatne can you give some more details about how to put multiple JS files into a single bundle, using react-native bundle?


Fix crash with the index type function, where it would stack overflow due to not waiting for a pending-expansion

Fix for https://github.com/luau-lang/luau/issues/1406
I'd recommend generalized functions for sanity checks like these, since there will be more cases of similar issues I believe.
But if this gets done, I hope that they'll be connected to the Solver Logger, because I actually refined mine with colors and more info (yet need to finish that) to understand the Luau Source Code more and to debug issues.

A Unit Test is going to appear soon!
I need to cope with the /out folder, hence why I really need this https://github.com/luau-lang/luau/pull/1394

Unit Test is there now


Update instructions based on recently walking through them

Add :latest tag when creating workstation configuration
When I tried creating the workstations without specifying a tag to pull,
they failed to pull every time. Maybe Cloud Workstations doesn't
automatically default to :latest when no tag is specified?
Curious if this was working for you @kmontg @jerop as it was - maybe there was something else going wrong 🤷♀ 🤷♀ 🤷♀
Make instructions for providing your own image registry a bit clearer
I tried to run through this myself and got a bit confused so I added
another substitution var for the image registry, and changed the example
GCB command to provide the substitutions on the command line so you
don't need to change the cloudbuild.yaml to change those values.
Re-added logic I'd (foolishly) previousy removed to default the tag to
'latest' if no commit hash env var exists.
Also changed markdown numbering so that items can be moved around/added
without having to keep them all in sync.
Move local instructions to the bottom
Assuming most ppl will come to this repo wanting to run this as a
cloud workstation, so putting those instructions first in the README.

I walked through these steps last week and they did work, but specifying the tag sounds good to me to be explicit.
Though just for posterity I remember (partially, it’s a bit fuzzy) running into an issue with the default service account for cloud workstations and just wanted to note that. I believe the issue was that it might be created when the service is enabled or used for the first time, so if you run the steps too quickly (in a fresh project) I believe granting the IAM permission to the image might fail. Just wanted to call that out in case it comes up again. Maybe creating the service account too and not relying on the default might be a good idea?

LGTM though!

lol nooooo I thought my numbering was so fancy


auto-complete broken when a generic is used as both function parameter and argument

TypeScript Version:  2.2.1 / nightly (2.2.0-dev.201xxxxx)
Code
Copy paste the code below in TypeScript Playground.
// a function that takes one typed object argument
function doSomething(props: { a: number, b?: string }) {
    // code
}

// a function that takes a function and calls it with the given props
function call<P>(fn: (props: P) => any, props: P): void {
    // code
}

// type { or {} and ctrl-space and you see nothing
// type {a or {a} and you see a: any
// type {a:1, } and ctrl-space and you see b: string
// type {a:1, b} and ctrl-space and you see nothing
call(doSomething, { a: 1 });

// I managed to get a different behavior if I use
// keyof on the generic type
export type Same<T> = {
    [P in keyof T]: T[P];
};

// Same as call() but wraps P with Same<>
function callSame<P>(fn: (props: P) => any, props: Same<P>): void {
    // code
}

// type { or {} and ctrl-space and you see nothing
// type {a or {a} and you see a: number
// type {a:1, } and ctrl-space and you see b: string
// type {a:1, b} and ctrl-space and you see b: string
callSame(doSomething, { a: 1 });

// I managed to get a different behavior if I use
// T extends P for the second parameter
function callExtends<P, T extends P>(fn: (props: P) => any, props: T): void {
    // code
}
// type { or {} and ctrl-space and you see nothing
// type {a or {a} and you see a: any
// type {a:1, } and ctrl-space and you see nothing
// type {a:1, b} and ctrl-space and you see b: any
callExtends(doSomething, { a: 1 });

Expected behavior:
Auto-complete (ctrl-space) should display the properties 'a: number' and 'b: string'.
Actual behavior:
It's very inconsistent but overall doesn't work. I even managed to get some different behavior if I use keyof on the generic type or use generic extends.

The issue here is that the argument is in an inference position. the compiler uses the type of the object literal to infer the generic type argument type; this happens to be the same type the language service uses to provide completions, so you basically get completions for the same type you are just writing, which is nothing.
There is not really a simple way to know if this is a place where you want to infer from, or just one to check against the type from the other argument.

I agree with your comment @mhegazy for the first 2 examples, however in the 3rd example I made it explicit that the first argument is the source of truth and the second argument needs to be type-checked against it (using T extends P):
function callExtends<P, T extends P>(fn: (props: P) => any, props: T): void {

again, T is an inference target. and constraints are only used to check inferences once they occurred, and they are not inference positions themselves. so if you write callExtends(fn, {}) T is inferred as {}.

Why this is closed?

Because as the issue is tagged and as explained, it is a design limitation as it is difficult to infer type information in the locations exampled and therefore impossible to auto-completion intellisense.


Release 2.2.0

Pull Request
My patch is about

[ ] :bug: Bugfix
[ ] :arrow_up: Improvement
[ ] :pencil: Documentation
[ ] :heavy_check_mark: Tests
[ ] :sparkle: Feature
[x] 🔖 Release

Checklist

[x] I accept that my PR will be distributed under the MIT license.
[ ] Test cases added for changed code if necessary.

Describe what you have changed in this PR.

Improvement: Implement insert() method on Headers class.
Feature: Introducing the Attributes class in models. Attributes/members are now ordered by default.
Improvement: Add pop() and insert() methods on Header class.
Bugfix: Unescape the double quote char in the cookie value when using SetCokies or Cookie classes.
Improvement: Implement valued_attrs property on Header.

Codecov Report

Merging #33 into master will increase coverage by 0.94%.
The diff coverage is 89.83%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
+ Coverage   87.36%   88.31%   +0.94%
==========================================
  Files           7        7
  Lines        1100     1215     +115
==========================================
+ Hits          961     1073     +112
- Misses        139      142       +3

Impacted Files
Coverage Δ

kiss_headers/api.py
91.54% <ø> (+4.88%)
:arrow_up:

kiss_headers/builder.py
82.03% <0.00%> (ø)

kiss_headers/utils.py
91.30% <ø> (-3.63%)
:arrow_down:

kiss_headers/models.py
91.53% <90.55%> (+1.80%)
:arrow_up:

kiss_headers/__init__.py
100.00% <100.00%> (ø)

kiss_headers/structures.py
90.90% <100.00%> (+0.58%)
:arrow_up:

kiss_headers/version.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 26fe929...719b6f5. Read the comment docs.


How to generate the list of RangeFilter's from ModelMultipleChoiceFilter?

How to generate the list of RangeFilter's from ModelMultipleChoiceFilter?
ModelMultipleChoiceFilter produce the list of variants to choose. Filter will check - are property exist in instance? I need to generate the list of RangeFilter widgets, to check values, linked to ManyToManyField.
Can you give me an example?

Here is a scetch for DB struct and wanted interface

Please use the Mailing List for usage questions and discussions. Thanks!


Better UX for autosuggesting host graphs

cc @hannah-martinez

Updating the hint text to "Start typing to choose a host graph..." or changing to a dropdown would both be better UX


error statement

Question: I'd like to be able to insert assert false in the code, and have Infer tell me if it thinks that that statement is reachable. Is this possible?
Some extra info:
Unless I'm crazy, which is not unlikely, I recall that using while(true){} worked (in the sense that there was a warning when such a piece of code was reachable). But now (08d4465e1dbde345fd96a2df13640388ff20b85f), I don't get any warning on file A.java with content
class B { static void f() { assert false; } }
class C { static void f() { while (true); } }
public class A { public static void main() { B.f(); C.f(); } }

when I use the command infer -- javac A.java.
Is there something that can be used as an error statement (in Java)? Do I need to give it some command line options? If it's not possible now, are there any plans to introduce one? As you know, other tools do support such a statement; most notably, it's used in the SV-COMP benchmarks.

This is possible, but only in a somewhat hacky way at the moment. You can use Object o = null; o.toString() as an alias for assert false, and Infer will report a null dereference on o only if it thinks that the dereference is reachable.

If I say
class B { static void f() { assert false; } }
class C { static void f() { while (true); } }
class D { static void f(boolean a) { if (a) {Object o = null; o.toString();} } }
public class A { public static void main() { B.f(); C.f(); D.f(false); } }

I get a warning no matter what argument I actually send D.f. I'd like to get a warning only if I call with the argument being true. The null trick you suggest is actually what I was trying before @ddino showed me that while(true){} does what I want. But it stopped working in the meantime ...

Ah, good point. My original suggestion will not work so well for what you want. But what about f(Object o) { o.toString(); } with f(null) as an alias for assert false?

Hmm, it still doesn't seem to be compositional. Here's a function: void f(Object x, Object y) { /* ??? */ }. What do I put in there to force infer to find a (single) triple with the precondition x!=y and complain later only if f is used in a way for which that triple is not enough? This worked: void f(Object x, Object y) {while(x==y);}.
Here's how I tried to use your second proposal (so you can check if I did something wrong):
public class T2 {
  void assertF(String o) { o.toString(); }

  void f(Object x, Object y) {
    if (x != y) assertF(null);
  } // gives warning even if g is commented out
  /*
  void g() {
    f(1, 2); // ok
    f(null, null); // nok
  }
  */
}

Thanks, that does indeed clear things up!
I think that the triple you want is what can/will inferred for the on-paper version of the bi-abduction algorithm, but the Infer implementation chooses to report a warning in this case for pragmatic reasons (assuming that all branches are reachable in some context lets us report more bugs without causing too many false positives).
If I'm right about this, I'm not immediately sure how to talk Infer into doing what you want. Let me think about it a bit more.
(Copying @cristianoc and @ddino since they have better knowledge about how the theory and practice diverge here.)

Notice that Infer works bottom-up, so if f calls g then Infer's decision on whether reporting on g will not be affected by how f calls it.
For example, If f contains if (a) {Object o = null; o.toString();} then the error is reported in f no matter how it's called.
If f contains instead if (a) {o.toString();} then nothing is reported in f but will be reported in g if it calls f the wrong way (with a=true and o=null).
Being bottom-up, it might be difficult to model the typical top-down reachability question, as if the error is reported half way through the chain of calls, it won't be reported in calls higher up the call stack.
One attempt could be to put a dereference in the code that you wish to know if reachable, as in foo(Object r,...) { ...r.toString;...}
Then pass r through each call, untouched, and only call it with null from main, or from the roots of the program where one would like to know if it's reachable.
Another proviso is that the analysis might fail for a number of reasons (errors found, limits to the number of operations, etc), so it might not explore all the paths, and fail to report reachability.

Bottom up "reachability" is what I want. I want to cook up a procedure with a given pre (say, x!=y) and then have infer say when that procedure is called in a situation where the pre doesn't hold. The issue is convincing Infer to use the precondition I want. The precondition I want will always be a (Java, boolean) expression over the arguments.

as if the error is reported half way through the chain of calls, it won't be reported in calls higher up the call stack.

So, that's OK in principle. But, why is there an error reported in f in the T2 example? Clearly it can continue propagating up the pre.

I dug a bit to make sure I'm not crazy. This is the file I was actually looking at some time ago (with @ddino):
import java.util.Random;

class G { // global
  static private Object tracked = null;
  static private int state = 0;
  static void get_ret(Object x) {
    if (maybe()) tracked = x;
  }
  static void go_ret(Object x) {
  }
  static void go_call(Object x) {
    if (x == tracked) {
      if (state == 0) state = 1;
      else if (state == 1) {while (true);}
    }
  }
  static boolean maybe() {
    return random.nextBoolean();
  }
  static private Random random = new Random();
}

class O {
  private O() {}
  public static O get() {
    return new O();
  }
  public void go() { }
}

public class T3 {
  public static void main(String[] args) {
    O x = O.get();
    G.get_ret(x);
    O y = O.get();
    G.get_ret(y);
    G.go_call(y);
    y.go();
    G.go_call(x);
    x.go();
    G.go_call(x); // HERE
    x.go();
  }
}

This used to give a warning on line marked with HERE. It stopped giving a warning at commit 3fb8801b6c8672ad0b7819aeda74d1feb4325be7 (by @cristianoc).
In any case, even if the parent commit gives a warning on T3@HERE (which I want!), it does not give a warning on the following:
public class T2 {
  void assertF(String o) { o.toString(); }

  void f(Object x, Object y) {
    //if (x == y) assertF(null);
    while (true);
  }
  void g() {
    f(1, 2); // ok
    f(null, null); // nok
  }
  public static void main(String[] args) {
    while (true);
  }
}

I don't understand why. I'm rather confused at this point.

Oh, maybe it's because G.go_call has some specs, while T2.f doesn't.

Last time I forgot to say that one needs -nf to see the warning with older versions. Also, I misidentified the culprit, probably by messing up some git bisect command. The issue appeared in a9f1d21dd210f41c5632cff23ddce06361bd6d8c. I'll put a comment on the commit to ask if the change was intended. (I hope not.)
Here's a small change that brings back the missing warnings:
m.zip

One can get back the warnings with --debug-exceptions. I'm closing.


chore: WDS refine shadows

Follow-up to #29702

Please add your planning poker estimate with Zenhub @KelvinOm


⚠ GitLab Server has degraded performance

In 9d6b206, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 13986 ms

Resolved: GitLab Server performance has improved in c0d9e49.


Corruption writing to file with accelerometer example

When using the accelerometer example on the GitHub page, and reading the serial data using TeraTerm, the received data is corrupted, as enclosed. It looks to me like the kind of symptom you'd get with concurrent write access to the file or pointer overruns, but it may have another cause, of course. I don't believe it is corruption on reception of the serial data, because the string "MICROBIT_FS_1 " appears in the data, and it is hard to explain that except by corruption during either reading or writing the file.
Time    Acceleration
4580    704
4653    704
4658    672
4663    672
4735    720
4740    720
4813    720
4818    720
4891    688
ÿÿ      688ÿ!ÿÿÿ        ÿÿIÿ4973        %ÿ
ÿÿÿ•688
ÿÿïÿ    656ÿ=ÿÿÿ        656
5169    656
5174    656
5268    624
5273    624
5366    656
5371    656
5375    688
5470    624
5475    624
5569    672
5574    672
5668    640
5673    640
5767    624
5772    624
5776    624
5870    640
5875    640
5969    640
5974    ÿÿÿ6068 !ÿ
ÿÿÿI640
ÿ%ÿ     640ÿ•ÿÿÿ        640ÿ6177        =ÿ
6270    640
6275    640
6369    640
6374    640
6468    624
6473    624
6567    640
6572    640
6576    640
6670    624
6675    640
6770    640
6776    640
6870    640
6879    640
6972    624
6977    624
6981    624
7075    640
7080    640
7MICROBIT_FS_1  0@œ624
7277    624
7371    624
7376    640
7381    640
7475    640
7480    640
7574    640
7579    640
7673    624
7678    624
7772    640
7777    640
7781    640
7875    624
7880    624
7974    624
7979    640
8073    640
8079    640
8173    640
8179    640
8186    640
8280    62Time  Acceleration
                                8153    16
8158    16
8230    16
8235    16
8239    16
8312    112
8316    112
8388    32
8393    32
8465    32
8470    32
8542    32
                8546    32
8550

Could you share project in PXT and post the URL in this bug?

This bug affects me too. Corruption begins at data index 116 when printed to serial, and becomes more prevalent after that: https://pxt.microbit.org/55832-64036-02150-34008
I get the corruption simonmorrish showed at line 25 and on using the file append line to wrote strings: https://pxt.microbit.org/96921-93818-70560-16976

...I have found that by removing the radio or bluetooth package from the javascript explorer, the corruption starts later, at line 300 or so

Corruption is fixed through new heap allocator. Indeed BLE stack was silently corruption heap.


Changes in 0.30 deny access to HA services

Problem/Motivation
I assumed that this was a normal update in Home Assistant and that the changes would only be "minor".
Expected behavior
All services are still accessible via the Netbird network.
Actual behavior
No services are accessible anymore, except the Home Assistant itself (port 8123).
Services such as n8n, traefik or vaultwarden are no longer accessible via the netbird network.
Steps to reproduce
After restoring the backup to 0.29.4, all other ports are via the Netbird network accessible again.
Proposed changes
I didn't expect my configuration to be thrown away.
For me, this and the fact that something in the container/client has changed is all a major change.
I would have expected a note in the changelog.
Not only regarding the configuration change but also regarding the ACL or whatever the cause is.

mv /mnt/data/supervisor/homeassistant/netbird/config.json /mnt/data/supervisor/addon_configs/7edd9457_netbird/config.json
or simple in a terminal:
mv homeassistant/netbird/config.json addon_configs/7edd9457_netbird/config.json
in the next version i try to fix it

v<IP_ADDRESS> fix it

Thank you very much for that, the problem with the config was understandable and not the cause as it seemed.
I used the "diff" command to adjust and compare the configurations, apart from the keys nothing was different in the end, but access via the Netbird network was different.
Something was changed in the client so that only port 8123 (Home Assistant) was accessible from the outside.
your change also failed with the following output:
-----------------------------------------------------------
 Add-on: NetBird
 Connect your devices into a single secure private WireGuard®-based mesh network.
-----------------------------------------------------------
 Add-on version: v<IP_ADDRESS>
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (amd64 / generic-x86-64)
 Home Assistant Core: 2024.10.1
 Home Assistant Supervisor: 2024.09.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to DEBUG
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service netbird: starting
s6-rc: info: service netbird successfully started
s6-rc: info: service legacy-services: starting
mv: can't remove '/homeassistant/netbird/config.json': Read-only file system
[23:52:00] INFO: Service NetBird Client exited with code 1 (by signal 0)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service netbird: stopping
s6-rc: info: service netbird successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

v<IP_ADDRESS> fix it

I updated from v0.29.x directly to v<IP_ADDRESS> yet I still ran into this issue.
-----------------------------------------------------------
 Add-on: NetBird
 Connect your devices into a single secure private WireGuard®-based mesh network.
-----------------------------------------------------------
 Add-on version: v<IP_ADDRESS>
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (amd64 / qemux86-64)
 Home Assistant Core: 2024.10.1
 Home Assistant Supervisor: 2024.09.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service netbird: starting
s6-rc: info: service netbird successfully started
s6-rc: info: service legacy-services: starting
mv: can't remove '/homeassistant/netbird/config.json': Read-only file system
[17:01:06] INFO: Service NetBird Client exited with code 1 (by signal 0)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service netbird: stopping
s6-rc: info: service netbird successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

i hope in  v<IP_ADDRESS> it's working


Unbinding problem

So i have problem that whenever i boot up tf2 all my movement keys and my call for medic keys unbind.Its really frustrating bc it happens everytime and it stops when i delete masterscomfig.Its really a shame bc its very good config .
* Config version-Medium low (problem happens on every one)
* Config preset and addon(s)- Chris config
* Custom values (if any)-none
* DX level-95 (it happens on each one)
* Launch options- -dxlevel 95 -refresh 120 -heapsize 1048576 -full -w 800 -h 600 -console -novid -useforcedmparms -noforcemaccel -noforcemspd -nosteamcontroller -softparticlesdefaultoff -reuse -lv -autoexec.cfg
* Operating system (OS)- windows 7 64bit
* Graphics card (GPU)-ATI Radeon HD 3400 Series
* Processor (CPU)- AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ 3.00 GHz
* HDD or SSD-none
* RAM size in MB or GB- 6 GB

I hope you fix it and thanks in advance!

Config preset and addon(s)- Chris config

?
Also, do you use custom.cfg?

Nvm i fixed it.There were some shenanigans with my config file so i reinstalled it and it works fine


After authentication while redirecting back to application return error 404 not found.

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.0.2
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.0.2
Description
Hello Team
I am using azure/msal in angular 12.2.0 application. It’s working fine on http://localhost:4200/. I had deploy my application apache server, its’ redirecting on Microsoft authentication site and open authentication popup. After successful authentication it’s redirect on return url, now I am getting 404 not found : The requested URL was not found on this server.
Application Authentication Steps –

Hit url https://abc-xyz.com// on browser.
Redirect to https://abc-xyz.com/login page. –Excepted
Checking local storage for token and user information if user authenticated redirect to /home page, if not redirect to Microsoft authentication site and open authentication popup. - Excepted
After authentication redirect back to https://abc-xyz.com/login page. Now I am getting Error 404 not found. -Unexcepted

Redirect Uri on Azure AD: https://abc-xyz.com/
Redirect Uri on Application Config: https://abc-xyz.com/
Server SSL Information:  Your connection is to this site is not secure.
MSAL Configuration
No response
Relevant Code Snippets
No response
Identity Provider
Azure AD / MSA
Source
External (Customer)

@UMANGAWASTHY It looks like your server is not configured correctly to route /login to your Angular application when a user visits the page directly (it works initially likely because you are using client-side routing in Angular). Please verify your server configuration to ensure any pages on your application are routed to your application when visited directly.
Closing, as this is outside of the scope of MSAL.js.

@UMANGAWASTHY Again, the issue if your web server not routing /login to your app correctly, not anything to do with MSAL.js.


Additional Statiistics

Readable names for species, parameters. Look at the fraction of the string that is a number. Want to avoid names like "s1", "s2", ...

Patterns
Add moiety
Remove moiety
Transfer moiety
Fraction of parameters, species that are annotated
For readability, use "Frac Dissimilar Names" for a namespace such as species and parameters


CKB Indexer references are conflicting

On this page, "https://docs.nervos.org/docs/integrate/introduction," we find the following statements:
1. "It is not recommended to use the ckb node internal Indexer module to collect live cells, which is very slow and deprecated."
2. "You may also need an indexer to index live cells and transactions, and then you can try CKB Indexer. If you are looking for a one-stop solution that includes both node and indexer, you can try Perkins' Tent."
However, we also have on the same page:
"Since v0.105.0, CKB has integrated the functions in previous standalone ckb-indexers. Users of v0.105.0 nodes or above have no need to start ckb-indexer service separately. Ckb-indexer-related RPC is included in the current RPC as a module. Users don't have to configure the indexer port separately."
So for me, number 1 seems conflicting. Number 2 also seems possibly deprecated with the reference to Perkins' tent. I think we need to be more clear about the preferred method of operation, with the caveat of how to run indexer on its own if so desired.

Associated https://github.com/nervosnetwork/docs-new/issues/160

The outdated inconsistencies have been fixed, if you find there is still something ambiguous and misunderstood, feel free reopen.


@Output event not emitting from nzOnOk when modal is inside a component within a ng-template

Reproduction link
https://stackblitz.com/edit/angular-yqmg18
Steps to reproduce

Create a component and put it inside a ng-template.
Add a button to trigger the modal within the template.
Emit an @Output event in the nzOnOk method from the modal.
The @Output event is not emitted as expected when the modal is inside a component that is inside a ng-template.

What is expected?
The @Output event from the nzOnOk should be emitted correctly even when the modal is inside a component that is inside a ng-template.
What is actually happening?
The @Output event does not trigger when the modal is placed inside a component within a ng-template.

Environment
Info

ng-zorro-antd
18.1.1

Browser
Brave

In your example when you open a dialog popover is closed(and destroyed), because of this there are no subscribers to the Observable, which leads to non-obvious behavior. Modal has ref to destroyed component, without @output subscribers.


Document all public APIs in Jupyter.csproj.

This PR adds API documentation for all public APIs in the Jupyter project for IQ#.

Thanks for the review, @tcNickolas! I've addressed your comment, which as a side effect dismissed your review. If you could please approve again, I'd appreciate it. Thanks!


Canceled appointments

I noticed that when I received a cancelled appointment on outlook "source" side, the meeting in outlook now says "Canceled: "
However nothing gets reflected on the outlook "destination" side
How do I get those cancelations reflected?
In case it matters, this is what I have for eventResponseTypes
[
"organizer",
"accepted",
"tentativelyAccepted",
"none",
"notResponded"
]

I think you're seeing this because cancelled meetings are still meetings
for most intents and purposes. I'm sure you can track down a way to
identify the cancelled ones, thick (if nothing else, could maybe look for
the text in the title.)
But I just wanted to mention that this feels like the correct behavior to
me, and share my personal solution. After I get the cancelled message, I
usually just hit the "remove from calendar" button that Outlook provides
for them, then it I'd no longer synced. To my mind, if I'm leaving a
cancelled meeting on my calendar, it's because I want that time to remain
blocked, so still copying it between calendars is what I would want.
That said, since Outlook is able to recognize cancelled meetings, with some
digging you might be able to find the indicator it is using to recognize
them.
On Wed, Jan 31, 2024, 8:46 AM arcegabriel @.***> wrote:

I noticed that when I received a cancelled appointment on outlook "source"
side, the meeting in outlook now says "Canceled: "
However nothing gets reflected on the outlook "destination" side
How do I get those cancelations reflected?
In case it matters, this is what I have for eventResponseTypes
[
"organizer",
"accepted",
"tentativelyAccepted",
"none",
"notResponded"
]
—
Reply to this email directly, view it on GitHub
https://github.com/MShekow/outlook-calendar-sync/issues/6, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADMUG5QQ64VVGC3RZT5EYCLYRJKMDAVCNFSM6AAAAABCTGDZA6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYTAMRWGEZDMMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

While it would be interesting to know what the responseType of cancelled meetings is, I also agree with @travisterrell in that this is expected behavior - thanks for your support / explanations.

Thanks - I couldnt figure out the responsetype. Not sure where to look
For my use case - once something is cancelled it should be gone. I don't monitor the soure (secondary for me). The problem now is that even though the source is change to "Canceled: Title" the target is unchanged " Title"
So you can only see the event was cancelled on the source
Once I accept cancelation manually, it dissapears from source and target
Workarounds

Set outlook to accept all invites and delete cancelations. Problem I have is accept all invites
VBA to delete canceled meetings - I went this route


[RFC] Add Mercure

Add Mercure or something similar.
But first, wait until https://github.com/dunglas/mercure/issues/105 solved.

Closing in favor of: https://github.com/spiral/roadrunner-plugins/issues/6


rev different betwen nix-prefetch-git and prefetch-github

Hi, if I am running nix-prefetch-github --nix without specify --rev option, why the result is different from nix-prefetch-git command?
nix-prefetch-github seems prefetch old rev instead of newest like nix-prefetch-git did. Can you explain about this?Is this intended result from nix-prefetch-github?

This appears to be detail in a nix-prefetch-github as you've reported https://github.com/seppeljordan/nix-prefetch-github/issues/9
and not an issue with nix-prefetch-git which is maintained in nixpkgs.


try to profile pydantic-core main

Change Summary
Stacked upon #10886 with additional changes to measure current pydantic-core main, as per #10845 concern.
Related issue number
N/A
Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Looks like this perf regression has been resolved on the pydantic-core side. Closing this for now 👍


Add Python 3.12 support.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@37f9cbe). Click here to learn what that means.

:exclamation: Current head 354d1ed differs from pull request most recent head f17a08c. Consider uploading reports for the commit f17a08c to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage        ?   99.09%
=======================================
  Files           ?        8
  Lines           ?      444
  Branches        ?        0
=======================================
  Hits            ?      440
  Misses          ?        4
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

(blocked on 3.12 support in aiohttp)


Updates Arquillian Core and some mvn plugins

Intentionally skipped:

Guava
Jacoco (new version of ARQ integration coming soon)
Glassfish container (separated PR with ARQ Chameleon if you are interested can be sent separately)
Coveralls plugin

Travis is failing..
Could you check whats going on?
I will probably find some time after weekend to test and merge it...

Sure I will, funny as I ran the build locally.


[DOC] Conformed to new-standards

conformed the _fit function from classification\deep_learning  to new standards of Aeon's docstrings

Reference Issues/PRs
closes: #1150

The comment should follow this format, only the datatype or relevant datatype info should be on the first line. _fit should also only be receiving np.ndarray, as other types will be converted in fit. Could you also update the #1245 shapedtw doc? I forgot this applies there as well 🙂
    X : np.ndarray
        The training input samples of shape (n_cases, n_channels, n_timepoints)
    y : np.ndarray
        The training data class labels of shape (n_cases,).

sure thing!

great stuff, thank you for this.


Integration not getting loaded after upgrading to 2024.10.1

Description
After upgrading to 2024.10.1, the integration is not getting loaded.
Reproduction Steps
Just added the integration through config flow.
Expected behavior
The integration to be loaded
If applicable, add error logs.
Logger: homeassistant.setup
Source: setup.py:334
First occurred: 13:16:02 (1 occurrences)
Last logged: 13:16:02

Setup failed for custom integration 'tapo_control': Unable to import component: cannot import name 'Downloader' from 'pytapo.media_stream.downloader' (/usr/local/lib/python3.12/site-packages/pytapo/media_stream/downloader.py)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1007, in async_get_component
    comp = await self.hass.async_add_import_executor_job(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1067, in _get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/config/custom_components/tapo_control/__init__.py", line 54, in <module>
    from .utils import (
  File "/config/custom_components/tapo_control/utils.py", line 15, in <module>
    from pytapo.media_stream.downloader import Downloader
ImportError: cannot import name 'Downloader' from 'pytapo.media_stream.downloader' (/usr/local/lib/python3.12/site-packages/pytapo/media_stream/downloader.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 334, in _async_setup_component
    component = await integration.async_get_component()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1027, in async_get_component
    self._component_future.result()
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1019, in async_get_component
    comp = self._get_component()
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1067, in _get_component
    ComponentProtocol, importlib.import_module(self.pkg_path)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/config/custom_components/tapo_control/__init__.py", line 54, in <module>
    from .utils import (
  File "/config/custom_components/tapo_control/utils.py", line 15, in <module>
    from pytapo.media_stream.downloader import Downloader
ImportError: cannot import name 'Downloader' from 'pytapo.media_stream.downloader' (/usr/local/lib/python3.12/site-packages/pytapo/media_stream/downloader.py)

Device Firmware
1.3.11 Build 231115 Rel.85532n(4555)
Integration Version
5.6.1
Using stream component
Yes
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
HA OS on RPi4
Search for similar issues
Yes
Additional information
No response

Try reinstalling, I have been running 2024.10.1 since it has been released with all of my cameras with zero issues.

I have the same issue. Tried to remove the integration, restart HA, install it again and restart with no success. Error message:
Config flow could not be loaded: {"message":"Invalid handler specified"}

Could you check what is inside /usr/local/lib/python3.12/site-packages/pytapo/media_stream/downloader.py?
Can you try removing all entries that have tapo_control from your .storage/core.config_entries file (make a backup first), restart, and try adding integration as usual?
Can you try downgrading to 2024.09.x to see if the issue persists?
I wonder what is different between our envs, I use RPI 5 HA OS as well. I wonder if it has something to do with https://www.home-assistant.io/blog/2024/10/02/release-202410/#faster-upgrades-when-using-custom-integrations . I double checked developer notes in blog and there is nothing I found that could lead to this issue.

I use file explorer and I don’t have that folder where the downloader should be located. Maybe there are limitations in the file explorer addon. Anyway, I downgraded to Core 2024.10 from 2024.10.1 and now it seems to be working again. So it should not have anything todo with 2024.10 HA version.

Closing as this seems to be a weird anomaly with environments, reinstall of intergration/core seems to solve this.

after the latest 2024.10 updates the integration no longer works
with the following error
homeassistant.exceptions.DependencyError: Could not setup dependencies: Incorrect pytapo version installed: 3.3.30. Required: 3.3.32. 2024-10-30 21:13:10.128 ERROR (MainThread) [homeassistant.components.homekit] HomeKit Tapo Device cannot startup: entity not available: {'include_entities': ['camera.tapo_c200_f2f7_hd_stream'], 'exclude_domains': [], 'include_domains': [], 'exclude_entities': [], 'include_entity_globs': [], 'exclude_entity_globs': []} 2024-10-30 21:13:41.358 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry <IP_ADDRESS> for tapo_control Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup     result = await component.async_setup_entry(hass, self)              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/tapo_control/__init__.py", line 325, in async_setup_entry     raise DependencyError( homeassistant.exceptions.DependencyError: Could not setup dependencies: Incorrect pytapo version installed: 3.3.30. Required: 3.3.32. 2024-10-30 21:13:55.206 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry <IP_ADDRESS> for tapo_control Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup     result = await component.async_setup_entry(hass, self)

@Gjonni This works as expected. This is a check for users with nonstandard unrecommended HA setup, where HA is not managing dependencies. You will need to install pytapo 3.3.32.

Hi, can you explain better?
I have used HA on k3s and it has always worked correctly.
Also I already have pytapo installed in the container
Successfully installed pytapo-3.3.32 rtp-0.0.4

I have the same issue with the pytapo version not being 3.3.32. I'm simply using the offical HA image with version "2024.10.4".
As far as I see there is nothing custom on my setup. I already tried uninstalling and purging everything related to the integration, but after installing the latest version and restarting, I see the same error again.
homeassistant.exceptions.DependencyError: Could not setup dependencies: Incorrect pytapo version installed: 3.3.30. Required: 3.3.32.
@Gjonni were you able to solve it by now?

no he was wrong

I have the same issue with the pytapo version not being 3.3.32. I'm simply using the offical HA image with version "2024.10.4".
As far as I see there is nothing custom on my setup. I already tried uninstalling and purging everything related to the integration, but after installing the latest version and restarting, I see the same error again.
homeassistant.exceptions.DependencyError: Could not setup dependencies: Incorrect pytapo version installed: 3.3.30. Required: 3.3.32.
@Gjonni were you able to solve it by now?

no he was wrong

You have invalid pytapo installed. The version is set inside pytapo and integration requires 3.3.32, this is done automatically on normal HA installations methods. If there is wrong version installed, instead of using the (potentionally) incompatible old version resulting in weird issues, there is this check instead.
There is absolutely no way how you can have 3.3.32 and this error at the same time. You simply need to ensure that correct pytapo version is installed - in this case 3.3.32 if HA does not install it for you as it usually does.

I understand, but I have never installed anything, it is the official image of HA, stable version.

You will need to debug it to find out why this happens, kubernetes is an advanced installation method and can result in issues like these if not properly configured.
You might want to go into the docker container and install the proper version there manually.

for everyone's benefit, I rolled back the integration to version 5.6.1 and, without doing anything else, it was working properly again.
At the moment I will stay on version 5.6.1 to be able to use the device, hoping that the BUG will be resolved as soon as possible.
Thank you

As described previously, this is not a bug and there is nothing to resolve here. The environment where you are running it needs to be fixed.
5.6.1 you rolled back to uses pytapo 3.3.30 which your environment currently has installed where as the newest uses 3.3.32.
I recommend either learning a bit about kubernetes/docker and how to install packages via pip there, or migrating to something simpler like HA OS that manages depedencies for you automatically.

:-) I don't agree with you.
I know kubernetes very well and have already tried to update the package inside the container or image.
But I repeat, the image is the official one ghcr.io/home-assistant/home-assistant:stable.
In any case, thank you for wasting your time

Pypi packages have absolutely nothing to do with docker file, or image you are using.

You did not post steps on what you did inside container
You did not post any debugging steps you tried to do to debug the issue in the environment
You lack knowledge on what pypi is at all and instead of asking, you say you know it all.

In any case, thank you for wasting your time

And now you are blocked because of the entitlement and negativity.

Pypi packages have absolutely nothing to do with docker file, or image you are using.

You did not post steps on what you did inside container
You did not post any debugging steps you tried to do to debug the issue in the environment
You lack knowledge on what pypi is at all and instead of asking, you say you know it all.

In any case, thank you for wasting your time

You are welcomed. Next time, try posting debugging steps and asking for help instead of being entitled and ignorant on OSS project.

:-) I don't agree with you. I know kubernetes very well and

That's great. I am sure someone with your skills will have no issues figuring this out and fixing their environment on their own.

have already tried to update the package inside the container or image.

If a package was updated correctly, it would not show the old version and this error would not happen.

I don't agree with rewriting the dockerfile of an official image.

There is no need, HA integration dependencies have absolutely nothing to do with dockerfile, but I am sure you know that.

In any case, thank you for wasting your time

User @Gjonni has been blocked. For anyone else experiencing this issue, message me at<EMAIL_ADDRESS>and we can have a quick look and I can help you fix the environment on a call. In case this is a HA (not integration) bug we can open a bug report as well - I doubt that though because of number of users of the integration and lack of any bug reports so far.

@JurajNyiri as said before, I'm facing the same problem as @Gjonni and I'm not sure what you mean by "installing it ourself", I never installed any python dependency myself into the image/container. So it either comes with the image or it is installed at runtime by the integration. That's what confuses me about this issue.
Thank you for your offer, that is really appreciated! I'll write you a mail as soon as I find time to schedule a call. For now I just stick with the version that runs on 3.3.30, I'm fine with that.

Integration defines dependencies in manifest file - https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/blob/main/custom_components/tapo_control/manifest.json#L11 .
This is correctly set in both versions. HA is responsible for installing this dependency, before starting the integration. If that does not happen it is either a HA bug or an environment issue (resulting in HA not being able to install dependencies for some reason). That's what we will need to figure out.

I also run home assistant in a kubernetes cluster and had this issue now.
A quite similar problem happened a few releases ago, probably almost a year, can't remember exactly how i could solve it then.
This time it worked by removing the old pytapo and pytapo-3.3.30.dist-info directories in deps/lib/python3.12/site-packages.
and copy the the directories from deps into deps/lib/python3.12/site-packages.

Possibly related to https://github.com/home-assistant/core/issues/127966 ?

I ran into the Incorrect pytapo version installed: 3.3.30. Required: 3.3.32 error as well, even though pytapo was at correctly upgraded to 3.3.32.
Turned out that in my case the issue was a pytapo in version 3.3.30 lingering around in deps/lib/python3.12/site-packages within my HASS config directory which seems to end up in the import path and shadowed the desired version. I assume it was put there by an older version of home assistant and never got cleaned up.
I resolved the issue by removing the following two directories before triggering the upgrade from 3.6.1 to 3.8.1:
deps/lib/python3.12/site-packages/pytapo/
deps/lib/python3.12/site-packages/pytapo-3.3.30.dist-info/

Hope this helps.

Thanks for your update @martinohmann, I played around with it as well and installed the new version manually with and without having the old one, also installing it in the local python paths and the homeassistant config/deps path.
The integration still complains about the wrong version... I think I have something wrong with my setup, but currently not sure what.
@JurajNyiri I'll probably contact you next week, if your offer still stands. :)


Update the Erase Color icon.

Add the red cross over the color symbol.

The old icon is good enough... Nothing had been done...


Expand use of Sensitive to match node tokens

Fixes #51

@rwaffen Had an old Gemfile.lock on my laptop, so the reference update went in the wrong direction...


opsdroid: init at 0.22.0 + dependencies

Motivation for this change
Package opsdroid.
Based on staging because it depends on python.pkgs.Babel upgrade.
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)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 122364 at 7374ce00 run on x86_64-linux 1

1 package failed to build:

python39Packages.udatetime

7 packages skipped due to time constraints:

opsdroid
python38Packages.ibm-cloud-sdk-core
python38Packages.ibm-watson
python38Packages.pycron
python39Packages.ibm-cloud-sdk-core
python39Packages.ibm-watson
python39Packages.pycron

19 packages built successfully:

python38Packages.delorean
python38Packages.get-video-properties
python38Packages.matrix-api-async
python38Packages.mattermostdriver
python38Packages.mockupdb
python38Packages.motor
python38Packages.opsdroid_get_image_size
python38Packages.puremagic
python38Packages.udatetime
python38Packages.watchgod
python39Packages.delorean
python39Packages.get-video-properties
python39Packages.matrix-api-async
python39Packages.mattermostdriver
python39Packages.mockupdb
python39Packages.motor
python39Packages.opsdroid_get_image_size
python39Packages.puremagic
python39Packages.watchgod

14 suggestions:

warning: no-uri-literals
URI literals are deprecated.
Near pkgs/applications/networking/opsdroid/default.nix:31:16:
   |
31 |     homepage = https://opsdroid.dev/;
   |                ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/applications/networking/opsdroid/default.nix:30:0:
   |
30 |     description = "An open source chat-ops bot framework";
   | ^

warning: unused-argument
Unused argument: stdenv.
Near pkgs/development/python-modules/delorean/default.nix:1:3:
  |
1 | { stdenv
  |   ^

warning: unused-argument
Unused argument: isPy3k.
Near pkgs/development/python-modules/matrix-api-async/default.nix:1:39:
  |
1 | { lib, buildPythonPackage, fetchPypi, isPy3k
  |                                       ^

warning: unused-argument
Unused argument: stdenv.
Near pkgs/applications/networking/opsdroid/default.nix:1:3:
  |
1 | { stdenv, lib, fetchFromGitHub, fetchpatch, python3Packages }:
  |   ^

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/applications/networking/opsdroid/default.nix:1:33:
  |
1 | { stdenv, lib, fetchFromGitHub, fetchpatch, python3Packages }:
  |                                 ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/watchgod/default.nix:19:0:
   |
19 |     description = "Simple, modern file watching and code reload in python";
   | ^

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/networking/opsdroid/default.nix:33:5:
   |
33 |     license = licenses.gpl3;
   |     ^

warning: python-explicit-check-phase
Consider using pytestCheckHook in checkInputs rather than checkPhase = "pytest";.
Near pkgs/development/python-modules/ibm-watson/default.nix:47:3:
   |
47 |   checkPhase = ''
   |   ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/motor/default.nix:23:0:
   |
23 |     description = "Non-blocking MongoDB driver for Tornado or asyncio";
   | ^

warning: no-uri-literals
URI literals are deprecated.
Near pkgs/development/python-modules/puremagic/default.nix:26:16:
   |
26 |     homepage = https://github.com/cdgriffith/puremagic;
   |                ^

warning: no-uri-literals
URI literals are deprecated.
Near pkgs/development/python-modules/opsdroid_get_image_size/default.nix:21:16:
   |
21 |     homepage = https://github.com/opsdroid/image_size;
   |                ^

warning: no-uri-literals
URI literals are deprecated.
Near pkgs/development/python-modules/pycron/default.nix:27:16:
   |
27 |     homepage = https://github.com/kipe/pycron;
   |                ^

warning: unused-argument
Unused argument: stdenv.
Near pkgs/development/python-modules/udatetime/default.nix:1:3:
  |
1 | { stdenv
  |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


zib-AdvanceDirective

Hola! Zouden jullie deze willen reviewen?
Ik heb nog één error, maar dat is geloof ik een fout in de FHIR spec? https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Consent.2Escope.3A.20diff.20in.20codes.20shown.20on.20FHIR.20vs.20Tx.20server

Nog een link toegevoegd voor de nu bekende validatie error, kan deze dan al wel naar main?

The missing "adr" in http://terminology.hl7.org/CodeSystem/consentscope keeps generating validation problems, not only in the profiles but also in the examples. I think we should think a bit harder how to deal with this before merging this to main.
At the moment I see two options:

Add the corrected CodeSystem to our package. This would mean we "publish" something that we don't own but we also know that this is a very special case where the official source is broken.
Wait for #178 to be solved to properly handle these kind of errors.

Manually merged


[FEATURE] Phase out PowerMock usage

Is your feature request related to a problem?
PowerMock is unsupported
What solution would you like?
Phase out PowerMock usage since it is unsupported for years and is not working with latest JDKs
What alternatives have you considered?
N/A
Do you have any additional context?
See please https://github.com/opensearch-project/OpenSearch/issues/10334

Catch All Triage - 1 2 3 4 5


hide delete button when viewing a non-HEAD

Closes #1622

Thanks for the quick fix @johnnyaug ! And many thanks and apologies to @shamikakumar who implemented and completed it months ago (before it was reverted accidentally).


update more places with version to 0.8

@martinwicke have we already generated new documentation?

Working on that


Fix ''use strict' is unnecessary inside of modules.' issue in config\webpack.config.prod.js

CodeFactor found an issue: 'use strict' is unnecessary inside of modules.
It's currently on:
config\webpack.config.prod.js:1

Fix


No way to turn off - -> _ conversion for flag args

I defined an argument to parse like so:
    private static final String GOV_CONSTANTS_FILEPATH_ARG = "gov-constants";

        ArgumentParser parser = ArgumentParsers.newFor("Financial Predictor").build()
                .defaultHelp(true)
                .description("A financial modelling CLI");
        parser.addArgument("--" + GOV_CONSTANTS_FILEPATH_ARG)
                .required(true)
                .help("YAML file of gov constants per year");

but I was very confused why the following was showing a null value:
        String govConstantsFilepath = parsedArgs.getString(GOV_CONSTANTS_FILEPATH_ARG);
        LOG.debug("Gov constants filepath: {}", govConstantsFilepath);

When I printed the Namespace object, turns out argparse4j is changing the case of the output:
Namespace: Namespace(gov_constants=gov-constants.yml)

This was very unexpected, and only after some digging did I find the noDestConversionForPositionalArgs flag on the builder. However, even with this flag to true, my --gov-constants flag arg gets registered in the Namespace as gov_constants.
It seems likely most people would reuse a single constant for both defining the argument and retrieving the arg from the namespace, so I'm curious what the rationale is for doing the conversion?

The flag noDestConversionForPositionalArgs only applies to positional arguments as is implied by the name. As your argument has a name that starts with a prefix character (assuming you are using the default of a hyphen (-)), it is not a positional argument, so the argument name always gets converted.
I understand it is a bit strange to have names that are different from the argument names for the the keys in the resulting namespace. There are 2 reasons for this:

Emulating the behavior of argparse of Python, which does this so keys are valid attribute names: https://docs.python.org/3/library/argparse.html#dest
Ensuring the names are valid Java identifiers, so they can also be used to set the arguments on an object using reflection.

What would you prefer?

A new flag on the configuration that disables conversion of - to _ completely. Setting this flag will also prevent use of the methods that use reflection to fill a user data object.
Extra methods on Namespace that allow retrieving the the values by argument name (without the prefix). For example: String getStringByArgumentName(String).

The second option has the lowest impact, so less chance of introducing backwards incompatibilities or bugs.

Hey @jstuyts , thanks for the explanation - makes sense! Two questions:

Re. option #1, what would the methods that use reflection be? Are there any in argparse4j itself, or just for things like Jackson and so on?
Re. option number three - would this save both the unprocessed version (e.g. some-arg) as well as the processed version, so you can do both?

@mieubrisse

Option 1: Reflection is used when a user data object is passed when passing arguments. For example: parseArgs(String[], Object)
Option 3: Yes, it would save both some-arg and some_arg in the namespace. The new flag would enable this for parseArgs methods that return a Namespace and that accept a Map. I could make it an enumeration so you can choose: underscores (default), argument names, or both.

Thanks for clarifying @jstuyts ! With that in mind, I'd also agree that the third option would be best - I don't iterate over the Namespace, so flipping on the flag would allow me to use the same enum everywhere.

Sorry that it took me a long time to get started. I did end up with a nice naked yak though.
I have added an option to include the names of arguments as keys in the result. This works for positional arguments and named arguments with 1 or 2 dashes as the prefix. It is tested for the main parser, and I will add tests for a sub parser later.
Can you try it out? If you find any issues, let me know, and I will fix them.

Haha no worries, I understand how it can go with life getting in the way! Do I just need to upgrade to the latest release to start using this?

There is no release yet. You will have to build it yourself, or you can download it here: https://1drv.ms/u/s!Ag13WlvRSi9Ytbt2RhRrSpA0ABOfPQ?e=m2uqDA

@mieubrisse Have you been able to test the changes? I found 1 issue that might affect you after I sent you the build. For named arguments, the flag used for the name in the result could differ from the flag used for dest. This has been corrected in: https://github.com/argparse4j/argparse4j/commit/221a2fb34c3cba77aa83458de4736d1c1dab4568
The artifacts in the link above have been updated.
If it is working for you, I will merge this.


Adds API for account/settings

I recently find that there's no account setting API implements in tweepy.
Twitter is trying to add more options in account setting so we should prepare for that changes.

Looks good to me. Thanks!


Does it have the function of displaying rare capture creatures?

Is those, colorful big beetles and so on are very rare creatures, usually slowly find it is easy to ignore

Nope


DismissPresentationLink stopped working

The DismissPresentationLink in the code below works fine in 1.2.0 and doesn't work in 1.2.1.
struct Issue44: View {
    var body: some View {
        ZStack {

        }
        .presentation(
            transition: .slide,
            isPresented: .constant(true)
        ) {
            DismissPresentationLink {
                Text("Close")
            }
        }
    }
}

hmm not able to reproduce.
struct Issue44: View {
    @State var isPresented = true
    var body: some View {
        ZStack {
        }
        .presentation(isPresented: $isPresented) {
            DismissPresentationLink {
                Text("Close")
            }
        }
    }
}

hmm not able to reproduce.

My bad, forget to define lumaFullScreenSheet. Updated my minimal reproducible example - it happens with .slide transition

Seeing the same with slide transitions. Here is a modified content view from the example app:
struct ContentView: View {

    @State var isStatusBarHidden: Bool = false
    @State var statusBarStyle: StatusBarStyle = .default
    @State var isHeroPresented: Bool = false
    @State var progress: CGFloat = 0

  @Environment(\.presentationCoordinator) var presentationCoordinator

    var body: some View {
        NavigationView {
            List {
              PresentationLink(transition: .slide(edge: .trailing)) {
                VStack {
                    Text("Hello, World 1.")

                    DismissPresentationLink {
                        Text("DismissPresentationLink")
                    }

                  Button(action: {
                    presentationCoordinator.dismiss()
                  }) {
                    Text("Call .dismiss")
                  }
                }
              } label: {
                  Text("Fullscreen")
              }
            }
            .navigationBarTitleDisplayMode(.inline)
            .navigationTitle("Transmission")
            .prefersStatusBarHidden(isStatusBarHidden)
            .preferredStatusBarStyle(statusBarStyle.toUIKit())
        }
        .navigationViewStyle(.stack)
    }
}

with this version, both dismiss buttons don't work, but I can use the slide gesture to dismiss the fullscreen view.

Ak than you. Patched in 1.3.0 sorry!