Can't run vector addition on Nvidia GPU

I installed hipSYCL per the documentation to support CPUs and my Nvidia GPU through the cuda-nvcxx compilation path. I successfully installed the Nvidia HPC SDK and all the other requirements. The following example script provided with hipSYCL successfully compiles using the given compilation command. However, the output of the script, the result vector, is all zeros.
syclcc -o sycl_test.o sycl_test.cpp -03 --hipsycl-targets="cuda-nvcxx"
#include <cassert>
#include <iostream>
#include <CL/sycl.hpp>

using data_type = float;

std::vector<data_type> add(cl::sycl::queue& q,
                           const std::vector<data_type>& a,
                           const std::vector<data_type>& b)
{
  std::vector<data_type> c(a.size());

  assert(a.size() == b.size());
  cl::sycl::range<1> work_items{a.size()};

  {
    cl::sycl::buffer<data_type> buff_a(a.data(), a.size());
    cl::sycl::buffer<data_type> buff_b(b.data(), b.size());
    cl::sycl::buffer<data_type> buff_c(c.data(), c.size());

    q.submit([&](cl::sycl::handler& cgh){
      auto access_a = buff_a.get_access<cl::sycl::access::mode::read>(cgh);
      auto access_b = buff_b.get_access<cl::sycl::access::mode::read>(cgh);
      auto access_c = buff_c.get_access<cl::sycl::access::mode::write>(cgh);

      cgh.parallel_for<class vector_add>(work_items,
                                         [=] (cl::sycl::id<1> tid) {
        access_c[tid] = access_a[tid] + access_b[tid];
      });
    });
  }
  return c;
}

int main()
{
  cl::sycl::queue q;
  std::vector<data_type> a = {1.f, 2.f, 3.f, 4.f, 5.f};
  std::vector<data_type> b = {-1.f, 2.f, -3.f, 4.f, -5.f};
  auto result = add(q, a, b);

  std::cout << "Result: " << std::endl;
  for(const auto x: result)
    std::cout << x << std::endl;
}

One other detail, running on Nvidia Quadro 4000.

Please don't call a C++ program a script ;)

Can you please provide the output of your program when setting the environment variable HIPSYCL_DEBUG_LEVEL=3?
nvc++ is not a particularly reliably compiler, and it occasionally miscompiles complex code. In SYCL the vector types, such as float4, are very complex. What happens if you run the example code from here: https://github.com/OpenSYCL/OpenSYCL/blob/develop/doc/examples.md ? This code does not use vector types.
Which nvc++ version is this?

My bad, script slipped out of my mouth. I did mean program :)
nvc++ version:
nvc++ 23.5-0 64-bit target on x86-64 Linux -tp skylake-avx512
NVIDIA Compilers and Tools
Copyright (c) 2022, NVIDIA CORPORATION & AFFILIATES.  All rights reserved.

**Output after running attached example code: **
Result:
0
0
0
0

**Output of CUDA-memcheck: **
========= CUDA-MEMCHECK
========= This tool is deprecated and will be removed in a future release of the CUDA toolkit
========= Please use the compute-sanitizer tool as a drop-in replacement
[hipSYCL Info] backend_loader: Searching path for backend libs: '"/usr/local/bin/../lib/hipSYCL"'
[hipSYCL Info] backend_loader: Successfully opened plugin: "/usr/local/bin/../lib/hipSYCL/librt-backend-omp.so" for backend 'omp'
[hipSYCL Info] backend_loader: Successfully opened plugin: "/usr/local/bin/../lib/hipSYCL/librt-backend-cuda.so" for backend 'cuda'
[hipSYCL Info] Registering backend: 'omp'...
[hipSYCL Info] multi_queue_executor: Spawned for backend OpenMP with configuration:
[hipSYCL Info]   device 0:
[hipSYCL Info]     memcpy lane: 0
[hipSYCL Info]     kernel lane: 1
[hipSYCL Info] Registering backend: 'cuda'...
[hipSYCL Info] multi_queue_executor: Spawned for backend CUDA with configuration:
[hipSYCL Info]   device 0:
[hipSYCL Info]     memcpy lane: 0
[hipSYCL Info]     memcpy lane: 1
[hipSYCL Info]     kernel lane: 2
[hipSYCL Info]     kernel lane: 3
[hipSYCL Info] Discovered devices from backend 'OpenMP':
[hipSYCL Info]   device 0:
[hipSYCL Info]     vendor: the hipSYCL project
[hipSYCL Info]     name: hipSYCL OpenMP host device
[hipSYCL Info] Discovered devices from backend 'CUDA':
[hipSYCL Info]   device 0:
[hipSYCL Info]     vendor: NVIDIA
[hipSYCL Info]     name: Quadro RTX 4000
[hipSYCL Info] dag_manager: DAG manager is alive!
[hipSYCL Info] runtime: ******* rt launch initiated ********
[hipSYCL Info] queue: Constructed queue with node group id 1
Running on Quadro RTX 4000
[hipSYCL Info] data_region: constructed with page table dimensions 1 1 1
[hipSYCL Info] data_region: constructed with page table dimensions 1 1 1
[hipSYCL Info] data_region: constructed with page table dimensions 1 1 1
[hipSYCL Info] dag_manager: Checking DAG flush opportunity...
[hipSYCL Info] buffer_impl::~buffer_impl: Preparing submission of writeback...
[hipSYCL Info] dag_manager: Checking DAG flush opportunity...
[hipSYCL Info] buffer_impl::~buffer_impl: Waiting for operations to complete...
[hipSYCL Info] buffer_impl::~buffer_impl: dag node is registered as user but not marked as submitted, performing emergency DAG flush.
[hipSYCL Info] dag_manager: Submitting asynchronous flush...
[hipSYCL Info] dag_builder: DAG contains operations:
[hipSYCL Info] 0. kernel: ZZ4mainENKUlRN7hipsycl4sycl7handlerEE_clES2_EUlvE_
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16 @node 0x2571a00
[hipSYCL Info]     --> requires node @0x2571430 MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info]     --> requires node @0x2571570 MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info]     --> requires node @0x25716e0 MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info] 1. MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 @node 0x2571d40
[hipSYCL Info]     --> requires node @0x2571a00 kernel: ZZ4mainENKUlRN7hipsycl4sycl7handlerEE_clES2_EUlvE_
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info] 2. MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16 @node 0x2571430
[hipSYCL Info] 3. MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16 @node 0x2571570
[hipSYCL Info] 4. MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16 @node 0x25716e0
[hipSYCL Info] dag_manager: waiting for async worker...
[hipSYCL Info] dag_manager [async]: Flushing!
[hipSYCL Info] dag_manager [async]: Releasing dead users of data region 0x2570de0
[hipSYCL Info] dag_manager [async]: Releasing dead users of data region 0x2570fb0
[hipSYCL Info] dag_manager [async]: Releasing dead users of data region 0x25711c0
[hipSYCL Info] dag_manager [async]: Submitting node to scheduler!
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16 to 0x7f9a27a00000
[hipSYCL Info] multi_queue_executor: Processing node 0x2571430 with 0 non-virtual requirement(s) and 0 direct requirement(s).
[hipSYCL Info] multi_queue_executor: Dispatching to lane 0: Memcpy: CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] inorder_executor: Processing node 0x2571430 with 0 non-virtual requirement(s) and 0 direct requirement(s).
[hipSYCL Info] inorder_executor: Dispatching to lane 0x1d6ef70: Memcpy: CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16 to 0x7f9a27a00200
[hipSYCL Info] multi_queue_executor: Processing node 0x2571570 with 0 non-virtual requirement(s) and 0 direct requirement(s).
[hipSYCL Info] multi_queue_executor: Dispatching to lane 1: Memcpy: CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] inorder_executor: Processing node 0x2571570 with 0 non-virtual requirement(s) and 0 direct requirement(s).
[hipSYCL Info] inorder_executor: Dispatching to lane 0x2253190: Memcpy: CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16 to 0x7f9a27a00400
[hipSYCL Info] multi_queue_executor: Processing node 0x2571a00 with 2 non-virtual requirement(s) and 3 direct requirement(s).
[hipSYCL Info] multi_queue_executor: Dispatching to lane 2: kernel: ZZ4mainENKUlRN7hipsycl4sycl7handlerEE_clES2_EUlvE_
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info] inorder_executor: Processing node 0x2571a00 with 2 non-virtual requirement(s) and 3 direct requirement(s).
[hipSYCL Info]  --> Synchronizes with other queue for node: 0x2571430
[hipSYCL Info]  --> Synchronizes with other queue for node: 0x2571570
[hipSYCL Info] inorder_executor: Dispatching to lane 0x1fb0860: kernel: ZZ4mainENKUlRN7hipsycl4sycl7handlerEE_clES2_EUlvE_
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info] buffer_memory_requirement: Attempting to initialize embedded pointers for requirement 0x2571380
[hipSYCL Info] Identified embedded pointer with uid<PHONE_NUMBER>8628935550-4185990782115063571 in kernel blob, setting to 0x7f9a27a00000
[hipSYCL Info] buffer_memory_requirement: Attempting to initialize embedded pointers for requirement 0x25714c0
[hipSYCL Info] Identified embedded pointer with uid<PHONE_NUMBER>131339750-17804747412406211347 in kernel blob, setting to 0x7f9a27a00200
[hipSYCL Info] buffer_memory_requirement: Attempting to initialize embedded pointers for requirement 0x2571630
[hipSYCL Info] Identified embedded pointer with uid<PHONE_NUMBER>68584156-5194728932347681811 in kernel blob, setting to 0x7f9a27a00400
[hipSYCL Info] dag_manager [async]: Submitting node to scheduler!
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 to 0x7ffd2aaf6010
[hipSYCL Info] multi_queue_executor: Processing node 0x2571d40 with 1 non-virtual requirement(s) and 1 direct requirement(s).
[hipSYCL Info] multi_queue_executor: Dispatching to lane 0: Memcpy: CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] inorder_executor: Processing node 0x2571d40 with 1 non-virtual requirement(s) and 1 direct requirement(s).
[hipSYCL Info]  --> Synchronizes with other queue for node: 0x2571a00
[hipSYCL Info] inorder_executor: Dispatching to lane 0x1d6ef70: Memcpy: CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] dag_manager [async]: DAG flush complete.
[hipSYCL Info] buffer_impl::~buffer_impl: Preparing submission of writeback...
[hipSYCL Info] dag_manager: Checking DAG flush opportunity...
[hipSYCL Info] buffer_impl::~buffer_impl: Waiting for operations to complete...
[hipSYCL Info] buffer_impl::~buffer_impl: dag node is registered as user but not marked as submitted, performing emergency DAG flush.
[hipSYCL Info] dag_manager: Submitting asynchronous flush...
[hipSYCL Info] dag_builder: DAG contains operations:
[hipSYCL Info] 0. MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 @node 0x2571ec0
[hipSYCL Info] dag_manager: waiting for async worker...
[hipSYCL Info] data_region::~data_region: Freeing allocation 0x7f9a27a00400
[hipSYCL Info] dag_manager [async]: Flushing!
[hipSYCL Info] dag_manager [async]: Submitting node to scheduler!
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 to 0x7ffd2aaf6020
[hipSYCL Info] dag_manager [async]: DAG flush complete.
[hipSYCL Info] buffer_impl::~buffer_impl: Preparing submission of writeback...
[hipSYCL Info] dag_manager: Checking DAG flush opportunity...
[hipSYCL Info] buffer_impl::~buffer_impl: Waiting for operations to complete...
[hipSYCL Info] buffer_impl::~buffer_impl: dag node is registered as user but not marked as submitted, performing emergency DAG flush.
[hipSYCL Info] dag_manager: Submitting asynchronous flush...
[hipSYCL Info] dag_builder: DAG contains operations:
[hipSYCL Info] 0. MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 @node 0x2571d40
[hipSYCL Info] dag_manager: waiting for async worker...
[hipSYCL Info] data_region::~data_region: Freeing allocation 0x7f9a27a00200
[hipSYCL Info] dag_manager [async]: Flushing!
[hipSYCL Info] dag_manager [async]: Submitting node to scheduler!
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 to 0x7ffd2aaf6030
[hipSYCL Info] dag_manager [async]: DAG flush complete.
  A { 1, 2, 3, 4 }
+ B { 4, 3, 2, 1 }
------------------
= C { 0, 0, 0, 0 }
[hipSYCL Info] runtime: ******* rt shutdown ********
[hipSYCL Info] dag_manager: Waiting for async worker...
[hipSYCL Info] dag_manager: Submitting asynchronous flush...
[hipSYCL Info] dag_manager: Nothing to do
[hipSYCL Info] dag_manager: waiting for async worker...
[hipSYCL Info] dag_manager: Shutdown.
[hipSYCL Info] data_region::~data_region: Freeing allocation 0x7f9a27a00000
========= ERROR SUMMARY: 0 errors

**Output of running previous program with higher debug level: **
[hipSYCL Info] backend_loader: Searching path for backend libs: '"/usr/local/bin/../lib/hipSYCL"'
[hipSYCL Info] backend_loader: Successfully opened plugin: "/usr/local/bin/../lib/hipSYCL/librt-backend-omp.so" for backend 'omp'
[hipSYCL Info] backend_loader: Successfully opened plugin: "/usr/local/bin/../lib/hipSYCL/librt-backend-cuda.so" for backend 'cuda'
[hipSYCL Info] Registering backend: 'omp'...
[hipSYCL Info] multi_queue_executor: Spawned for backend OpenMP with configuration:
[hipSYCL Info]   device 0:
[hipSYCL Info]     memcpy lane: 0
[hipSYCL Info]     kernel lane: 1
[hipSYCL Info] Registering backend: 'cuda'...
[hipSYCL Info] multi_queue_executor: Spawned for backend CUDA with configuration:
[hipSYCL Info]   device 0:
[hipSYCL Info]     memcpy lane: 0
[hipSYCL Info]     memcpy lane: 1
[hipSYCL Info]     kernel lane: 2
[hipSYCL Info]     kernel lane: 3
[hipSYCL Info] Discovered devices from backend 'OpenMP':
[hipSYCL Info]   device 0:
[hipSYCL Info]     vendor: the hipSYCL project
[hipSYCL Info]     name: hipSYCL OpenMP host device
[hipSYCL Info] Discovered devices from backend 'CUDA':
[hipSYCL Info]   device 0:
[hipSYCL Info]     vendor: NVIDIA
[hipSYCL Info]     name: Quadro RTX 4000
[hipSYCL Info] dag_manager: DAG manager is alive!
[hipSYCL Info] runtime: ******* rt launch initiated ********
[hipSYCL Info] queue: Constructed queue with node group id 1
Running on Quadro RTX 4000
[hipSYCL Info] data_region: constructed with page table dimensions 1 1 1
[hipSYCL Info] data_region: constructed with page table dimensions 1 1 1
[hipSYCL Info] data_region: constructed with page table dimensions 1 1 1
[hipSYCL Info] dag_manager: Checking DAG flush opportunity...
[hipSYCL Info] buffer_impl::~buffer_impl: Preparing submission of writeback...
[hipSYCL Info] dag_manager: Checking DAG flush opportunity...
[hipSYCL Info] buffer_impl::~buffer_impl: Waiting for operations to complete...
[hipSYCL Info] buffer_impl::~buffer_impl: dag node is registered as user but not marked as submitted, performing emergency DAG flush.
[hipSYCL Info] dag_manager: Submitting asynchronous flush...
[hipSYCL Info] dag_builder: DAG contains operations:
[hipSYCL Info] 0. kernel: ZZ4mainENKUlRN7hipsycl4sycl7handlerEE_clES2_EUlvE_
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16 @node 0x17d78a0
[hipSYCL Info]     --> requires node @0x17d72d0 MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info]     --> requires node @0x17d7410 MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info]     --> requires node @0x17d7580 MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info] 1. MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 @node 0x17d7be0
[hipSYCL Info]     --> requires node @0x17d78a0 kernel: ZZ4mainENKUlRN7hipsycl4sycl7handlerEE_clES2_EUlvE_
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info] 2. MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16 @node 0x17d72d0
[hipSYCL Info] 3. MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16 @node 0x17d7410
[hipSYCL Info] 4. MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16 @node 0x17d7580
[hipSYCL Info] dag_manager: waiting for async worker...
[hipSYCL Info] dag_manager [async]: Flushing!
[hipSYCL Info] dag_manager [async]: Releasing dead users of data region 0x17d6c80
[hipSYCL Info] dag_manager [async]: Releasing dead users of data region 0x17d6e50
[hipSYCL Info] dag_manager [async]: Releasing dead users of data region 0x17d7060
[hipSYCL Info] dag_manager [async]: Submitting node to scheduler!
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16 to 0x7f39b7a00000
[hipSYCL Info] multi_queue_executor: Processing node 0x17d72d0 with 0 non-virtual requirement(s) and 0 direct requirement(s).
[hipSYCL Info] multi_queue_executor: Dispatching to lane 0: Memcpy: CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] inorder_executor: Processing node 0x17d72d0 with 0 non-virtual requirement(s) and 0 direct requirement(s).
[hipSYCL Info] inorder_executor: Dispatching to lane 0xfd4f90: Memcpy: CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16 to 0x7f39b7a00200
[hipSYCL Info] multi_queue_executor: Processing node 0x17d7410 with 0 non-virtual requirement(s) and 0 direct requirement(s).
[hipSYCL Info] multi_queue_executor: Dispatching to lane 1: Memcpy: CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] inorder_executor: Processing node 0x17d7410 with 0 non-virtual requirement(s) and 0 direct requirement(s).
[hipSYCL Info] inorder_executor: Dispatching to lane 0x14b91c0: Memcpy: CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16 to 0x7f39b7a00400
[hipSYCL Info] multi_queue_executor: Processing node 0x17d78a0 with 2 non-virtual requirement(s) and 3 direct requirement(s).
[hipSYCL Info] multi_queue_executor: Dispatching to lane 2: kernel: ZZ4mainENKUlRN7hipsycl4sycl7handlerEE_clES2_EUlvE_
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info] inorder_executor: Processing node 0x17d78a0 with 2 non-virtual requirement(s) and 3 direct requirement(s).
[hipSYCL Info]  --> Synchronizes with other queue for node: 0x17d72d0
[hipSYCL Info]  --> Synchronizes with other queue for node: 0x17d7410
[hipSYCL Info] inorder_executor: Dispatching to lane 0x1216750: kernel: ZZ4mainENKUlRN7hipsycl4sycl7handlerEE_clES2_EUlvE_
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: R device {0, 0, 0}+{1, 1, 1} #16
   MEM_REQ: Discard W device {0, 0, 0}+{1, 1, 1} #16
[hipSYCL Info] buffer_memory_requirement: Attempting to initialize embedded pointers for requirement 0x17d7220
[hipSYCL Info] Identified embedded pointer with uid<PHONE_NUMBER>544791484-9734378245931350813 in kernel blob, setting to 0x7f39b7a00000
[hipSYCL Info] buffer_memory_requirement: Attempting to initialize embedded pointers for requirement 0x17d7360
[hipSYCL Info] Identified embedded pointer with uid<PHONE_NUMBER>96430484-8365175106401983005 in kernel blob, setting to 0x7f39b7a00200
[hipSYCL Info] buffer_memory_requirement: Attempting to initialize embedded pointers for requirement 0x17d74d0
[hipSYCL Info] Identified embedded pointer with uid<PHONE_NUMBER>757923524-4113919994189301021 in kernel blob, setting to 0x7f39b7a00400
[hipSYCL Info] dag_manager [async]: Submitting node to scheduler!
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 to 0x7ffc15982580
[hipSYCL Info] multi_queue_executor: Processing node 0x17d7be0 with 1 non-virtual requirement(s) and 1 direct requirement(s).
[hipSYCL Info] multi_queue_executor: Dispatching to lane 0: Memcpy: CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] inorder_executor: Processing node 0x17d7be0 with 1 non-virtual requirement(s) and 1 direct requirement(s).
[hipSYCL Info]  --> Synchronizes with other queue for node: 0x17d78a0
[hipSYCL Info] inorder_executor: Dispatching to lane 0xfd4f90: Memcpy: CUDA-Device0 #16 {0, 0, 0}+{1, 1, 1}-->CPU-Device0 #16 {0, 0, 0}+{1, 1, 1}{1, 1, 1}
[hipSYCL Info] dag_manager [async]: DAG flush complete.
[hipSYCL Info] buffer_impl::~buffer_impl: Preparing submission of writeback...
[hipSYCL Info] dag_manager: Checking DAG flush opportunity...
[hipSYCL Info] buffer_impl::~buffer_impl: Waiting for operations to complete...
[hipSYCL Info] buffer_impl::~buffer_impl: dag node is registered as user but not marked as submitted, performing emergency DAG flush.
[hipSYCL Info] dag_manager: Submitting asynchronous flush...
[hipSYCL Info] dag_builder: DAG contains operations:
[hipSYCL Info] 0. MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 @node 0x17d7d60
[hipSYCL Info] dag_manager: waiting for async worker...
[hipSYCL Info] data_region::~data_region: Freeing allocation 0x7f39b7a00400
[hipSYCL Info] dag_manager [async]: Flushing!
[hipSYCL Info] dag_manager [async]: Submitting node to scheduler!
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 to 0x7ffc15982590
[hipSYCL Info] dag_manager [async]: DAG flush complete.
[hipSYCL Info] buffer_impl::~buffer_impl: Preparing submission of writeback...
[hipSYCL Info] dag_manager: Checking DAG flush opportunity...
[hipSYCL Info] buffer_impl::~buffer_impl: Waiting for operations to complete...
[hipSYCL Info] buffer_impl::~buffer_impl: dag node is registered as user but not marked as submitted, performing emergency DAG flush.
[hipSYCL Info] dag_manager: Submitting asynchronous flush...
[hipSYCL Info] dag_builder: DAG contains operations:
[hipSYCL Info] 0. MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 @node 0x17d7be0
[hipSYCL Info] dag_manager: waiting for async worker...
[hipSYCL Info] data_region::~data_region: Freeing allocation 0x7f39b7a00200
[hipSYCL Info] dag_manager [async]: Flushing!
[hipSYCL Info] dag_manager [async]: Submitting node to scheduler!
[hipSYCL Info] dag_direct_scheduler: Setting device data pointer of requirement node MEM_REQ: R host_buffer {0, 0, 0}+{1, 1, 1} #16 to 0x7ffc159825a0
[hipSYCL Info] dag_manager [async]: DAG flush complete.
  A { 1, 2, 3, 4 }
+ B { 4, 3, 2, 1 }
------------------
= C { 0, 0, 0, 0 }
[hipSYCL Info] runtime: ******* rt shutdown ********
[hipSYCL Info] dag_manager: Waiting for async worker...
[hipSYCL Info] dag_manager: Submitting asynchronous flush...
[hipSYCL Info] dag_manager: Nothing to do
[hipSYCL Info] dag_manager: waiting for async worker...
[hipSYCL Info] dag_manager: Shutdown.
[hipSYCL Info] data_region::~data_region: Freeing allocation 0x7f39b7a00000


Consider increasing single_line_if_else_max_width

The default 50 column limit on single-line if-else statements feels like it creates too much whitespace for simple logic. For example:
let dest: PathBuf = {
    let grave = graveyard.join(path.strip_prefix("/").unwrap());
    if grave.exists() { rename_grave(grave) } else { grave }
};

becomes
let dest: PathBuf = {
    let grave = graveyard.join(path.strip_prefix("/").unwrap());
    if grave.exists() {
        rename_grave(grave)
    } else {
        grave
    }
};

I understand the rationale behind discouraging complex one-liners, but it seems like a length restriction just encourages shorter variable names.

Yeah, I mostly agree and also get frustrated when we don't quite hit the length limit. However, rather than just extend the limit, I'd rather do something a little smarter, like look at the expressions in the arms (I think we already require a single expression) and allow a one-liner if there is a 'small' expression, for some definition of that.

Discussed at https://github.com/rust-lang-nursery/fmt-rfcs/issues/47


XCode 12.5 logs not loading

I was able to see the logs as expected with XCode 12.3.
However, recently upgraded my XCode to version 12.5 and since then unable to see any logs with XCTestHTMLReport v2.1.

Is anyone else also facing a similar issue?

Yes me too!

Same here, but only for UI tests. The -j junit output is empty too
Unit tests work fine for html and junit for me.

yep same here

same here

same here. See XCHTML Error on Xcode 12 test result bundles
I finally solved this problem using XCTestHTMLReport 2.0.0.
And once I got xcrun: error: unable to find utility "xcresulttool", not a developer tool or in PATH.
Just execute:
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer and eventually got a right xcrun xcresulttool.

@IcyW Just switching to XCTestHTMLReport 2.0.0 solved the problem?

itching to XCTestHTMLReport 2.0.0 solved the problem?

For me, yes.

itching to XCTestHTMLReport 2.0.0 solved the problem?

For me, yes.

@IcyW do you mind sharing the binary that's working for you? Just to confirm its working for you on Xcode 12.5?

This doesn't work even with XCTestHTMLReport 2.0.0. We are using Xcode 12.5.1 and we run tests from xctesplans

I faced the same problem.
In my case the .testPlan files contained some "selectedTests" (open as source code) it create trouble to generate HTML report.
I used "skippedTests" instead of "selected tests".
It's not a perfect solution, it's a restrictive one but it's working!
I think the problem comes from XCTestKit not especially from XCTestHTMLReport

I wonder what other test reporting tools are available in the market? There are few that I found are not being maintained but nothing comes as close to this tool. This xchtml tool is really handy but sad to see that this is not being maintained.

I have merged this old fix which solved this https://github.com/TitouanVanBelle/XCTestHTMLReport/pull/201
Now we need a new release. :)
(If you need a work-around until release is done you can use the -i option which will load the contents into the HTML from the start. It will make the HTML bigger since it does not read logs on demand. It loads everything from the start.)
@TitouanVanBelle Can you release a new version please? This issue is solved and various people seems to be affected.

This issue is about tests plans logs. I got confused about normal logs. Sorry this is not fixed yet.

@anuragmaheshwari

I wonder what other test reporting tools are available in the market? There are few that I found are not being maintained but nothing comes as close to this tool. This xcTesthtml tool is really handy but sad to see that this is not being maintained.

I use xcresults to export from Xcode to Allure2 report for tvOS UITests running on CircleCi:

Confirm this issue is resolved on the latest commit in the develop branch.

@nickgarkusha

Confirm this issue is resolved on the latest commit in the develop branch. Tested on Xcode 12.5.1.

Thank you for confirming this! I think we need a release soon :)


Stage 1 breaks with ^C

Hi!
I'm trying to run the repo in google colab and getting this after
$ python launch.py --config configs/dreamcraft3d-coarse-nerf.yaml --train system.prompt_processor.prompt="$prompt" data.image_path="$image_path"
/usr/local/lib/python3.10/dist-packages/controlnet_aux/mediapipe_face/mediapipe_face_common.py:7: UserWarning: The module 'mediapipe' is not installed. The package will have limited functionality. Please install it using the command: pip install 'mediapipe'
warnings.warn(
/usr/local/lib/python3.10/dist-packages/diffusers/utils/outputs.py:63: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
torch.utils._pytree._register_pytree_node(
2024-04-24 12:55:29.148875: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-04-24 12:55:29.148928: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-04-24 12:55:29.150336: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-04-24 12:55:30.221042: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
/usr/local/lib/python3.10/dist-packages/diffusers/utils/outputs.py:63: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
torch.utils._pytree._register_pytree_node(
/usr/local/lib/python3.10/dist-packages/diffusers/utils/outputs.py:63: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
torch.utils._pytree._register_pytree_node(
Seed set to 0
[INFO] Loading Deep Floyd ...
A mixture of fp16 and non-fp16 filenames will be loaded.
Loaded fp16 filenames:
[safety_checker/model.fp16.safetensors, text_encoder/model.fp16-00001-of-00002.safetensors, unet/diffusion_pytorch_model.fp16.safetensors, text_encoder/model.fp16-00002-of-00002.safetensors]
Loaded non-fp16 filenames:
[watermarker/diffusion_pytorch_model.safetensors
If this behavior is not expected, please check your folder structure.
Loading pipeline components...:   0% 0/3 [00:00<?, ?it/s]You are using the default legacy behaviour of the <class 'transformers.models.t5.tokenization_t5.T5Tokenizer'>. This is expected, and simply means that the legacy (previous) behavior will be used so nothing changes for you. If you want to use the new behaviour, set legacy=False. This should only be set if you understand what it means, and thoroughly read the reason why this was added as explained in https://github.com/huggingface/transformers/pull/24565
Loading pipeline components...: 100% 3/3 [00:01<00:00,  2.46it/s]
[INFO] Loaded Deep Floyd!
[INFO] Loading Stable Zero123 ...
LatentDiffusion: Running in eps-prediction mode
^C
There is only empty folder with prompt@LAST

colab just doesn't have enough memory..


Fix product ratings fetching

Closes #116

Codecov Report
Base: 97.91% // Head: 97.91% // No change to project coverage :thumbsup:

Coverage data is based on head (e6292e6) compared to base (c1e3629).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #117   +/-   ##
=======================================
  Coverage   97.91%   97.91%
=======================================
  Files         171      171
  Lines        2830     2830
  Branches      147      147
=======================================
  Hits         2771     2771
  Misses         52       52
  Partials        7        7

Impacted Files
Coverage Δ

...catalog/product-ratings/product-ratings.service.ts
100.00% <ø> (ø)

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

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


envoy on arm64

any chance an arm64 build will be made available?  im looking to get envoy and istio running on an arm64 cluster.

@BitRacer do you think https://www.envoyproxy.io/docs/envoy/latest/install/building#arm64-binaries will help you?

@dio ill take a look. Im new to this part of k8s and really hoping to use my budget home microk8s cluster to envoy, istio, service mesh etc.  thanks for the lead.

I believe the docs are wrong:
Stable image is only intel: https://hub.docker.com/r/envoyproxy/envoy/tags/
Development includes arm64: https://hub.docker.com/r/envoyproxy/envoy-dev/tags/
But even the alpine development image is missing arm64 tags/manifest entries: https://hub.docker.com/r/envoyproxy/envoy-alpine-dev/tags

Hmm, I would love to see a fat released image here as well.

Is there a chance to get this re-opened since I would like such an image to be released as well.

Arm64 is already present, see https://hub.docker.com/r/envoyproxy/envoy/tags/


[Adaptive Card iOS - Table.FirstRowAsHeaders.json]: While navigating using swipe gesture Rating stars are not accessible.

Target Platforms
iOS
SDK Version
Version 1.0 (2.4.0-beta.<IP_ADDRESS>)
Application Name
Adaptive Cards
Problem Description
Test Environment:
Device: iPhone 11
iOS: 17.5.1
Application: Adaptive Cards
App Version: Version 1.0 (2.4.0-beta.<IP_ADDRESS>)
Screen Reader: Voice Over
Repro Steps:

Launch Adaptive Cards iOS application.
Home screen will appear.
Activate Voice over
Navigate to "V1.5" control and select it.
Navigate to 'Elements' control and activate it.
Navigate to 'Input.Rating.Actions.Json' and activate it.
The Card will open.
Navigate to the rating star using swipe gesture and observe the issue.

Actual Result:
While navigating to the Rating Star using the swipe gesture, Rating stars are not accessible through the swipe gesture. On performing left or right swipe, voice over focus is landing on the next control.
Observations:
Using manually tapping on the stars, user is able to select the rating stars individually.
Expected Result:
While navigating using the swipe gesture, Rating star should be individually accessible through the swipe gesture.
User Impact:
Screen Reader user will be impacted as they will not be able to access the control while navigating using the swipe gesture due to this they will not be able to provide the rating to the user.
WCAG Reference:
https://www.w3.org/TR/WCAG21/#meaningful-sequence
Have feedback to share on Bugs ? please tag bug as “A11yRCA” and add your feedback in the comment section
Screenshots
https://github.com/microsoft/AdaptiveCards-Mobile/assets/95913748/7c862920-c53c-453d-9de5-7854e32f6258
Card JSON
NA

Sample Code Language
No response
Sample Code
No response

Abhishek, Can you take a look at this rating a11y bug from rating component. Lets target the fix by EOW.

Abhishek, Can you take a look at this rating a11y bug from rating component. Lets target the fix by EOW.

Sure, checking this.


/edit-task command doesn't work

/edit-task command doesn't work,
one running that command slack throws "invalid_block" error

This has been fixed in https://github.com/SiddhiKhairee/slackpoint-v4/pull/1


implementation of calendar day and auto increment

This P.R implements basic types for list fields types.
The simplest approach (unions) has been used, and as such, when creating a field, all possible options are presented.
A cleanest but more invasive approach would be to discrimate against the type of the field. It could be implemented in the feature.

Only thing I'm going to do to this post-merge is remove the dev dependency on Keystone 4, as I don't think we need it there.


Ask if hacker is from FIB-UPC, and if so, what degree/master he/she is cursing

It's a Maria Teresa (vice-dean) request:

podríeu afegir al formulari d'inscripció que el participant indiqui si és fiber o no i, en cas afirmatiu, quina titulació està cursant (GEI, MAI, MIRI, MEI, GCED, MasterSecundaria).

fiber?

@qaisjp It's how we call people studying at FIB (Informatics Faculty of Barcelona) XD

Will take a look at how to do that. I need to do a refactor on the way of creating the forms

ah cool :D We say Infer (School of Informatics)

Once we have this as a standalone repo and use a fork for HackUPC, we may be able to do it

Would it be to complex to move this into a feature titled "Targeted Questions", allowing you to ask questions ("What degree?") based on a predicate (school=FIB-UPC)?

Currently, there's no easy way to do this. There are a few targeted questions though (Projects you have done only appear if this is not your first hackathon. The only problem is that it's quite manual. I may look to see if there's an easier way to do it.

Closed since we are not gonna implement this.


iOS: remove border from toolbar containing segment

From @drewrygh on November 20, 2015 22:51

Copied from original issue: driftyco/ionic2#614

From @adamdbradley on December 7, 2015 22:30
Note: See if we can cleanly select and place an ion-toolbar inside of an ion-navbar

From @brandyscarney on November 20, 2015 23:31
So this is tricky because on iOS there is no border between the title and the segment in the next toolbar, but we can't use the segment to select a previous sibling in order to change it. Or...we could modify it so if the user puts a segment in a navbar with a title it moves to the next line.

This will be possible with the beta 10 release. 👍


"math.randomseed() must be called in init_worker" errior when using lua_cache=off in Docker

Summary
As discussed in the gitter channel, I have been receiving this error for any requests to the adminn_api (8001) server, in Docker, using Kong 0.9.2:
"math.randomseed() must be called in init_worker"
After investigation it turned out to be related to the lua_cache directive being set to off.
A workaround for the issue is to comment out line 22 (raising the error) in the kong/core/globalpatches.lua file.
Steps To Reproduce

Using the docker-kong project, build a new image with the Dockerfile
Add the directive lua_cache=off to the kong.conf file
Link your local kong.conf to the instance's (in /etc/kong/) when running the container
Start the container and open error logs (/usr/local/kong/logs/error.log)
Attempt to load http://localhost:8001/apis
Kong responds with a 500 and the logs show the error above.

Additional Details & Logs

Kong version 0.9.2
Kong configuration has lua_cache=off
Operating System Docker / docker-kong / Centos 7

Fixed by #1717, thanks.


Suggestion: Port the Mod To Minecraft 1.18.2

That's all I wanted to suggest.

Got it. I will mention you here once I'm done :)

Done! Currently, you can download MinecraftClientGobrrr for MC 1.18.2 (and 1.20) from Github Releases page. I'll upload those to Modrinth and Curseforge a little bit later.


ff and cuda_ray flag

Nice job! But what does the flag 'ff' and 'cuda_ray' mean ?
Does ff mean an implenment of tcnn yourself ?
What about cuda_ray ? Sampling ray with CUDA ops?

@QinlongHuang Yes, these can be found in the readme.

There may be implementation differences, but the idea behind the algorithm should be the same, and the performance are similar.


TypeError: Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script.

Versions
Angular: 5.1.1
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router
... service-worker

@angular/cli: 1.6.0-rc.2
@angular/language-service: 5.0.2
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.0-rc.2
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.4.2
webpack: 3.10.0

Repro steps

When I run with "ng serve" which should be using web pack dev server in dev enviornment, it is trying to load the service worker file.  I have tried adding both pieces of code below and neither work, the only thing that works is to comment this out and not run ServiceWorkerModule at all.

ServiceWorkerModule.register('/ngsw-worker.js', { enabled: environment.production }),

environment.production ? ServiceWorkerModule.register('/ngsw-worker.js') : [],

Observed behavior
ERROR Error: Uncaught (in promise): TypeError: Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script.

Mention any other details that might be useful (optional)
Package.json
{
  "name": "responder",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^5.0.0",
    "@angular/common": "^5.0.0",
    "@angular/compiler": "^5.0.0",
    "@angular/core": "^5.0.0",
    "@angular/forms": "^5.0.0",
    "@angular/http": "^5.0.0",
    "@angular/platform-browser": "^5.0.0",
    "@angular/platform-browser-dynamic": "^5.0.0",
    "@angular/router": "^5.0.0",
    "@angular/service-worker": "^5.0.0",
    "@ngrx/entity": "^4.1.1",
    "@ngrx/store": "^4.1.1",
    "@ngrx/store-devtools": "^4.1.1",
    "core-js": "^2.4.1",
    "moment": "^2.19.3",
    "rxjs": "^5.5.2",
    "zone.js": "^0.8.14"
  },
  "devDependencies": {
    "@angular/cli": "1.6.0-rc.2",
    "@angular/compiler-cli": "^5.0.0",
    "@angular/language-service": "^5.0.0",
    "@types/jasmine": "~2.5.53",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "~6.0.60",
    "codelyzer": "~3.2.0",
    "jasmine-core": "~2.6.2",
    "jasmine-spec-reporter": "~4.1.0",
    "karma": "~1.7.0",
    "karma-chrome-launcher": "~2.1.1",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "ngrx-store-freeze": "^0.2.0",
    "protractor": "~5.1.2",
    "ts-node": "~3.2.0",
    "tslint": "~5.7.0",
    "typescript": "~2.4.2"
  }
}

Ugh had production =  true in my dev enviornment.ts file.    Overlooked that!

Can this be reopened?
I've just came across this, trying to figure out WHY it isn't working.
Yes, I also have production true. But on purpose, because I want to test the service worker with ng serve --prod.
Why does fetching the service worker script give a 404, when fetching all other resources works (scripts, styles, images etc.) ?
We shouldn't have to put up yet another dev server just to test the service worker. ng serve --prod should do the trick.

@MrCroft I think you might want to open a new one for that is it isn't a bug.  That is the way it is by design so it will most likely be a feature request


[Feature] Add Heart Pulse loader

Description
I want to add the Heart Pulse Loader which will load the pulse in red color

Assign me this issue under GSSOC2024
Screenshots
1d91bd97-7475-4171-bc81-3ab61623ebde.webm
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

I would like to work on this issue , please assign this to me.
@SaiyamTuteja @pb0126 @Rakesh9100 @NaveenChandraAdhikari @Nemesis-AS @SplinterSword

Proceed @SaiyamTuteja


pubmed_qa checksum mismatch

Describe the bug
Loading pubmed_qa results in a mismatched checksum error.
Steps to reproduce the bug
# Sample code to reproduce the bug
import datasets
try:
    datasets.load_dataset("pubmed_qa", "pqa_labeled")
except Exception as e:
    print(e)

try:
    datasets.load_dataset("pubmed_qa", "pqa_unlabeled")
except Exception as e:
    print(e)

try:
    datasets.load_dataset("pubmed_qa", "pqa_artificial")
except Exception as e:
    print(e)

Expected results
Successful download.
Actual results
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.9/site-packages/datasets/load.py", line 1702, in load_dataset
builder_instance.download_and_prepare(
File "/usr/local/lib/python3.9/site-packages/datasets/builder.py", line 594, in download_and_prepare
self._download_and_prepare(
File "/usr/local/lib/python3.9/site-packages/datasets/builder.py", line 665, in _download_and_prepare
verify_checksums(
File "/usr/local/lib/python3.9/site-packages/datasets/utils/info_utils.py", line 40, in verify_checksums
raise NonMatchingChecksumError(error_msg + str(bad_urls))
datasets.utils.info_utils.NonMatchingChecksumError: Checksums didn't match for dataset source files:
['https://drive.google.com/uc?export=download&id=1RsGLINVce-0GsDkCLDuLZmoLuzfmoCuQ', 'https://drive.google.com/uc?export=download&id=15v1x6aQDlZymaHGP7cZJZZYFfeJt2NdS']
Environment info

datasets version: 1.18.3
Platform: macOS
Python version: 3.8.1
PyArrow version: 3.0.0

Hi @jon-tow, thanks for reporting.
This issue was already reported and its root cause is a change in the Google Drive service. See:

#3786

We have already fixed it. See:

#3787

We are planning to make a patch release today.
In the meantime, you can get this fix by installing our library from the GitHub master branch:
pip install git+https://github.com/huggingface/datasets#egg=datasets

Then, if you had previously tried to load the data and got the checksum error, you should force the redownload of the data (before the fix, you just downloaded and cached the virus scan warning page, instead of the data file):
load_dataset("...", download_mode="force_redownload")


timing_parameters cleaning mask

It appears that implicitly masking pixels for image > 0 rather than explicitly asking for a cleaning mask tends to make the user (at least me) use the function in a bad way.
Explicitly requiring a cleaning mask should make the user more aware of the need to clean the image before using the function timing_parameters.

The original reasoning was, that people pass in image[mask], geom[mask] like with the hillas calculation and that then the negative sizes should be ignored.
Maybe it's better to raise an error on negative values here.
But cleaning_mask should be optional, to enable the image[mask], geom[mask] thingy, right?

Sorry I made the changes too quickly without pytesting.


Inconsistent documentation on C# operators

The true and false  operators were added to https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/operators/index by #11860, but they are still missing on the left-side TOC of the page as well as several others.
That page is also missing the stackalloc and nameof operators.
On the other hand, https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/operator-keywords is missing default,, delegate. unchecked,  checked are mentioned at the end, but should be on the TOC.
/cc @BillWagner @pkulikov

@paulomorgado thanks for sharing your observations.
On TOC
The TOC is being shrunk with the individual operator entries made "hidden" behind the overview article entries. That is, one wouldn't see the "% operator" entry, but if one enters "%" in the textbox above the TOC, the "Arithmetic operators" entry is shown. That said, I think every operator should be "searchable" this way in the TOC. @BillWagner would it mean that keyword operators that don't end up in any overview should be listed in the operators TOC as it is? Is it acceptable to mention one article in two different TOCs?
On the list of operators
It looks that current C# operators index page intends to list all the operators. Then, it should contain both stackalloc and nameof as well.
The nameof is listed in the definition of primary expressions.
To which section should stackalloc go?

Thanks for writing this @paulomorgado I'm glad you're participating in the discussion.
There are several moving parts here. I'll notes those then address the questions.
We're looking to trip the Language Reference section of the C# Guide by relying on the Language Specification as the complete authoritative reference. See #2840 for the background discussion. we intend this to make the reference more conversational, enhancing understanding for readers.
As part of that, we're consolidating articles in groups based on common themes. Much of the task plan is in this project.  Related to this work, we're leveraging the TOC filter to find operators better. Operators are difficult to find using search engines: the search engines view those characters as punctuation and removes them. As @pkulikov states above, we're adding the operator tokens so you can type an operator in the TOC filter, and find the correct pages.
For the TOC: Yes, there will be fewer entries, because we're combining pages. We hope the TOC filter helps. We welcome any suggestions to make it easier to find.
operators: Yes, the intent is that this is complete. I've added stackalloc and new to #10741 (operators that are single pages.)

I think it's not obvious that the filter will find something that's "not there". I would expect the filter to, well, filter what's "there".


Handles exceptions raised by coroutine made in shutdown waits for

Because shutdown_waits_for creates a new task as a proxy for the coroutine, it must handle all exception types and not just CancelledErrors. If this isn't included, when an exception is raised in coro it isn't handled and an error you get this message: 'Task exception was never retrieved'.

Coverage remained the same at 98.095% when pulling 0d8e5cc2851da8ec24ed070332229ed9092b5196 on ashwini-balnaves:catch-exceptions-in-shutdown-waits-for into 52022a0b4d6ef6a6230c5d0a91a967d3a725a4ee on cjrh:master.


vue-template-compiler build failure when upgrading to Vue 2.5.16 from 2.5.13

I currently have vue specified in package.json as "vue": "^2.3.3", but the installed version is 2.5.13. When using yarn upgrade vue to upgrade from 2.5.13 to 2.5.16, the output from yarn run brunch build goes from:
18:01:27 - info: compiled 662 files into 3 files, copied 10 in 35.2 sec

to:
$ /Users/austin/dev/kinetic/lowes-loyalty-web/assets/node_modules/.bin/brunch build
18:09:36 - warn: Loading of vue-brunch failed due to

Vue packages version mismatch:

-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

Stack trace was suppressed. Run with `LOGGY_STACKS=1` to see the trace.
… noisy messages suppressed …
18:10:11 - error: Compiling of components/employee/analytics/store/StoreTable.vue failed. L1:0 Unexpected token
   > 1 | <template>
       | ^
     2 |

     3 |

     4 |

Stack trace was suppressed. Run with `LOGGY_STACKS=1` to see the trace.

I cannot figure out how to upgrade vue-template-compiler to 2.5.16 in order to fix the dependency issue here. I am not sure that I can.

I use yarn to manage my dependencies.
I am using brunch with an Elixir/Phoenix project, so it’s going to be hard to get a minimal reproduction from what I have.
I can provide some configuration files as needed, but my package.json is below as a start. I cannot provide other files, but I am happy to try any commands necessary to fix issues as required.
I have seen no difference when using @nblackburn/vue-brunch as the devDependency.

{
  "repository": {},
  "license": "MIT",
  "scripts": {
    "lint:css": "stylelint 'web/static/**/*.vue'",
    "deploy": "brunch build --production",
    "watch": "brunch watch --stdin",
    "fragments": "node priv/query_fragment_types.js"
  },
  "dependencies": {
    "apollo-cache-inmemory": "^1.1.2",
    "apollo-client": "^2.1.0",
    "apollo-link": "^1.2.0",
    "apollo-link-context": "^1.0.2",
    "apollo-link-http": "^1.3.0",
    "autoprefixer": "^8.0.0",
    "axios": "^0.18.0",
    "babel-polyfill": "^6.26.0",
    "base64url": "^2.0.0",
    "css-vars-ponyfill": "^1.1.2",
    "date-fns": "^1.29.0",
    "graphql": "^0.13.1",
    "lodash": "^4.17.4",
    "phoenix": "file:../deps/phoenix",
    "phoenix_html": "file:../deps/phoenix_html",
    "qinu": "^2.0.0",
    "qs": "^6.5.1",
    "raven-js": "^3.16.0",
    "regenerator-runtime": "^0.11.0",
    "unfetch": "^3.0.0",
    "vue": "^2.3.3",
    "vue-apollo": "^3.0.0-beta.4",
    "vue-cookie": "^1.1.4",
    "vue-password": "^1.0.0",
    "vue-router": "^3.0.0",
    "vuejs-datepicker": "^0.9.20",
    "vuelidate": "^0.6.0",
    "vuex": "^3.0.0",
    "vuex-router-sync": "^5.0.0"
  },
  "devDependencies": {
    "vue-brunch": "^2.0.1",
    "babel-brunch": "^6.0.0",
    "clean-css-brunch": "^2.0.0",
    "eslint-brunch": "^3.12.0",
    "uglify-js-brunch": "^2.0.1",
    "brunch": "^2.10.9",
    "babel-eslint": "^8.2.2",
    "babel-plugin-lodash": "^3.2.11",
    "babel-plugin-macros": "^2.1.0",
    "babel-plugin-transform-runtime": "^6.23.0",
    "babel-preset-env": "^1.5.2",
    "babel-preset-stage-3": "^6.24.1",
    "eslint-config-vue": "^2.0.2",
    "eslint-plugin-compat": "^2.0.0",
    "eslint-plugin-lodash-fp": "^2.1.3",
    "eslint-plugin-vue": "^4.0.0",
    "eslint-plugin-vuefix": "^0.2.0",
    "graphql.macro": "^1.0.2",
    "inchjs": "^0.4.1",
    "node-sass": "^4.5.3",
    "stylelint": "^9.0.0",
    "stylelint-config-recess-order": "^1.2.1",
    "stylelint-config-standard": "^18.0.0",
    "stylelint-no-unsupported-browser-features": "^2.0.0",
    "stylelint-processor-html": "^1.0.0"
  }
}

Occured me too, under somewhat different circumstances. The following may show the culprit.
yarn why vue-template-compiler
yarn why v1.5.1
[1/4] Why do we have the module "vue-template-compiler"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "vue-template-compiler"
info This module exists because it's specified in "devDependencies".
info Disk size without dependencies: "360kB"
info Disk size with unique dependencies: "500kB"
info Disk size with transitive dependencies: "500kB"
info Number of shared dependencies: 2
=> Found<EMAIL_ADDRESS>info This module exists because "laravel-mix" depends on it.
info Disk size without dependencies: "128kB"
info Disk size with unique dependencies: "268kB"
info Disk size with transitive dependencies: "268kB"
info Number of shared dependencies: 2
Done in 0.84s.

So, if some other dep is using<EMAIL_ADDRESS>you can either

upgrade the cuplrit(in my case it was laravel-mix)
downgrade vue back to 2.5.13 in your package.json followed by yarn install
add "vue-template-compiler": "^2.5.16" to your package.json followed by yarn install followed by hopefully that works

I’m pretty sure that this is a dependency specification in vue-brunch based on yarn why:
yarn why v1.5.1
[1/4] Why do we have the module "vue-template-compiler"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "vue-brunch#vueify" depends on it
   - Hoisted from "vue-brunch#vueify#vue-template-compiler"
info Disk size without dependencies: "28MB"
info Disk size with unique dependencies: "68MB"
info Disk size with transitive dependencies: "68MB"
info Number of shared dependencies: 2
Done in 1.54s.

In interpretation of npm semver convention and following the transitive dependency chain:
"vue-brunch": "^2.0.1" depending on "vueify": "^9.4.1" depending on "vue-template-compiler": "^2.0.0-alpha.8","
vue-template-compiler 2.5.16 should be compatible. Having read that vue-template-compiler is a peer dependecy of vue, i would go with
yarn add -D<EMAIL_ADDRESS>

@halostatue I just updated both to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

I have updated the lockfile which should hopefully fix some issues, let me know if that solves this issue for you.

By removing and adding again; solved my problem.
npm remove vue npm audit fix --force npm add vue --save

I’ve just gotten to try this again and it looks like either adding vue-template-compiler as a direct dependency now works. I’m not going to pretend to understand this.

I’ve just gotten to try this again and it looks like either 2.5.16 or 2.5.17 fixed the issue, but ONLY if I

It worked because I was still on Vue 2.5.13. I still get:
Vue packages version mismatch:

-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

Stack trace was suppressed. Run with `LOGGY_STACKS=1` to see the trace.
babel-preset-env: `DEBUG` option
…

And…yarn remove vue-brunch && yarn add -D vue-brunch && git checkout -- package.json works. The checkout is required because of the conflict between brunch (order-of-dev-dependency-keys-matters) and yarn (let's-sort-the-dependency-keys!).


[pt-br] Add concepts/configuration/manage-resources-containers.md

Changes

Add translation for page concepts/configuration/manage-resources-containers.md.
Add translation for two glossary entries:

eviction;
cgroups.

/cc @edsoncelio

@devlware PTAL :)

/uncc jailton yagonobre

/lgtm

/approve


no such attribute 'package_file_name' in '_real_pkg_tar' rule

Hi, I want to use bazel to package my folder and facing below issue. Could you take a look? Is there any example of how to use this?
Error info
$ bazel build main:hello_package
ERROR: /home/topaz/Projects/BazelDemo/stage2/main/BUILD:8:8: //main:hello_package: no such attribute 'package_file_name' in '_real_pkg_tar' rule
ERROR: Skipping 'main:hello_package': Error evaluating 'main:hello_package': error loading package 'main': Package 'main' contains errors
WARNING: Target pattern parsing failed.
ERROR: Error evaluating 'main:hello_package': error loading package 'main': Package 'main' contains errors
INFO: Elapsed time: 0.139s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)

Bazel version
$ bazel version
Bazelisk version: v1.18.0
Build label: 6.4.0
Build target: bazel-out/aarch64-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Oct 19 17:07:17 2023<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

Structure
$ tree -L 2
.
├── BUILD
├── main
│   ├── BUILD
│   └── hello.cc
└── WORKSPACE

WORKSPACE
$ cat WORKSPACE
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "rules_pkg",
    urls = [
        "https://mirror.bazel.build/github.com/bazelbuild/rules_pkg/releases/download/0.9.1/rules_pkg-0.9.1.tar.gz",
        "https://github.com/bazelbuild/rules_pkg/releases/download/0.9.1/rules_pkg-0.9.1.tar.gz",
    ],
    sha256 = "8f9ee2dc10c1ae514ee599a8b42ed99fa262b757058f65ad3c384289ff70c4b8",
)
load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
rules_pkg_dependencies()

main/BUILD
$ cat main/BUILD
load("@bazel_tools//tools/build_defs/pkg:pkg.bzl", "pkg_tar")

cc_binary(
    name = "hello",
    srcs = ["hello.cc"],
)

pkg_tar(
    name = "hello_package",
    srcs = [
        ":hello",
    ],
    package_file_name = "hello.tar.gz"
)

load("@bazel_tools//tools/build_defs/pkg:pkg.bzl", "pkg_tar")   is unsupported, and not from rules_pkg
Use @rules_pkg//pkg:tar.bzl", "pkg.tar")

Thank u. I've tried to build rpm using Bazel, and facing the bellow issue.
main/BUILD
$ cat main/BUILD
load("@rules_pkg//pkg:rpm.bzl", "pkg_rpm")

cc_binary(
    name = "hello",
    srcs = ["hello.cc"],
)

pkg_rpm(
  name="hello_rpm",
  srcs = [":hello"],
  license = "Internal",
  package_file_name = "hello.rpm",
  summary = "test",
)

output
$ bazel build main:hello
INFO: Analyzed target //main:hello (1 packages loaded, 2 targets configured).
INFO: Found 1 target...
Target //main:hello up-to-date:
  bazel-bin/main/hello
INFO: Elapsed time: 0.183s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action

I can not find my rpm package by using this BUILD file.
$ find . -name "hello.rpm"
$

However, if I specify the out attribute get the below issue (The pkg_tar can specify "out" attribute)
$ bazel build main:hello
ERROR: /home/topaz/Projects/BazelDemo/stage4/main/BUILD:8:8: //main:hello_rpm: no such attribute 'out' in 'pkg_rpm' rule
ERROR: Skipping 'main:hello': Error evaluating 'main:hello': error loading package 'main': Package 'main' contains errors
WARNING: Target pattern parsing failed.
ERROR: Error evaluating 'main:hello': error loading package 'main': Package 'main' contains errors
INFO: Elapsed time: 0.112s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded)

Could u take a look anything wrong of the BUILD file

If you want the rpm, you should do bazel build main:hello_rpm '
Also, find . won't work. Output is in bazel-bin, so you need find bazel-bin/. ...


Blank line filter in dataloader doesn't quite work

I assume line 44 in dataloader_iam.py is supposed to ignore blank lines as well as those starting with # but it doesn't work because lines read from the open file include the newline at the end. I think if not line or line[0] == '#' should be changed to if not line.strip() or line[0] == '#':.

I think it was just intended to be used for comment lines, not for empty lines. But ignoring empty lines too makes sense, will add it.


feat: add WM_WTSESSION_CHANGE, and WTS_SESSION_*  constants

Description

Related Issue

Type of Change

[x] ✨ feat -- New feature (non-breaking change which adds functionality)
[ ] 🛠 fix -- Bug fix (non-breaking change which fixes an issue)
[ ] ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 refactor -- Code refactor
[ ] ✅ ci -- Build configuration change
[ ] 📝 docs -- Documentation
[ ] 🧪 test -- Test
[ ] 🗑 chore -- Chore

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

Project coverage is 61.73%. Comparing base (ce1cd85) to head (7662d84).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #914   +/-   ##
=======================================
  Coverage   61.73%   61.73%
=======================================
  Files          33       33
  Lines        1061     1061
=======================================
  Hits          655      655
  Misses        406      406

Flag
Coverage Δ

win32
59.33% <ø> (ø)

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

Files with missing lines
Coverage Δ

packages/win32/lib/src/constants.dart
8.77% <ø> (ø)


Focus when expanding and collapsing BottomSheet with VoiceOver and TalkBack

Scenario to reproduce
When the sheet is expanded the focus follow the "COVID alert is active and jumps back to the bottom of the page view.
When the sheet is collapsed the focus has inconsistent positioning. It should orient people to the header or.
Expected behaviour
When BottomSheet is expanded, it should focus on first card header.
When BottomSheet is collapsed, it should focus on header in the content.
Bug or issue / WCAG
2.4.3 Focus Order
Video of experience
https://drive.google.com/drive/u/0/recent
I am combining these issues here:
https://github.com/cds-snc/covid-shield-mobile/issues/544
https://github.com/cds-snc/covid-shield-mobile/issues/542
https://github.com/cds-snc/covid-shield-mobile/issues/488

@henrytao-me @smcmurtry I've combined the focus issues here.

Pending usability findings https://github.com/cds-snc/covid-shield-mobile/issues/565

this one too. https://github.com/cds-snc/covid-shield-mobile/issues/567


Issues with adding mediaType to ids:representation (v4.2.5)

Using Infomodel library v4.2.5.
According to the Infomodel, it should be possible to add official IANAMediaTyoes and custom media types to the representation:
ids:MediaType. Removed instances for ids:IANAMediaType.

Media types via ids:mediaType with range ids:IANAMediaType should be used with the corresponding IANA URLs, as these have complete coverage. E.g., for JSON-LD:
"ids:mediaType": {
  "@id":   "https://www.iana.org/assignments/media-types/application/ld+json",
  "@type": "ids:IANAMediaType"
}
For custom media types (ids:CustomMediaType), it is advised to use a recognizable unique identifier.

With the newest library version, the IANAMediaTypeBuilder has been removed. Since the MediaType and CustomMediaType do not inherit from each other and both classes are enums, it is not possible to add other types than the provided json or other. Can you give a hint on how to implement? Perhaps I have missed something.

@JohannesLipp We see, that this is still an open issue. Currently data offerings of DSC contain the media type in following structure:
 "ids:mediaType" : {
      "@type" : "ids:IANAMediaType",
      "@id" : "https://w3id.org/idsa/autogen/iANAMediaType/971f7e84-f697-4783-9683-0c6a5a2d45fb",
      "ids:filenameExtension" : "application/json"
    }

See full example here: https://international-data-spaces-association.github.io/DataspaceConnector/Documentation/v6/Messages#resourceupdatemessage
A proper structure is described by Julia above. As far as I seem this shall be possible to archive by simple calling constructor and setting the id as parameter https://github.com/International-Data-Spaces-Association/Java-Representation-of-IDS-Information-Model/blob/cbff893bf48e8b4c3a7f7a0facd446d69c83eb4b/de/fraunhofer/iais/eis/IANAMediaTypeBuilder.java#L17
Am I right? Are you aware of any problems, which might occur in other components when setting the id correctly? @sebplorenz @timwirtz86
Another related issues: https://github.com/International-Data-Spaces-Association/InformationModel/issues/224

@SebastianOpriel @juliapampus what is the respective infomodel version for "Infomodel library v4.2.5"?
In short: IMHO @SebastianOpriel suggests a correct solution by passing the IANA URL as id to the respective builder method.
The ids:IANAMediaType hints to the possibility of using pre-defined IANA media types, such as e.g. application/json as listed at IANA at https://www.iana.org/assignments/media-types/.

Currently 4.2.7 is used: https://github.com/International-Data-Spaces-Association/IDS-Messaging-Services/blob/1f55002f8063b6af4af2615fbf850c815446f092/pom.xml#L89
Changelog see: https://github.com/International-Data-Spaces-Association/Java-Representation-of-IDS-Information-Model/blob/main/Changelog.md#427---2021-11-03
I am not aware how IAIS is tracking the version. This was also a big confusion in a discussion some time ago. You maybe know responsible contacts for infomodel library better than me.
Thanks for your opinion, we will take that as an request for improvement.


tsserver.js 100% CPU on Code Insiders

VSCode Version: Version 1.34.0-insider (1.34.0-insider)
OS Version: macOs 10.14.4 (18E226)

Steps to Reproduce:

Open any javascript file in vscode
CPU spikes to 100% in Code Helper

Does this issue occur when all extensions are disabled?: Yes
Whenever I open a javascript file in vscode the CPU spikes to 100% and it vscode is slow.  It will stay between 98%-150% while the file is open.  I've tried installing the insider edition and disabling all extensions and that didn't change anything.
I have node v11.13.0 installed on my computer.  I don't have typescript installed, nor am I using it in this project that I'm working with.
This happens even if I open a single javascript file, I don't need to have a folder opened.
What additional steps can I take to help find the cause of this?
Thanks

Thanks for the logs. Moving this issue upstream as I don't see anything suspicious in the logs from @dusty. These were collected when the high cpu usage was happening, correct?
@awwong1 From your logs, I see that you have @types/styled-components installed in your workspace. Can you please make sure you have the latest version of this. There was a perf issue with a few versions: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/34391

Yes, this was during high CPU.

Sorry all, I didn't realize that this thread was about the insiders build. Well, I downloaded the insiders build and I haven't been able to duplicate this problem, seems to be fixed on insiders. Here's my current version:
Version: 1.33.0-insider (user setup)
Commit: 9b849d9de7168eb4f685823bf9b9e27a0a8dae74
Date: 2019-03-08T06:59:35.464Z
Electron: 3.1.3
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

I'm still having issues with code insider.  On 1.34.0.
Could it be the size of the project?  I'm working on a relatively large project, we have about 1600 src .js files.

Sorry all, I didn't realize that this thread was about the insiders build. Well, I downloaded the insiders build and I haven't been able to duplicate this problem, seems to be fixed on insiders. Here's my current version:
Version: 1.33.0-insider (user setup)
Commit: 9b849d9de7168eb4f685823bf9b9e27a0a8dae74
Date: 2019-03-08T06:59:35.464Z
Electron: 3.1.3
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

Haha, I spoke too soon. It's happening again right now. Oddly tsserver is not the culprit, at least according to the process explorer. I didn't get a chance to turn on the tsserver verbose log, but will do that now and post the log when this happens again. Or, is there another log you need since process explorer does not show tsserver to be consuming cpu?

@mjbvz I have the latest version of @types/styled-components (4.1.15).
I still experience issues using VSCode 1.33.1.
Is this issue related to VScode shipping with TypeScript 3.4?
I downgraded my editor to VSCode 1.32.3 and I do not experience any performance issues, even with<EMAIL_ADDRESS>in my package.json file.

@awwong1 You also need to switch your workspace to use your local typescript version by by following these instructions
Please try this again, but using the latest typescript@next

I have tried typescript 3.3.1, 3.4 and @next. Cleared typescript caches and tsserver is still using 100% of the cpu when typing. Every keystroke takes around 2-3 seconds.

There are a lot of different versions being reported here and a lot of different possible root causes. 3.3 had some issues that were fixed in 3.4; if anyone's on 3.5 and still seeing this, please log a new issue with server logs as suggested by @mjbvz above. Thanks!


Ignoring certificate errors in Chrome headless

What steps are required to instantiate a headless Chrome browser object that won't verify certificates?
The following displays a blank page when navigating to a test website w/ a self-signed cert but otherwise works on pages that have valid certs:
this_profile = Selenium::WebDriver::Chrome::Profile.new
this_profile['download.prompt_for_download'] = false
this_profile['download.default_directory'] = '~/Downloads'

this_browser = Watir::Browser.new(
  :chrome,
  headless: true
)

this_browser.goto('https://<IP_ADDRESS>')
this_browser.title
=> ""

Versions:
Watir 6.10.0
Chromium 62.0.3202.89
Chromedriver 2.32
I've even tried:
              this_browser = Watir::Browser.new(
                :chrome,
                headless: true,
                switches: [
                  '--ignore-certificate-errors'
                ]
              )

to no avail.  The interesting part is if I use :chrome w/o the headless option, the page renders properly.  Please advise.
Thanks in advance for your help!

Headless chrome does not respect any preferences. Google didn't even include that code in headless chromium.
@p0deje & @jkotests do you think we should add a warning to our capabilities class when using both chrome preferences and headless?

So for headless browsing is it advised to simply use firefox at this point?

Most people using headless don't actually need headless. If headless gem with xvfb make sense, I'd recommend that. If Firefox headless does what you need, then go for it.

No thanks - there's also a multi-OS requirement...I tried firefox but that's not working properly either.  I don't know wth Google was thinking about not respecting any preferences while headless but running headless chrome and ignoring certificates is kind of a big deal when leveraging automation to test internal sites.

Headless is both complicated and impressive. Most test suites these days are run via CI on remote machines that have GUIs, though, so headless doesn't matter.

fwiw: State on supporting a "acceptInsecureCerts" flag:
https://bugs.chromium.org/p/chromium/issues/detail?id=721739

thx @ninp0  i will use this issue as good starting point


Upgrade jruby-gradle-jar-plugin to 1.5.0.

@muga Can you have a look? It may solve the problem of the "rubygems.lasagna.io" problem in building Embulk. (Thanks to @hiroyuki-sato's finding. :) )

@muga @dmikurube
JFYI https://github.com/jruby-gradle/jruby-gradle-plugin/issues/297

Let me check diff https://github.com/jruby-gradle/jruby-gradle-plugin/compare/v1.0.1...v1.5.0

@muga https://github.com/jruby-gradle/jruby-gradle-plugin/commit/2d1c14e1765f666a70fb90484486ee17290f5093 maybe this commit.

@hiroyuki-sato cool. thank you.

@dmikurube @hiroyuki-sato It seems that jruby-gradle-plugin is built by Java8 and the class files are formatted in version 52.0. If we use the plugin v1.5.0, we might not be able to build Embulk by Java7. To use v1.5.0, do we build Embulk by Java8? Or we will look for other workarounds?
https://github.com/jruby-gradle/jruby-gradle-plugin/compare/v1.0.1...v1.5.0#diff-c197962302397baf3a4cc36463dce5eaR21
To test Embulk on Travis CI, we already use Java8. That is the reason why this PR's build passed.
https://github.com/embulk/embulk/blob/master/.travis.yml#L3

Maybe we need update jruby-gradle again when rubygems.lasagna.io back.
https://github.com/jruby-gradle/jruby-gradle-plugin/issues/297#issuecomment-320670502

@dmikurube @dmikurube
Ah, Java8.....
It found temporary fix
https://github.com/jruby-gradle/jruby-gradle-plugin/issues/297#issue-248368105
But I'm not sure where is add this entry in Embulk.
And also I asked rubygems.lasagna.io status.
https://github.com/jruby-gradle/jruby-gradle-plugin/issues/297#issuecomment-326155030

Maybe the top one (in buildscript { ... }) would work. Will try that later.

@muga @hiroyuki-sato Trying #776.

#776 looks successful. I keep this PR open, and will merge when we go Java 8.

@sakama (Cc: @muga) Embulk is going to Java 8 after #853, and ready for this PR. Can you have a look?

Thanks! Merging.


Deprecation of implode usage with PHP 7.4

bin/cake migrations create gives:
2019-12-15 10:50:01 Notice: Deprecated (8192): implode(): Passing glue string after array is deprecated. Swap the parameters in [/home/diego/public_html/cakephp/vendor/robmorgan/phinx/src/Phinx/Util/Util.php, line 111]
This was already fixed in master with #1606 but wasn't merged in 0.11.x branch.

Master is 0.11
What branch are you referring to? Pretty sure that one is not supposed to be used.

I made a 0.next and merged master into it: https://github.com/cakephp/phinx/compare/0.next?expand=1
Please move away from using the 0.11.x as this is misleading and will be removed in the near future.

Just upgraded a test project to CakePHP 4.0-RC2 with PHP 7.4.
Phinx hasn't been installed manually but via dependency of cakephp/migrations.
The phinx version is:
"name": "robmorgan/phinx",
"version": "0.11.x-dev",

Thx, we then need to fix migrations, too.

https://github.com/cakephp/migrations/pull/415


Zarf dependence on existing storageclass

Is your feature request related to a problem? Please describe.
Zarf is unable to init against a cluster that does not contain a storageclass by default. RKE2 is a given example that will require deployment of resources to support a storageclass before zarf init will execute successfully.
Fundamentally, zarf should support a pattern (either logically or documented) that allows for the storageclass to be brought with the init package for the registry to use. Assuming the existence of one puts a burden on the true airgap deployment scenario.
Describe the solution you'd like
Given an empty cluster without any storage infrastructure, when zarf init is executed then zarf should allow a storageclass component to be included and used by the registry (Allowing for enhanced deployments of the registry such as HA)
Describe alternatives you've considered
Creation of a custom init package that performs the following:

Deploy the zarf-injector
Deploy the zarf-seed-registry w/o persistence
Deploy the zarf-registry w/o persistence
Deploy the zarf-agent
Deploy a given storageclass and any required resources
Re-deploy the zarf-registry with persistence
Seed the registry, agent and storageclass images

Tested the above and currently incurring issues around image push auth. Either due to persistence or credential mis-match perhaps?
Additional context
May be related to https://github.com/defenseunicorns/zarf/issues/375

So I have this working locally on a fork using a similar above construct . I added a step to a custom init package that after zarf-seed-registry w/o persistence installs the rancher local path provisioner (if your not using k3s already)  and then after thats up re-install zarf-registry with persistence.   I ran into this problem all the time on RKE2 as we use Longhorn but that doesn't help us for initial Airgap install.  Let me know and I can post / put a pull request in.

Linking https://github.com/defenseunicorns/zarf/issues/1998 as this deals with similar StorageClass shenanigans


A Fade Transition Between Screens.

Here I will be implementing Fade Transition Between Screens.
kindly assign me this work, I wanna take it

@AvinashMahanthi transitions are already added in the repo, so need for Fade Transition as it is a retro theme based app.


RDS DBCluster provisioning with composite KMS Key fails with 'The specified KMS key [...] does not exist'

I'm using the Composition below to create a DBCluster. I'd like to create a KMS key per DBCluster.
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
  name: mysqlclusters.aws.database.du.co
spec:
  compositeTypeRef:
    apiVersion: database.du.co/v1alpha1
    kind: XMySQLCluster
  resources:
  - name: kmskey
    base:
      apiVersion: kms.aws.crossplane.io/v1alpha1
      kind: Key
      spec:
        forProvider:
          region: eu-west-1
  - name: dbcluster
    base:
      apiVersion: rds.aws.crossplane.io/v1alpha1
      kind: DBCluster
      spec:
        forProvider:
          ...
          region: eu-west-1
          kmsKeyIDSelector:
            matchControllerRef: true
          ...

This successfully creates the kms key:
➜  kubectl get xmysqlcluster
NAME                    READY   COMPOSITION                        AGE
rg-test-cluster-5bp8r   False   mysqlclusters.aws.database.du.co   2d17h

➜  kubectl get keys.kms.aws.crossplane.io -l crossplane.io/composite=rg-test-cluster-5bp8r
NAME                          READY   SYNCED   EXTERNAL-NAME
rg-test-cluster-5bp8r-zzp65   True    True     85c59e3b-9b0f-437d-b721-a8d094c56d4f

But the DBCluster fails to provision:
➜   kubectl get dbcluster.rds -l crossplane.io/composite=rg-test-cluster-5bp8r
NAME                          READY   SYNCED   EXTERNAL-NAME
rg-test-cluster-5bp8r-88lq4   False   False    rg-test-cluster-5bp8r-88lq4

with this error:
  Warning  CannotCreateExternalResource     2s                    managed/dbcluster.rds.aws.crossplane.io  cannot create DBCluster in AWS: KMSKeyNotAccessibleFault: The specified KMS key [rg-test-cluster-5bp8r-zzp65] does not exist, is not enabled or you do not have permissions to access it.
           status code: 400, request id: 9ffbdf72-077d-4729-8287-efa720a8b3fc

`
The key does exist in the AWS UI.
What permissions do I need to give it?
Should it be looking up using the name rg-test-cluster-5bp8r-zzp65 or does it actually need to be using the externalName?
Any ideas where I should look to find more?

Looking in Cloudtrail, I can see the following errorMessage. That KMS key does indeed not exist - that's just the crossplane 'internal' (?) name the externalName resource:  85c59e3b-9b0f-437d-b721-a8d094c56d4f
Is this the issue? Should it be looking up the externalName and passing that through?
{
...
    "errorMessage": "The specified KMS key [rg-test-cluster-5bp8r-zzp65] does not exist, is not enabled or you do not have permissions to access it.",
    "requestParameters": {
        "dBClusterIdentifier": "rg-test-cluster-5bp8r-88lq4",
...
        "kmsKeyId": "rg-test-cluster-5bp8r-zzp65",
        "enableIAMDatabaseAuthentication": false,
        "engineMode": "provisioned",
        "deletionProtection": false,
        "copyTagsToSnapshot": false
    },
...

Confirming a further few things:

I've added a policy to the kms key to allow the crossplane user to see it. I don't think this was necessary, but it felt like the next thing to try.

I updated the composition to use the crossplane-provisioned key directly using the actual externalName (eg kmsKeyID: d32wc-sdfsq-asd) and it created fine

I guess the kmsKeyIDSelector should actually be a kmsKeyIDRefSelector?

A kubectl get dbclusters.rds rg-test-cluster-4bfzf-z8dg2 -o yaml shows that crossplane has added both a kmsKeyID and a kmsKeyIDRef:
...
    engine: aurora-mysql
    engineMode: provisioned
    engineVersion: 5.7.mysql_aurora.2.10.0
    kmsKeyID: rg-test-cluster-4bfzf-6xg6f
    kmsKeyIDRef:
      name: rg-test-cluster-4bfzf-6xg6f
    kmsKeyIDSelector:
      matchControllerRef: true
    masterUserPasswordSecretRef:
...

And I guess it's then using the KeyID as it's the most precise?

And if I kubectl edit dbclusters.rds rg-test-cluster-4bfzf-z8dg2 and delete the kmsKeyID: rg-test-cluster-4bfzf-6xg6f, then run kubectl get dbclusters.rds rg-test-cluster-4bfzf-z8dg2 -o yaml again, it's then replaced with the correct ref:
...
    engine: aurora-mysql
    engineMode: provisioned
    engineVersion: 5.7.mysql_aurora.2.10.0
    kmsKeyID: 5dbbec3c-2a11-4185-b467-b8a59d947689
    kmsKeyIDRef:
      name: rg-test-cluster-4bfzf-6xg6f
    kmsKeyIDSelector:
      matchControllerRef: true
    masterUserPasswordSecretRef:
...

can you tell us which provider-aws and crossplane version you are using ?


if(mounted) added for setState()

mounted check added before calling setState()
Issue: #5
Kindly review @sachin-kumar56 @hemanath-ss

@sachin-kumar56 @hemanath-ss Any update on this ?


 Also spot <$> as an alias for fmap.

This already works for fromMaybe foo (fmap f x) and fromMaybe foo $ fmap f x, but not fromMaybe foo (f <$> x)

The $ vs brackets is built into the matcher automatically. I added a special extra case for <$> instead of fmap.


Update moment.js

Small change avoids minification bugs.

Now we generate all files from ES6 modules. Should we add this to all bundles?

@Hypercubed I couldn't find on the internet a reliable source of whether this is good or bad practice. It might break some old browsers : http://stackoverflow.com/a/12319804/235253
So I'm not sure we need it yet. Please provide more proof that it is a good thing, and then modify the headers we use for the bundles (all code is now transpiled from es6 modules).

In particular, please provide an example of how not having it creates a minification bug.  Thanks.

In some cases concatenating and minimizing will result in a bug.  For example the following:
var b = 7
var a = 3 + b   // another modules's code
(function(global, factory) {/* moment.js */} )

Will compress to:
var b=7,a=3+b(function(global, factory) {/* moment.js */});

Which would give a "b is not a function" error.
I admit this is not moment.js's fault.  You can blame the other library for not using the "optional" semicolons or you can blame the minification tool.  But it does come up sometimes... as it did for me.

Close in favor of #2739


Incompatible recipes warning

I accidentally added an invalid recipe path, and now when I try to add the right one I get
Warning (straight): Package "ox-ravel" has two incompatible recipes (:local-repo cannot be both "~/.emacs.d/orgmode-accessories/ox-ravel.el" and "~/.emacs.d/orgmode-accessories")
I'm not sure how to clear the wrong one -- perhaps the warning text could make a suggestion?

Providing a new recipe does override the old one. You should only get a warning the first time.
The warning text should be modified to make this clear. Perhaps something like Warning (straight): Recipe for "ox-ravel" has been overridden (:local-repo changed from "~/.emacs.d/orgmode-accessories/ox-ravel.el" to "~/.emacs.d/orgmode-accessories")?

Sounds good to me.


Investigate performance of workspace diagnostics

Similar to #749, profiling shows that workspace diagnostics take a significant amount of time (30s). Although, much of it might be due to the start up cost of type checking the whole workspace, however profiling does not show us any significant calls to Frontend::check:

Also, findFilesForWorkspaceDiagnostics takes 2s, which can probably be improved further to prevent delays whilst workspace diagnostics are being computed on a fully cached repository. (workspace diagnostics should be instanteneous if there have been no changes to files)

Actually, this is with luau-lsp.diagnostics.workspace disabled, which is pretty bad


update astra server; update transcribe, polly extension.

pass transcribe and polly init param when invoking start api;
update transcribe_asr graph to display chat in playground;
bump up agora_rtc dependency version;
other code improvements.

Thanks very much for the contribution! We have just upgraded the underlying dependency to TEN framework, would you please help to refine it so that we're able to merge it? Here's things need to change:

rebase main
rename rte -> ten, RteEnv -> TenEnv
rename send_pcm_frame -> send_audio_frame, on_pcm_frame -> on_audio_frame

Please feel free to ask if any question, thanks again!


[SPARK-6802][SPARKR]Convert NAs to null type in SparkR DataFrames

Merged build triggered.

Merged build started.

Test build #32832 has started for   PR 6190 at commit bf82dee.

Test build #32832 has finished for   PR 6190 at commit bf82dee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32832/
Test PASSed.

Merged build finished. Test PASSed.

@davies Could you take a look at this ?

@hqzizania The title is wrong - Could you change this to [SPARK-6820] ?

@hqzizania, is it possible to simplify the conversion to one place,something like:
jrdd <- getJRDD(lapply(rdd,naToNull), "row")?
Another thought is, can we do the conversion in SerDe? seems this is more generic. For example, when you serialize an Int, you check it if is NA, if yes, convert it to a NULL. NA/NA_integer/NA_character/NA_real_ should be handled together.

@hqzizania Any update on this ?

@davies, do you have any comment on this issue?

Merged build triggered.

Merged build started.

Test build #34446 has started for   PR 6190 at commit 4614f6b.

Test build #34446 has finished for   PR 6190 at commit 4614f6b.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34451 has started for   PR 6190 at commit bb3411a.

Thanks @hqzizania for the update. I left some comments inline.
@davies will be great if you took a look

@hqzizania Could you add some tests?

Test build #34451 has finished for   PR 6190 at commit bb3411a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #34476 has started for   PR 6190 at commit 1641f9e.

Test build #34476 has finished for   PR 6190 at commit 1641f9e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

LGTM, just one minor comment, thanks!

Thanks @hqzizania - LGTM. Merging this

@shivaram  oops, I haven't fix the Nit davies said.

Its fine - it will make one line of code more complex and remove one line of code. If you want you can make a follow up PR, its up to you and @davies :)

@hqzizania Not needed, never mind.

@davies :)


Error: Not Found

It worked until yesterday, When trying to upload a video. the plugin fails.

This is due to some sort of possible outage with Vimeo. Their support got back to me at approx 6pm EST today that they had a short API outage and had fixed it. I'm still seeing some issues now, but they at least are aware of current issues.
I would expect functionality to be restored shortly.

I though so... Same problem here:)


Codegen generate swift models with deprecated keys.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v20.4.0
Amplify CLI Version
12.1.1
What operating system are you using?
amplify codegen models
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
N/A
Describe the bug
In swift models we get warnings in each generated model files.
Warning: 'pluralName' is deprecated: Use of pluralName is deprecated, use syncPluralName instead.
Expected behavior
It should just use syncPluralName key instead.
Reproduction steps

run amplify codegen models
Check newly generated swift models.
See Xcode warning tab is polluted.

Project Identifier
Project Identifier: 100d1308b49cbda339110ec98ca3549a
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

I was not able to reproduce this. It appears this has been fixed in the latest version of the CLI.


Default pinned property

How can I set the pinned property to True by default?
Or maybe I can upload annotations to task with this property?

By default pinned is true only for polygons
There is no formal way to make it true for other types of shapes (except of code changing of course).
Could you please clarify your use case?

@bsekachev Thanks, I did it with code changing.
I have a lot of good boxes from the model, but a lot of them have incorrect labels.
The task is only to correct the labels without changing the position of the boxes.
But with a large number of boxes, sometimes they can easily moved.

Okay, got it.
You also could try attribute annotation mode.

There you can switch objects using Tab and setup a label at right sidebar.
In standard view you can also bind labels to hotkeys (Ctrl + 1, 2, 3, ...) (if their count less than 11) and switch labels with hotkeys.

Thanks but I try it and it's not so comfortable for my case :(
And I have a lot of checkboxes (multilabel classification) and in attribute annotation mode they show one by one, not altogether.


[stable/prometheus] Default rules

Is this a request for help?:
No
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Feature req

Version of Helm and Kubernetes:
latest
Which chart:
stable/prometheus
What happened:
No default alert rules
What you expected to happen:
Add default alert rules
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

Re-opening


Removed the Underline from the Back Button of quiz game

fixes #216
Screenshot:-

Thank you for the  fix!


feat: run migrations with specified transaction mode

Fixes #417
Apologies for not waiting for an answer for you, but the fix looks simple enough, so I thought I'd open a PR.

@mderriey no problem. PR Looks good! Thank you for your contribution :blush:


Decimal nullable on collection187 issue

Have changed the compare logic for complex types using IgnoreOrderLogic when comparing complex type collections that contains a object with nullable decimal property. The issue #187 describes more details to reproduce.
Now, logic compares the FullName instead of Name and apply decimal formatting based on DecimalPrecision configuration that wasn't beeing applyed.
Added in CompareDecimalTests some new cases that grants this issue dont come back in future maintenances.
None other main logic was changed, just IgnoreOrderLogic.
Added IsDecimal(object value) in TypeHelper class and passing parameterValue to identify if parameter is a decimal type
FIXES #187 #188

Thanks so much

Any predictions of when a future release will be released with the fix?

Normally I release in groups of of at least three defect fixes or enhancements.  I am still waiting for another defect or pull request to add to the existing issue.


cannot access /dls/ops-data

The container does not load those folders.
This is only slightly inconvenient.

Is it appropriate to load this folder by default for everyone? How do permissions work by default, in this area?
You can add in additional mounts in your launch script. Perhaps we should include a command-line argument to provide additional mounts in the run-dev-c7.sh script?
It is worthwhile asking whether we want to completely replicate a RHEL7 workstation, or just provide the necessary functionality with some sensible restrictions.

I like the idea of adding extra mounts on the command line options.
The permissions for any mounts should work as normal I believe since all SELinux and secondary groups are handled.
There is also no significant cost to adding mounts that I'm aware of (maybe slower startup for the first invocation) so we could add this one.

I don't know what the permissions are like in the /dls/ops-data folder, but if I'm able to affect it at all I wouldn't want it included.
I would prefer being able to opt-in to or opt-out of these things. Even though dev-c7 is for general purpose use, I appreciate using it as a sandbox.
Obviously, we already have that problem elsewhere. I would personally vote for the ability to exclude things like read-write access to filesystems (excluding e.g. current directory) through command-line options, but I'm not going to be upset if other people disagree.

@MJGaughran I don't have a problem with making the file system mounts configurable.
Do you mean you want Read only access to the full list or no access? Note that quite a bit of dls_sw is needed for many of our tools to work, but read only would be OK for most tools.

I don't have an issue with read-only access.

I think we need to make the mounts configurable see #57


refactors wandb.sklearn into submodules

Description
This PR refactors the wandb.sklearn submodule into submodules -- plot for the core functions that are user-facing and invoke wandb.log and calculate for the internal functions used to calculate and format the data (typically using wandb.Table and wandb.visualize for the latter). We re-export the user-facing functions under the same names
Previously, all of this code lived in the __init__.py file for the wandb.sklearn submodule and had a few levels of unnecessary nesting (e.g. into nested if statements or function definitions), which made it difficult to read the code.
Furthermore, the code was untested, and this PR adds some very basic yea tests. These tests simply ensure that the top-level plot_{regressor, clusterer, classifier} functions run on the examples in our demo colab. These functions call almost all of the other functions in the submodule, so the coverage isn't bad.
The goal was to keep behavior entirely the same, making this a "pure" refactor -- which improvements should be easier to do now.
There is one exception: we were previously mis-reporting the maximum number of rows allowed in each example. The warnings have now been changed to report the actual limiting values. Some of those limiting values are very low (100 examples) but there is no documentation of how those values were arrived at, so I've opted not to increase them to the reported value (10000 examples, based on the MAX_ROWS for wandb.Table.
Testing
The outputs of the tests on the pre-refactor wandb.sklearn module are here, while the results post-refactor as of commit dee4040f4266772ae1202aed4e44c89c1c2d7faf are here.
The results have been quickly checked for similarity, up to RNG.
These tests are very minimal -- they just check exit status. A fuller test suite would check that all expected charts are logged, but I've pushed that to after the next update, which may change behavior.
Release Notes
Below, please enter user-facing release notes as one or more bullet points.
If your change is not user-visible, write NO RELEASE NOTES instead, with no bullet points.
------------- BEGIN RELEASE NOTES ------------------
NO RELEASE NOTES
------------- END RELEASE NOTES --------------------

reopening as two separate PRs for testing and for refactor.