Dataloader with >0 workers when using DDP causes a crash

Bug description
Having a dataloader with >0 workers causes a crash. This behavior occurs both with custom datasets, and even standard huggingface datasets, and torchvision datasets.
The dataloaders work fine standalone with many workers, and also work with accelerate just fine.
The run general works until the first validation step at which point it crashes. Interestingly, num_sanity_val_steps works fine [e.g., num_sanity_val_steps=10].
Working version:
def main(config):
    """Main entry point for training."""
    _print_config(config, resolve=True, save_cfg=True)
    tokenizer = get_tokenizer(config)
    train_dataloader, val_dataloader = get_dataloaders(config, tokenizer=tokenizer, valid_seed=config.seed)

    for i in range(10):
        for batch in tqdm(train_dataloader):
            pass

        for batch in tqdm(val_dataloader):
            pass

if __name__ == "__main__":
    main()

Not working:
trainer.fit(model, train_ds, valid_ds)

What version are you seeing the problem on?
v2.2, master
How to reproduce the bug
No response
Error messages and logs
Traceback:
terminate called after throwing an instance of 'c10::Error'                                                                                | 0/? [00:00<?, ?it/s]
  what():  CUDA error: initialization error
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Exception raised from c10_cuda_check_implementation at /opt/conda/conda-bld/pytorch_1716905979055/work/c10/cuda/CUDAException.cpp:43 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x57 (0x7f7f99b0d897 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::string const&) + 0x64 (0x7f7f99abdb25 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #2: c10::cuda::c10_cuda_check_implementation(int, char const*, char const*, int, bool) + 0x118 (0x7f7f99be7718 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #3: <unknown function> + 0x1d6f6 (0x7f7f99bb26f6 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #4: <unknown function> + 0x1f5e3 (0x7f7f99bb45e3 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #5: <unknown function> + 0x1f922 (0x7f7f99bb4922 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #6: <unknown function> + 0x5a5950 (0x7f7fe82d8950 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #7: <unknown function> + 0x6a36f (0x7f7f99af236f in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #8: c10::TensorImpl::~TensorImpl() + 0x21b (0x7f7f99aeb1cb in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #9: c10::TensorImpl::~TensorImpl() + 0x9 (0x7f7f99aeb379 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #10: <unknown function> + 0x851088 (0x7f7fe8584088 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #11: THPVariable_subclass_dealloc(_object*) + 0x2f6 (0x7f7fe8584406 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
<omitting python frames>

terminate called after throwing an instance of 'c10::Error'
  what():  CUDA error: initialization error
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Exception raised from c10_cuda_check_implementation at /opt/conda/conda-bld/pytorch_1716905979055/work/c10/cuda/CUDAException.cpp:43 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x57 (0x7f7c3193d897 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::string const&) + 0x64 (0x7f7c318edb25 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #2: c10::cuda::c10_cuda_check_implementation(int, char const*, char const*, int, bool) + 0x118 (0x7f7c31a17718 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #3: <unknown function> + 0x1d6f6 (0x7f7c319e26f6 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #4: <unknown function> + 0x1f5e3 (0x7f7c319e45e3 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #5: <unknown function> + 0x1f922 (0x7f7c319e4922 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #6: <unknown function> + 0x5a5950 (0x7f7c80108950 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #7: <unknown function> + 0x6a36f (0x7f7c3192236f in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #8: c10::TensorImpl::~TensorImpl() + 0x21b (0x7f7c3191b1cb in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #9: c10::TensorImpl::~TensorImpl() + 0x9 (0x7f7c3191b379 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #10: <unknown function> + 0x851088 (0x7f7c803b4088 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #11: THPVariable_subclass_dealloc(_object*) + 0x2f6 (0x7f7c803b4406 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #12: <unknown function> + 0x124633 (0x55d22c939633 in /homedir/envs/envname/bin/python)
frame #13: <unknown function> + 0x13d697 (0x55d22c952697 in /homedir/envs/envname/bin/python)
frame #14: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #15: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #16: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #17: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #18: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #19: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #20: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #21: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #22: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #23: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #24: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #25: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #26: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #27: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #28: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #29: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #30: <unknown function> + 0x13d77b (0x55d22c95277b in /homedir/envs/envname/bin/python)
frame #31: <unknown function> + 0x14dcf6 (0x55d22c962cf6 in /homedir/envs/envname/bin/python)
frame #32: <unknown function> + 0x129739 (0x55d22c93e739 in /homedir/envs/envname/bin/python)
frame #33: <unknown function> + 0x12763d (0x55d22c93c63d in /homedir/envs/envname/bin/python)
frame #34: <unknown function> + 0x1d418b (0x55d22c9e918b in /homedir/envs/envname/bin/python)
frame #35: _PyObject_GC_NewVar + 0x23f (0x55d22c93147f in /homedir/envs/envname/bin/python)
frame #36: PyTuple_New + 0x117 (0x55d22c938aa7 in /homedir/envs/envname/bin/python)
frame #37: <unknown function> + 0x1320b5 (0x55d22c9470b5 in /homedir/envs/envname/bin/python)
frame #38: <unknown function> + 0x1321d1 (0x55d22c9471d1 in /homedir/envs/envname/bin/python)
frame #39: <unknown function> + 0x131e4e (0x55d22c946e4e in /homedir/envs/envname/bin/python)
frame #40: <unknown function> + 0x1d7844 (0x55d22c9ec844 in /homedir/envs/envname/bin/python)
frame #41: <unknown function> + 0x1ea6eb (0x55d22c9ff6eb in /homedir/envs/envname/bin/python)
frame #42: <unknown function> + 0x143e8a (0x55d22c958e8a in /homedir/envs/envname/bin/python)
frame #43: _PyEval_EvalFrameDefault + 0x4c12 (0x55d22c94e142 in /homedir/envs/envname/bin/python)
frame #44: _PyFunction_Vectorcall + 0x6c (0x55d22c959a2c in /homedir/envs/envname/bin/python)
frame #45: _PyEval_EvalFrameDefault + 0x13ca (0x55d22c94a8fa in /homedir/envs/envname/bin/python)
frame #46: _PyFunction_Vectorcall + 0x6c (0x55d22c959a2c in /homedir/envs/envname/bin/python)
frame #47: _PyEval_EvalFrameDefault + 0x72c (0x55d22c949c5c in /homedir/envs/envname/bin/python)
frame #48: _PyFunction_Vectorcall + 0x6c (0x55d22c959a2c in /homedir/envs/envname/bin/python)
frame #49: _PyEval_EvalFrameDefault + 0x72c (0x55d22c949c5c in /homedir/envs/envname/bin/python)
frame #50: _PyFunction_Vectorcall + 0x6c (0x55d22c959a2c in /homedir/envs/envname/bin/python)
frame #51: _PyEval_EvalFrameDefault + 0x320 (0x55d22c949850 in /homedir/envs/envname/bin/python)
frame #52: _PyFunction_Vectorcall + 0x6c (0x55d22c959a2c in /homedir/envs/envname/bin/python)
frame #53: _PyEval_EvalFrameDefault + 0x320 (0x55d22c949850 in /homedir/envs/envname/bin/python)
frame #54: _PyFunction_Vectorcall + 0x6c (0x55d22c959a2c in /homedir/envs/envname/bin/python)
frame #55: <unknown function> + 0x144208 (0x55d22c959208 in /homedir/envs/envname/bin/python)
frame #56: _PyObject_CallMethodIdObjArgs + 0x169 (0x55d22c967419 in /homedir/envs/envname/bin/python)
frame #57: <unknown function> + 0x75187 (0x55d22c88a187 in /homedir/envs/envname/bin/python)
frame #58: _PyEval_EvalFrameDefault + 0x3e3b (0x55d22c94d36b in /homedir/envs/envname/bin/python)
frame #59: <unknown function> + 0x1d7c60 (0x55d22c9ecc60 in /homedir/envs/envname/bin/python)
frame #60: PyEval_EvalCode + 0x87 (0x55d22c9ecba7 in /homedir/envs/envname/bin/python)
frame #61: <unknown function> + 0x1dedaa (0x55d22c9f3daa in /homedir/envs/envname/bin/python)
frame #62: <unknown function> + 0x144bf3 (0x55d22c959bf3 in /homedir/envs/envname/bin/python)
frame #63: _PyEval_EvalFrameDefault + 0x5cd5 (0x55d22c94f205 in /homedir/envs/envname/bin/python)

terminate called after throwing an instance of 'c10::Error'
  what():  CUDA error: initialization error
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Exception raised from c10_cuda_check_implementation at /opt/conda/conda-bld/pytorch_1716905979055/work/c10/cuda/CUDAException.cpp:43 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x57 (0x7fe326374897 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::string const&) + 0x64 (0x7fe326324b25 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #2: c10::cuda::c10_cuda_check_implementation(int, char const*, char const*, int, bool) + 0x118 (0x7fe32644e718 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #3: <unknown function> + 0x1d6f6 (0x7fe3264196f6 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #4: <unknown function> + 0x1f5e3 (0x7fe32641b5e3 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #5: <unknown function> + 0x1f922 (0x7fe32641b922 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #6: <unknown function> + 0x5a5950 (0x7fe374b3f950 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #7: <unknown function> + 0x6a36f (0x7fe32635936f in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #8: c10::TensorImpl::~TensorImpl() + 0x21b (0x7fe3263521cb in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #9: c10::TensorImpl::~TensorImpl() + 0x9 (0x7fe326352379 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #10: <unknown function> + 0x851088 (0x7fe374deb088 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #11: THPVariable_subclass_dealloc(_object*) + 0x2f6 (0x7fe374deb406 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #12: <unknown function> + 0x124633 (0x563677bbe633 in /homedir/envs/envname/bin/python)
frame #13: <unknown function> + 0x13d697 (0x563677bd7697 in /homedir/envs/envname/bin/python)
frame #14: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #15: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #16: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #17: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #18: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #19: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #20: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #21: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #22: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #23: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #24: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #25: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #26: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #27: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #28: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #29: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #30: <unknown function> + 0x13d77b (0x563677bd777b in /homedir/envs/envname/bin/python)
frame #31: <unknown function> + 0x14dcf6 (0x563677be7cf6 in /homedir/envs/envname/bin/python)
frame #32: <unknown function> + 0x129739 (0x563677bc3739 in /homedir/envs/envname/bin/python)
frame #33: <unknown function> + 0x12763d (0x563677bc163d in /homedir/envs/envname/bin/python)
frame #34: <unknown function> + 0x1d418b (0x563677c6e18b in /homedir/envs/envname/bin/python)
frame #35: _PyObject_GC_NewVar + 0x23f (0x563677bb647f in /homedir/envs/envname/bin/python)
frame #36: PyTuple_New + 0x117 (0x563677bbdaa7 in /homedir/envs/envname/bin/python)
frame #37: <unknown function> + 0x1320b5 (0x563677bcc0b5 in /homedir/envs/envname/bin/python)
frame #38: <unknown function> + 0x1321d1 (0x563677bcc1d1 in /homedir/envs/envname/bin/python)
frame #39: <unknown function> + 0x131e4e (0x563677bcbe4e in /homedir/envs/envname/bin/python)
frame #40: <unknown function> + 0x1d7844 (0x563677c71844 in /homedir/envs/envname/bin/python)
frame #41: <unknown function> + 0x1ea6eb (0x563677c846eb in /homedir/envs/envname/bin/python)
frame #42: <unknown function> + 0x143e8a (0x563677bdde8a in /homedir/envs/envname/bin/python)
frame #43: _PyEval_EvalFrameDefault + 0x4c12 (0x563677bd3142 in /homedir/envs/envname/bin/python)
frame #44: _PyFunction_Vectorcall + 0x6c (0x563677bdea2c in /homedir/envs/envname/bin/python)
frame #45: _PyEval_EvalFrameDefault + 0x13ca (0x563677bcf8fa in /homedir/envs/envname/bin/python)
frame #46: _PyFunction_Vectorcall + 0x6c (0x563677bdea2c in /homedir/envs/envname/bin/python)
frame #47: _PyEval_EvalFrameDefault + 0x72c (0x563677bcec5c in /homedir/envs/envname/bin/python)
frame #48: _PyFunction_Vectorcall + 0x6c (0x563677bdea2c in /homedir/envs/envname/bin/python)
frame #49: _PyEval_EvalFrameDefault + 0x72c (0x563677bcec5c in /homedir/envs/envname/bin/python)
frame #50: _PyFunction_Vectorcall + 0x6c (0x563677bdea2c in /homedir/envs/envname/bin/python)
frame #51: _PyEval_EvalFrameDefault + 0x320 (0x563677bce850 in /homedir/envs/envname/bin/python)
frame #52: _PyFunction_Vectorcall + 0x6c (0x563677bdea2c in /homedir/envs/envname/bin/python)
frame #53: _PyEval_EvalFrameDefault + 0x320 (0x563677bce850 in /homedir/envs/envname/bin/python)
frame #54: _PyFunction_Vectorcall + 0x6c (0x563677bdea2c in /homedir/envs/envname/bin/python)
frame #55: <unknown function> + 0x144208 (0x563677bde208 in /homedir/envs/envname/bin/python)
frame #56: _PyObject_CallMethodIdObjArgs + 0x169 (0x563677bec419 in /homedir/envs/envname/bin/python)
frame #57: <unknown function> + 0x75187 (0x563677b0f187 in /homedir/envs/envname/bin/python)
frame #58: _PyEval_EvalFrameDefault + 0x3e3b (0x563677bd236b in /homedir/envs/envname/bin/python)
frame #59: <unknown function> + 0x1d7c60 (0x563677c71c60 in /homedir/envs/envname/bin/python)
frame #60: PyEval_EvalCode + 0x87 (0x563677c71ba7 in /homedir/envs/envname/bin/python)
frame #61: <unknown function> + 0x1dedaa (0x563677c78daa in /homedir/envs/envname/bin/python)
frame #62: <unknown function> + 0x144bf3 (0x563677bdebf3 in /homedir/envs/envname/bin/python)
frame #63: _PyEval_EvalFrameDefault + 0x5cd5 (0x563677bd4205 in /homedir/envs/envname/bin/python)

terminate called after throwing an instance of 'c10::Error'
  what():  CUDA error: initialization error
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Exception raised from c10_cuda_check_implementation at /opt/conda/conda-bld/pytorch_1716905979055/work/c10/cuda/CUDAException.cpp:43 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x57 (0x7f549635d897 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::string const&) + 0x64 (0x7f549630db25 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #2: c10::cuda::c10_cuda_check_implementation(int, char const*, char const*, int, bool) + 0x118 (0x7f5496437718 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #3: <unknown function> + 0x1d6f6 (0x7f54964026f6 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #4: <unknown function> + 0x1f5e3 (0x7f54964045e3 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #5: <unknown function> + 0x1f922 (0x7f5496404922 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10_cuda.so)
frame #6: <unknown function> + 0x5a5950 (0x7f54e4b28950 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #7: <unknown function> + 0x6a36f (0x7f549634236f in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #8: c10::TensorImpl::~TensorImpl() + 0x21b (0x7f549633b1cb in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #9: c10::TensorImpl::~TensorImpl() + 0x9 (0x7f549633b379 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #10: <unknown function> + 0x851088 (0x7f54e4dd4088 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #11: THPVariable_subclass_dealloc(_object*) + 0x2f6 (0x7f54e4dd4406 in /homedir/envs/envname/lib/python3.10/site-packages/torch/lib/libtorch_python.so)
frame #12: <unknown function> + 0x124633 (0x5557111ab633 in /homedir/envs/envname/bin/python)
frame #13: <unknown function> + 0x13d697 (0x5557111c4697 in /homedir/envs/envname/bin/python)
frame #14: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #15: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #16: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #17: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #18: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #19: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #20: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #21: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #22: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #23: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #24: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #25: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #26: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #27: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #28: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #29: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #30: <unknown function> + 0x13d77b (0x5557111c477b in /homedir/envs/envname/bin/python)
frame #31: <unknown function> + 0x14dcf6 (0x5557111d4cf6 in /homedir/envs/envname/bin/python)
frame #32: <unknown function> + 0x129739 (0x5557111b0739 in /homedir/envs/envname/bin/python)
frame #33: <unknown function> + 0x12763d (0x5557111ae63d in /homedir/envs/envname/bin/python)
frame #34: <unknown function> + 0x1d418b (0x55571125b18b in /homedir/envs/envname/bin/python)
frame #35: _PyObject_GC_NewVar + 0x23f (0x5557111a347f in /homedir/envs/envname/bin/python)
frame #36: PyTuple_New + 0x117 (0x5557111aaaa7 in /homedir/envs/envname/bin/python)
frame #37: <unknown function> + 0x1320b5 (0x5557111b90b5 in /homedir/envs/envname/bin/python)
frame #38: <unknown function> + 0x1321d1 (0x5557111b91d1 in /homedir/envs/envname/bin/python)
frame #39: <unknown function> + 0x131e4e (0x5557111b8e4e in /homedir/envs/envname/bin/python)
frame #40: <unknown function> + 0x1d7844 (0x55571125e844 in /homedir/envs/envname/bin/python)
frame #41: <unknown function> + 0x1ea6eb (0x5557112716eb in /homedir/envs/envname/bin/python)
frame #42: <unknown function> + 0x143e8a (0x5557111cae8a in /homedir/envs/envname/bin/python)
frame #43: _PyEval_EvalFrameDefault + 0x4c12 (0x5557111c0142 in /homedir/envs/envname/bin/python)
frame #44: _PyFunction_Vectorcall + 0x6c (0x5557111cba2c in /homedir/envs/envname/bin/python)
frame #45: _PyEval_EvalFrameDefault + 0x13ca (0x5557111bc8fa in /homedir/envs/envname/bin/python)
frame #46: _PyFunction_Vectorcall + 0x6c (0x5557111cba2c in /homedir/envs/envname/bin/python)
frame #47: _PyEval_EvalFrameDefault + 0x72c (0x5557111bbc5c in /homedir/envs/envname/bin/python)
frame #48: _PyFunction_Vectorcall + 0x6c (0x5557111cba2c in /homedir/envs/envname/bin/python)
frame #49: _PyEval_EvalFrameDefault + 0x72c (0x5557111bbc5c in /homedir/envs/envname/bin/python)
frame #50: _PyFunction_Vectorcall + 0x6c (0x5557111cba2c in /homedir/envs/envname/bin/python)
frame #51: _PyEval_EvalFrameDefault + 0x320 (0x5557111bb850 in /homedir/envs/envname/bin/python)
frame #52: _PyFunction_Vectorcall + 0x6c (0x5557111cba2c in /homedir/envs/envname/bin/python)
frame #53: _PyEval_EvalFrameDefault + 0x320 (0x5557111bb850 in /homedir/envs/envname/bin/python)
frame #54: _PyFunction_Vectorcall + 0x6c (0x5557111cba2c in /homedir/envs/envname/bin/python)
frame #55: <unknown function> + 0x144208 (0x5557111cb208 in /homedir/envs/envname/bin/python)
frame #56: _PyObject_CallMethodIdObjArgs + 0x169 (0x5557111d9419 in /homedir/envs/envname/bin/python)
frame #57: <unknown function> + 0x75187 (0x5557110fc187 in /homedir/envs/envname/bin/python)
frame #58: _PyEval_EvalFrameDefault + 0x3e3b (0x5557111bf36b in /homedir/envs/envname/bin/python)
frame #59: <unknown function> + 0x1d7c60 (0x55571125ec60 in /homedir/envs/envname/bin/python)
frame #60: PyEval_EvalCode + 0x87 (0x55571125eba7 in /homedir/envs/envname/bin/python)
frame #61: <unknown function> + 0x1dedaa (0x555711265daa in /homedir/envs/envname/bin/python)
frame #63: _PyEval_EvalFrameDefault + 0x5cd5 (0x5557111c1205 in /homedir/envs/envname/bin/python)
frame #62: <unknown function> + 0x144bf3 (0x5557111cbbf3 in /homedir/envs/envname/bin/python)

Error executing job with overrides: [''loader.num_workers=4', 'trainer.val_check_interval=2']
Traceback (most recent call last):
  File "/homedir/envs/envname/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1133, in _try_get_data
    data = self._data_queue.get(timeout=timeout)
  File "/homedir/envs/envname/lib/python3.10/queue.py", line 180, in get
    self.not_empty.wait(remaining)
  File "/homedir/envs/envname/lib/python3.10/threading.py", line 324, in wait
    gotit = waiter.acquire(True, timeout)
  File "/homedir/envs/envname/lib/python3.10/site-packages/torch/utils/data/_utils/signal_handling.py", line 66, in handler
    _error_if_any_worker_fails()
RuntimeError: DataLoader worker (pid 1076120) is killed by signal: Aborted.

Environment

Current environment

CUDA:
- GPU:
- NVIDIA RTX A6000
- NVIDIA RTX A6000
- available:         True
- version:           12.1
Lightning:
- lightning:         2.3.2
- lightning-utilities: 0.11.2
- pytorch-lightning: 2.3.1
- torch:             2.3.1
- torch-fidelity:    0.3.0
- torch-tb-profiler: 0.4.3
- torchaudio:        2.3.1
- torchmetrics:      1.4.0.post0
- torchvision:       0.18.1
- torchx:            0.6.0
System:
- OS:                Linux
- architecture:
- 64bit
- ELF
- processor:         x86_64
- python:            3.10.14
- release:           4.18.0-372.32.1.el8_6.x86_64

More info
No response

Hi @alexanderswerdlow
Can you show an example that produces this error? I am not aware of any serious issue regarding dataloading in Lightning.
From the error message, we can see that the dataloader worker failed, and that it had a cuda initialization error. Using any CUDA operations in your dataloading workers is not supported/recommended by PyTorch, so naturally we would expect to see issues with or without Lightning involved.
To be able to help you, I would need to see some evidence that the issue is caused by Lightning, and some code to work with to isolate the cause of it.

Thanks for responding! I don't have the time to continue to debug it at the moment and provide a full repro, but switching to the following works [only needed for the val dataloader]. There are no specific cuda operations in my dataloaders [and this bug happens with and without pin_memory=True]. I can confidently say it has happened with a simple torchvision imagenet dataset.
I should note it also happens on two different machines and on a newly installed conda env.
This strongly suggests it's a lightning issue. I spent a while digging into how lightning wraps dataloaders and it errors out around here, but again, not during the sanity check.
These issues [0, 1, 2] also seem to be discussing the same issue, specifically the last one that mentions this only occurring when passing a val dataloader.
Working [no worker] dataloader:
from torch.utils.data import default_collate
class SimpleDataLoader:
    def __init__(self, dataset, batch_size=1, collate_fn=default_collate, **kwargs):
        self.dataset = dataset
        self.batch_size = batch_size
        self.collate_fn = collate_fn
        self.idx = 0

    def __iter__(self):
        return self

    def __next__(self):
        if self.idx < len(self.dataset):
            batch = []
            for _ in range(self.batch_size):
                if self.idx >= len(self.dataset):
                    break
                batch.append(self.dataset[self.idx])
                self.idx += 1
            return self.collate_fn(batch)
        else:
            raise StopIteration

    def __len__(self):
        return (len(self.dataset) + self.batch_size - 1) // self.batch_size

Lightning does not wrap the dataloaders. It only injects a distributed sampler when you are using a torch DataLoader, because that sampler is needed for distributed training. For dataloaders with iterable datasets, also Lightning doesn't do anything, because the user has to take care of the implementation.
The issues you linked are open for the same reason, users are not able to provide the code that reproduces the problems, which means it's not possible to investigate only based on the error message. If we have that, it will be possible for me or someone from the community to determine the root cause, which is the first step.


How to feed from my existing dump1090 setup

Is there a way to configure my existing system that is already running a dump1090 setup to feed direct to adsb.lol without this container system. My setup is currently on a cloud Linux system that has atcp pipe to my pi via VPN and pulls from my pi via VPN because of Cox port blocking. It's loaded as a net-only dump1090 which thinks it's getting the data directly from the  SDR.
when I follow these instructions I get errors on the listen 30003 already in use

Hey, perhaps you can change your dump1090 port to a different value and expose a BEAST_IN port for the readsb container?
By setting READSB_NET_BEAST_INPUT_PORT=port in the docker-compose.yaml for the readsb service environment variables, and exposing the ports via ports:
Then if you configure your dump1090 to send beast to your port, you should be good & can take advantage of all the rest of the stack.

It tells me that tcp4 <IP_ADDRESS> port  unable to bind; already in use
On Wed, Feb 8, 2023, 7:24 AM katlol @.***> wrote:

Hey, perhaps you can change your dump1090 port to a different value and
expose a BEAST_IN port for the readsb container?
By setting READSB_NET_BEAST_INPUT_PORT=port in the docker-compose.yaml
for the readsb service environment variables, and exposing the ports via
ports:
Then if you configure your dump1090 to send beast to your port, you should
be good & can take advantage of all the rest of the stack.
—
Reply to this email directly, view it on GitHub
https://github.com/adsblol/feed/issues/3#issuecomment-1422596517, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A5FW5OSTMIYV7RLNKXLECMTWWONBVANCNFSM6AAAAAAUUXAOBM
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is what I get -- I have all these other services configured already in standalone feeds.... I'm just looking to feed into adsb-lol, but without a docker. I have had no luck getting a single one to run anything.
root@adsb1:/opt/adsblol/bin# adsblol-up
[ info] Removing old docker stack if it exists
[+] Running 8/8
⠿ Container adsblol        Removed                                                                                0.1s
⠿ Container mlathub        Removed                                                                                0.2s
⠿ Container tar1090        Removed                                                                                0.1s
⠿ Container vnstat         Removed                                                                                0.4s
⠿ Container watchtower     Removed                                                                                0.5s
⠿ Container autoheal       Removed                                                                                4.6s
⠿ Container readsb         Removed                                                                                0.0s
⠿ Network adsblol_default  Removed                                                                                0.1s
No stopped containers
[ info] Running docker-compose up with /opt/adsblol/cmdline.txt
[+] Running 7/9
⠿ Network adsblol_default                                           Created                                                                                0.2s
⠿ Container readsb                                                  Starting                                                                                1.3s
⠿ Container autoheal                                                Started                                                                                1.3s
⠿ Container watchtower                                              Started                                                                                1.2s
⠿ Container vnstat                                                  Started                                                                                0.6s
⠹ vnstat Published ports are discarded when using host network mode                                                                                0.0s
⠿ Container adsblol                                                 Created                                                                                0.1s
⠿ Container tar1090                                                 Created                                                                                0.1s
⠿ Container mlathub                                                 Created                                                                                0.0s
Error response from daemon: driver failed programming external connectivity on endpoint readsb (a938751a6786084d665040dfef510845df40adf2d06c8ac54d151a6dfb549c58): Error starting userland proxy: listen tcp4 <IP_ADDRESS>:30003: bind: address already in use

Apologies for not getting back to you here. Going to assume all is good. Feel free to reopen or get in touch on IRC if you need more help.


Add test cases for metrics config

What is the purpose of the change
Fixes #7808
Brief changelog
add a new metricConfigTest
Verifying this change

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[x] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[x] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #7809 (9a2d185) into master (fd4f765) will decrease coverage by 0.14%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #7809      +/-   ##
============================================
- Coverage     59.42%   59.28%   -0.15%
- Complexity      555      556       +1
============================================
  Files          1086     1088       +2
  Lines         43800    43800
  Branches       6391     6367      -24
============================================
- Hits          26030    25965      -65
- Misses        14900    14950      +50
- Partials       2870     2885      +15

Impacted Files
Coverage Δ

...a/org/apache/dubbo/rpc/filter/AccessLogFilter.java
28.35% <0.00%> (-50.75%)
:arrow_down:

...va/org/apache/dubbo/rpc/support/AccessLogData.java
53.16% <0.00%> (-37.98%)
:arrow_down:

.../dubbo/remoting/transport/MultiMessageHandler.java
80.00% <0.00%> (-20.00%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
43.47% <0.00%> (-19.57%)
:arrow_down:

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
76.92% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
68.96% <0.00%> (-13.80%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

.../apache/dubbo/rpc/protocol/AsyncToSyncInvoker.java
62.06% <0.00%> (-10.35%)
:arrow_down:

...dubbo/remoting/exchange/support/DefaultFuture.java
77.87% <0.00%> (-9.31%)
:arrow_down:

...mmon/threadpool/support/fixed/FixedThreadPool.java
80.00% <0.00%> (-7.50%)
:arrow_down:

... and 77 more

Continue to review full report at Codecov.

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

Closed no reply, reopen when it's ready.


PEP517 pyproject.toml prevents project-local module from being imported during build

Background
A project I maintain, cocotb, uses distutils to build several libraries and extension modules. Since there is quite a lot to it, we have most of build code partitioned off into a separate module which is imported by setup.py. As mentioned in the comment above the import, this is okay since the build module is included the MANIFEST.in. This currently works.
Problem
We have a pyproject.toml, but only for towncrier. I recently tried adding the following familiar lines necessary to make the project PEP517/518 compliant.
[build-system]
requires = ["setuptools", "wheel"]
build-backend = "setuptools.build_meta"

I get the following traceback

Using pip 20.2.2 from /home/kaleb/miniconda3/lib/python3.8/site-packages/pip (python 3.8)
Non-user install because site-packages writeable
Created temporary directory: /tmp/pip-ephem-wheel-cache-qzsqi0nm
Created temporary directory: /tmp/pip-req-tracker-tvat1n3p
Initialized build tracking at /tmp/pip-req-tracker-tvat1n3p
Created build tracker: /tmp/pip-req-tracker-tvat1n3p
Entered build tracker: /tmp/pip-req-tracker-tvat1n3p
Created temporary directory: /tmp/pip-install-pz90u3c3
Processing /home/kaleb/cocotb
  Created temporary directory: /tmp/pip-req-build-fq8xt9j6
  Added file:///home/kaleb/cocotb to build tracker '/tmp/pip-req-tracker-tvat1n3p'
    Created temporary directory: /tmp/pip-modern-metadata-quen39ee
    Running command /home/kaleb/miniconda3/bin/python /home/kaleb/miniconda3/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmppswbsf8w
    Traceback (most recent call last):
      File "/home/kaleb/miniconda3/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in <module>
        main()
      File "/home/kaleb/miniconda3/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
        json_out['return_val'] = hook(**hook_input['kwargs'])
      File "/home/kaleb/miniconda3/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 133, in prepare_metadata_for_build_wheel
        return hook(metadata_directory, config_settings)
      File "/home/kaleb/miniconda3/lib/python3.8/site-packages/setuptools/build_meta.py", line 174, in prepare_metadata_for_build_wheel
        self.run_setup()
      File "/home/kaleb/miniconda3/lib/python3.8/site-packages/setuptools/build_meta.py", line 158, in run_setup
        exec(compile(code, __file__, 'exec'), locals())
      File "setup.py", line 59, in <module>
        from cocotb_build_libs import get_ext, build_ext
    ModuleNotFoundError: No module named 'cocotb_build_libs'
    Preparing wheel metadata ... error

Reflection
It seems as though setuptools.build_meta does not have the same behavior as calling python setup.py ..., which is what I expect. Should build_meta handle the MANIFEST.in file? Or maybe just add the project root to sys.path? Is there some other build-backend entry point in setuptools I should be using? Is this bad practice in some way?

Add the following line before the offending import prevents an issue. I'm just wondering why this is necessary?
sys.path.append(path.dirname(__file__))

Yes, this is known and desirable for build isolation. If you want to add additional local files to your path during the build, you should modify the path explicitly. It is better to fail loudly in a way that's easy to fix than to have confusing error messages or fragile configurations that are very hard to debug.


Bot connection to lobby

Hello, i have questions about this node, for example, can i create lobby by bot and set bot as spectetare. If can, how?

The functionality is there, from what I can see. Just a question of looking at the various examples and figuring out how to adapt them.
The only thing probably not working, is the setLobbyTeamSlot, which is waiting for someone that cares to test and implement.
https://github.com/RJacksonm1/node-dota2/blob/master/handlers/lobbies.js#L26
https://github.com/RJacksonm1/node-dota2/blob/master/handlers/lobbies.js#L67
https://github.com/RJacksonm1/node-dota2/blob/master/handlers/lobbies.js#L148
https://github.com/RJacksonm1/node-dota2/blob/master/handlers/lobbies.js#L148
https://github.com/RJacksonm1/node-dota2/blob/master/handlers/lobbies.js#L284

Oh, and you will want to be using dev.
https://github.com/RJacksonm1/node-dota2/tree/dev
Posted too soon, previously.
The functionality is there, from what I can see. Just a question of looking at the various examples and figuring out how to adapt them.
The only thing probably not working, is the setLobbyTeamSlot, which is waiting for someone that cares to test and implement.
https://github.com/RJacksonm1/node-dota2/blob/dev/handlers/lobbies.js#L33
https://github.com/RJacksonm1/node-dota2/blob/dev/handlers/lobbies.js#L75
https://github.com/RJacksonm1/node-dota2/blob/dev/handlers/lobbies.js#L158
https://github.com/RJacksonm1/node-dota2/blob/dev/handlers/lobbies.js#L201
https://github.com/RJacksonm1/node-dota2/blob/dev/handlers/lobbies.js#L299
https://github.com/RJacksonm1/node-dota2/blob/dev/handlers/lobbies.js#L321
https://github.com/RJacksonm1/node-dota2/blob/dev/handlers/lobbies.js#L348

When you will finsih setLobbyTeamSlot? Its will be need me to teams generating

You should play around with it. You are likely not going to get far in making anything, without some critical thinking.
Have a read of this thread. Some of the way down it, I shared a compiled version the tools commonly used to figure out what exactly the client is doing.
https://github.com/RJacksonm1/node-dota2/issues/141
When you get stuck, come and open a thread specific to the issue you are encountering... and make sure to read all of the readme in the DEV branch (linked above)

This CMsg has been implemented in the mean time. It was split in a function for adding bots and one for setting player team. See joinPracticeLobbyTeam and addBotToPracticeLobby

Okay. Thank you, when i trying to set game mode or game name like this one, i have empty game mode and game name, what i doing wrong? (In the screen i setting just game_mode)

As far as I can see you're calling the function with the correct parameters. Does the data in the callback look something like {result: 1} ? If not, can you provide a little more context? Like how did you define Dota2, did you already establish a connection with Steam/the GC...?

Im not good in Eng, but i tried to understand all of your words))

A result of 2 is "fail" in Steam's enums.

Okay, thank you, ill check.
And can i ask question about function of bot? Can this bot after start game get info about this game? For example just a id of match

The bot can basically do anything you can do with the regular Reborn client. As for your example, can you post the entire argument set you're using?
No sweat about the english, you're doing fine :smile:

"you post the entire argument set you're using?" What you mean?
And after "npm install steam" i have an error with load

Fixed :)

If the issue is resolved, can you close it?

Crazy, i have some question about it and maybe pay job if your interest ofc

You can continue commenting on a closed issue, but I highly recommend trying your own hand at it and opening a new issue when you have a specific problem.


Unable to upload or access videos on S3

I am encountering an error running npx next-video sync while using s3.
+ Found 1 unprocessed video
- Processing file: Cross.mp4
✗ An unknown error occurred TypeError: Cannot read properties of undefined (reading 'provider')
    at createAsset (file:///E:/ScoreConnect/node_modules/next-video/dist/assets.js:40:27)
    at async newFileProcessor (file:///E:/ScoreConnect/node_modules/next-video/dist/cli/sync.js:68:24)
    at async Promise.all (index 0)
    at async Object.handler (file:///E:/ScoreConnect/node_modules/next-video/dist/cli/sync.js:94:24)

I have defined the provider in my next.config.mjs like so:
import withBundleAnalyzer from "@next/bundle-analyzer";
import withPlugins from "next-compose-plugins";
import { withNextVideo } from "next-video/process";
import { env } from "./env.mjs";

/**
 * @type {import('next').NextConfig}
 */
const nextConfig = {
  reactStrictMode: true,
  experimental: { instrumentationHook: true },
  images: {
    domains: ["avatars.githubusercontent.com", "lh3.googleusercontent.com"],
  },
};

const config = withPlugins([
  [withBundleAnalyzer({ enabled: env.ANALYZE })],
  [withNextVideo(nextConfig, {
    provider: 'amazon-s3',
    providerConfig: {
      'amazon-s3': {
        endpoint: 'https://s3.us-east-2.amazonaws.com',
      }
    }
  })]
]);

export default config;

And my access keys are in .env.local.
I'm not sure why provider is undefined, but I also seem to be unable to access anything at the /api/video endpoint, which returns this error.
TypeError: Cannot destructure property 'folder' of '(intermediate value)' as it is undefined.
    at getAssetPath (webpack-internal:///(rsc)/./node_modules/next-video/dist/assets.js:31:13)
    at async getAssetConfigPath (webpack-internal:///(rsc)/./node_modules/next-video/dist/assets.js:27:15)
    at async createAsset (webpack-internal:///(rsc)/./node_modules/next-video/dist/assets.js:41:29)
    at async handleRequest (webpack-internal:///(rsc)/./node_modules/next-video/dist/request-handler.js:47:17)
    at async GET (webpack-internal:///(rsc)/./node_modules/next-video/dist/request-handler.js:17:30)
    at async E:\ScoreConnect\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:62499

I had the same error, but before Cannot destructure property 'folder'   I have Failed to load next.config.js or next.config.mjs

shouldn't it be ?
const config = withPlugins([
  [withBundleAnalyzer({ enabled: env.ANALYZE })],
  [withNextVideo({
    provider: 'amazon-s3',
    providerConfig: {
      'amazon-s3': {
        endpoint: 'https://s3.us-east-2.amazonaws.com/',
      }
    }
  })]
], nextConfig);

check https://github.com/cyrilwanner/next-compose-plugins

let me know if it turns out to be something else.


Optionally include newer versions of Linaro/Ubuntu/Xen/Linux

This doesn't change the default build unless you set DISTROVER=vivid. The differences are:

Linaro 15.06 root filesystem
Includes a prebuilt Xen 4.5 binary (fixes #52), so for now the Xen build is skipped.
Ubuntu 15.04 (Vivid Vervet)
GCC 4.9.2
Linux 4.1.0 mainline
Config based on config-cubie2-docker
NTP daemon (fixes #48)
Some changes to make it easier to use a caching proxy for apt while building the image

Not done yet:

Update 1st-boot script for systemd compatibility
XAPI
blktap2 (?)
Check for performance regressions
Update README.md if the changes are considered useful

Tested with:

Ran make-linux-guest.sh and guest booted OK. Minor changes:
xenbr0 -> br0 (no XAPI yet)
trusty -> vivid (libpam-systemd post-install failed for trusty guest)
opam init
opam switch set 4.02.1
I tried 4.02.2 first but it failed due to https://github.com/mirage/mirage-platform/issues/137
opam install mirage
Clone mirage-www, build for Xen+DHCP and run
sudo reboot seems to work now (fixes #22)
SSH dropped once due to corruption. I vaguely remember this being related to TCP offload bugs?
#23 is not fixed

This is excellent news! I'd be happy to make Vivid the default (or even just drop the older version completely).

After PR #58 is merged I'll fix the merge conflicts here

Merged - please go ahead!

OK thanks. It's true that it complicates the scripts to support both versions but I thought that some people might want to stick with Trusty for a while longer, and also because it may help smooth future releases.
Do you know the specific reasons why 1st-boot was installed with order "S10", so that I can set the necessary dependencies in LSB format? (I'm new to such scripts)

I don't know about the xen/xapi bits (@djs55?) , but:

regenerating the SSH keys needs to happen before SSH starts
extending the partition could probably happen at any time, since nothing uses it during boot

On the other hand, it might be good to put /home in an LVM partition to make it easier to extend it.

OK, I've got something working. With a 1G home on LVM it's probably not necessary to resize the root FS partition from 2G to 3G anymore. Do you agree?

How much free space does it have? We want to leave a little (for logs, apt-get, etc), but won't need much with a separate /home.

iirc the size was increased to have room for installing additional packages after booting the image.

It has 800 MB free. I was just guessing that the main reason for growing it was for /home for source code, OPAM repo/switches/packages, etc.

Is there any other clean-up or refactoring required?
I tried "opam install xenctrl" but I found that the released version doesn't support Xen 4.5 (https://github.com/xapi-project/ocaml-xen-lowlevel-libs/issues/76) nor OCaml 4.02+.

The sunxi-mmc driver in ubuntu-vivid does not seem to work: http://sprunge.us/HfPE?text

I've built https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git branch linux-4.1.y (currently 4.1.3) and I'll try running it tomorrow.

For #39, I tested dom0_mem=512M,max=768M and changed target_kb to 650000 but it did not seem to have any effect on the output of vmstat (?). However, when I tried setting dom0_mem=768M,max=768M it worked fine, but left only 95MB free for guests according to "xl info".

xapi-project/ocaml-xen-lowlevel-libs#76 was closed so I've opened a new issue for the opam xenctrl problem in xapi-project/ocaml-xen-lowlevel-libs#78

Hi; Apologies this has sat for so long. Now the repo has been refreshed to use Alpine for dom0, I guess it would need considerable rewriting to be applicable. Happy to take a look (and I promise not to leave it sitting for over a year!) if you'd like to update scripts to enable alternatives to Alpine dom0 and reopen the PR, but in the meantime, I'll close this one. Thanks!


lighten searchbar

Is your feature request related to a problem? Please describe.
search bar on iOS 12.4 appears lighter than framework7 search bar.
Describe the solution you'd like
Change searchbar input bgcolor to #f0f0f0 as per iOS.
Describe alternatives you've considered
none
Additional context
Lighten searchbar to make more identical to iOS

Please, just set it to anything you like in custom styles. Defaults are defaults here, it is also related to translucent navbar


Added AeRO

@wildcard27 This domain does not belong to a university, nor to a college. I have to close the request without merging. Please ensure that you are familiar with this repository rules located at the bottom of this page before submitting a new request.


Packages from environment.yml not installed into python3 env

I have a directory with Python 3 notebooks, and I cannot directly run them even though the dependencies are listed in the corresponding environment.yml. This is not a big problem, since I can just instruct users to install them again, but it's a bit annoying.
This is the repository:
https://github.com/Juanlu001/poliastro/blob/master/environment.yml
And these are the available packages in each environment:
https://gist.github.com/Juanlu001/0abb2f5a09d8b549da08

I'm having the same problem. This is my repository:
https://github.com/maxalbert/paper-supplement-nanoparticle-sensing
The corresponding binder is here:
http://mybinder.org/repo/maxalbert/paper-supplement-nanoparticle-sensing
If I am not mistaken then the problem seems to be that the conda environment created by binder is somehow not activated in the docker container (even though the log file claims that it is). For example, when I open one of my notebooks and run !conda env list in a new cell, this is the output I get:
# conda environments:
#
binder                   /home/main/anaconda2/envs/binder
python3                  /home/main/anaconda2/envs/python3
root                  *  /home/main/anaconda2

The binder environment is the one created from my environment.yml file, but the root environment is the one that is activated. Any chance to fix this? Many thanks!

@Juanlu001 @maxalbert thanks for opening up this issue. The environment.yml handling that we're doing right now has definitely been a source of confusion, so we really should add some documentation here.
The immediate fix to your problem is to explicitly specify the Python version you'd like to use inside of your environment.yml file (just like here: https://github.com/binder-project/example-conda-environment/blob/master/environment.yml). With that line included, the default kernel will be Python 3.4, and the packages in the file will be available.
If you check out how we handle the files here: https://github.com/binder-project/binder/blob/master/binder/app.py#L204, you'll see that we aren't explicitly source activateing the environment, because that doesn't behave well during the Docker build process, but we are manipulating the path in such a way that the binder environment the first environment searched for packages.
From inside the binder-project/example-conda-environment binder:
import sys
sys.path

['',
 '/home/main/anaconda2/envs/binder/lib/python34.zip',
 '/home/main/anaconda2/envs/binder/lib/python3.4',
 '/home/main/anaconda2/envs/binder/lib/python3.4/plat-linux',
 '/home/main/anaconda2/envs/binder/lib/python3.4/lib-dynload',
 '/home/main/anaconda2/envs/binder/lib/python3.4/site-packages/setuptools-20.7.0-py3.4.egg',
 '/home/main/anaconda2/envs/binder/lib/python3.4/site-packages',
 '/home/main/anaconda2/envs/binder/lib/python3.4/site-packages/IPython/extensions',
 '/home/main/.ipython']

Thank you @andrewosh, adding python=3.4 to environment.yml indeed fixed the issue. Also your explanation on the file handling was spot on, since !conda list won't show the packages available from the path and that can be confusing. Closing!


ci: update bot tokens to read/write accesses

Use this URL to perform PR review https://github.com/customerio/customerio-ios/compare/levi/help-prevent-breaking-changes...levi/bot-tokens-update
Updating CI bot tokens. We have a bot that has read-only access to the repo and another bot with read/write access. This PR updates the CI tasks to use these 2 different bots in the correct scenarios.
Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

[x] Merge https://github.com/customerio/customerio-ios/pull/137
[x] Assign members of your team to review the pull request.
[x] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
[x] Wait until the pull request has been reviewed and approved by a teammate
[ ] After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request. A bot will squash and merge the pull request for you after the label is added.

Hey, there @levibostian 👋🤖. I'm a bot here to help you.
This project uses a special format for pull requests titles. Don't worry, it's easy!
This pull request title should be in this format:
<type>: short description of change being made

If your pull request introduces breaking changes to the code, use this format:
<type>!: short description of breaking change

where <type> is one of the following:

feat: - A new feature is being added by this pull request.

fix: - A bug is being fixed by this pull request.

docs: - This pull request is making documentation changes, only.

refactor: - A change was made that doesn't fix a bug or add a feature.

test: - Adds missing tests or fixes broken tests.

style: - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc)

perf: - Changes improve performance of the code.

build: - Changes to the build system (maven, npm, gulp, etc)

ci: - Changes to the CI build system (Travis, GitHub Actions, Circle, etc)

chore: - Other changes to project that don't modify source code or test files.

revert: - Reverts a previous commit that was made.

Examples

```
feat: edit profile photo
refactor!: remove deprecated v1 endpoints
build: update npm dependencies
style: run formatter
```

Need more examples? Want to learn more about this format? Check out the official docs.
Note: If your pull request does multiple things such as adding a feature and makes changes to the CI server and fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

:tada: This PR is included in version 1.1.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Urgent] Reduce load on CI due to excessive log flood

Description
as title

After merging this PR, I found that my PR #17400 fails to build on Windows, though I have retriggered CI several times.


HBASE-27092 Regionserver table on Master UI is broken

JIRA: HBASE-27092.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
6m 37s
master passed

+1 :green_heart:
spotless
0m 49s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 21s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
spotless
0m 49s
patch has no errors when running spotless:check.

 For Normal regionservers, is it good to display Live instead? Just like datanodes state, it would be live and decommissioned. WDYT?

@tomscut the change looks good. For Normal regionservers, is it good to display Live instead? Just like datanodes state, it would be live and decommissioned. WDYT?

I planned to set the status to Live, but found that the Live RegionServers in hbase included the Decommissioned RegionServers. If it is set to Live, there is ambiguity.


Fix early close time.

Convert the early close time 14:05 CET into local time in WET, i.e. 13:05.
To fix #135.

I can't download the logs of the failing tests at this moment. But I reckon my simple code change didn't consider that the early closing times for past years <= 2019 were correct, but we're affected by my change as well. I will try to fix, but any help from more regular project contributers would be appreciated.

Hey @jenskeiner - I agree that times should be in the local time of the market, thanks for catching this and the PR!
Can you elaborate on why the logs are inaccessible? Is there a permissions issue on our side or something on your end?
If it helps - here are is the failing test output:
2020-07-06T11:50:13.8235893Z ======================================================================
2020-07-06T11:50:13.8236316Z ERROR: test_minute_to_session_label (tests.test_xlis_calendar.XLISCalendarTestCase)
2020-07-06T11:50:13.8237110Z ----------------------------------------------------------------------
2020-07-06T11:50:13.8237254Z Traceback (most recent call last):
2020-07-06T11:50:13.8238824Z   File "/home/runner/work/trading_calendars/trading_calendars/tests/test_trading_calendar.py", line 433, in test_minute_to_session_label
2020-07-06T11:50:13.8239069Z     direction="none"),
2020-07-06T11:50:13.8239310Z   File "/home/runner/work/trading_calendars/trading_calendars/trading_calendars/trading_calendar.py", line 831, in minute_to_session_label
2020-07-06T11:50:13.8239496Z     Given a minute, get the label of its containing session.
2020-07-06T11:50:13.8239718Z   File "/home/runner/work/trading_calendars/trading_calendars/trading_calendars/trading_calendar.py", line 872, in minute_to_session_label
2020-07-06T11:50:13.8239941Z     raise ValueError("The given dt is not an exchange minute!")
2020-07-06T11:50:13.8240086Z ValueError: The given dt is not an exchange minute!
2020-07-06T11:50:13.8240187Z
2020-07-06T11:50:13.8240322Z ======================================================================
2020-07-06T11:50:13.8240458Z FAIL: test_half_days (tests.test_xlis_calendar.XLISCalendarTestCase)
2020-07-06T11:50:13.8240861Z ----------------------------------------------------------------------
2020-07-06T11:50:13.8241001Z Traceback (most recent call last):
2020-07-06T11:50:13.8241211Z   File "/home/runner/work/trading_calendars/trading_calendars/tests/test_trading_calendar.py", line 929, in test_half_days
2020-07-06T11:50:13.8241381Z     half_day + self.TIMEDELTA_TO_EARLY_CLOSE,
2020-07-06T11:50:13.8241788Z AssertionError: Timestamp('2010-12-24 13:05:00+0000', tz='UTC') != Timestamp('2010-12-24 14:05:00+0000', tz='Europe/Lisbon')
2020-07-06T11:50:13.8242354Z     "Timestamp('2010-12-24 13:05:00+0000', tz='UTC') != Timestamp('2010-12-24 14:05:00+0000', tz='Europe/Lisbon')" = '%s != %s' % (safe_repr(Timestamp('2010-12-24 13:05:00+0000', tz='UTC')), safe_repr(Timestamp('2010-12-24 14:05:00+0000', tz='Europe/Lisbon')))
2020-07-06T11:50:13.8243445Z     "Timestamp('2010-12-24 13:05:00+0000', tz='UTC') != Timestamp('2010-12-24 14:05:00+0000', tz='Europe/Lisbon')" = self._formatMessage("Timestamp('2010-12-24 13:05:00+0000', tz='UTC') != Timestamp('2010-12-24 14:05:00+0000', tz='Europe/Lisbon')", "Timestamp('2010-12-24 13:05:00+0000', tz='UTC') != Timestamp('2010-12-24 14:05:00+0000', tz='Europe/Lisbon')")
2020-07-06T11:50:13.8243919Z >>  raise self.failureException("Timestamp('2010-12-24 13:05:00+0000', tz='UTC') != Timestamp('2010-12-24 14:05:00+0000', tz='Europe/Lisbon')")
2020-07-06T11:50:13.8244075Z
2020-07-06T11:50:13.8244156Z
2020-07-06T11:50:13.8244285Z ======================================================================
2020-07-06T11:50:13.8244434Z FAIL: test_is_open_on_minute (tests.test_xlis_calendar.XLISCalendarTestCase)
2020-07-06T11:50:13.8244744Z ----------------------------------------------------------------------
2020-07-06T11:50:13.8244881Z Traceback (most recent call last):
2020-07-06T11:50:13.8245109Z   File "/home/runner/work/trading_calendars/trading_calendars/tests/test_trading_calendar.py", line 274, in test_is_open_on_minute
2020-07-06T11:50:13.8245285Z     self.assertTrue(self.calendar.is_open_on_minute(close_minute_utc))
2020-07-06T11:50:13.8245423Z AssertionError: False is not true
2020-07-06T11:50:13.8245777Z     'False is not true' = self._formatMessage('False is not true', "%s is not true" % safe_repr(False))
2020-07-06T11:50:13.8246080Z >>  raise self.failureException('False is not true')
2020-07-06T11:50:13.8246213Z
2020-07-06T11:50:13.8246273Z
2020-07-06T11:50:13.8246401Z ======================================================================
2020-07-06T11:50:13.8246548Z FAIL: test_next_prev_minute (tests.test_xlis_calendar.XLISCalendarTestCase)
2020-07-06T11:50:13.8246866Z ----------------------------------------------------------------------
2020-07-06T11:50:13.8247005Z Traceback (most recent call last):
2020-07-06T11:50:13.8247333Z   File "/home/runner/work/trading_calendars/trading_calendars/tests/test_trading_calendar.py", line 395, in test_next_prev_minute
2020-07-06T11:50:13.8247563Z     self.calendar.previous_minute(hour_after_close)
2020-07-06T11:50:13.8247956Z AssertionError: Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')
2020-07-06T11:50:13.8248487Z     "Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')" = '%s != %s' % (safe_repr(Timestamp('1992-12-31 13:05:00+0000', tz='UTC')), safe_repr(Timestamp('1992-12-31 12:05:00+0000', tz='UTC')))
2020-07-06T11:50:13.8249139Z     "Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')" = self._formatMessage("Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')", "Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')")
2020-07-06T11:50:13.8249577Z >>  raise self.failureException("Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')")
2020-07-06T11:50:13.8249732Z
2020-07-06T11:50:13.8249795Z
2020-07-06T11:50:13.8249924Z ======================================================================
2020-07-06T11:50:13.8250075Z FAIL: test_next_prev_open_close (tests.test_xlis_calendar.XLISCalendarTestCase)
2020-07-06T11:50:13.8250392Z ----------------------------------------------------------------------
2020-07-06T11:50:13.8250529Z Traceback (most recent call last):
2020-07-06T11:50:13.8250747Z   File "/home/runner/work/trading_calendars/trading_calendars/tests/test_trading_calendar.py", line 357, in test_next_prev_open_close
2020-07-06T11:50:13.8250914Z     next_close, previous_close
2020-07-06T11:50:13.8251115Z   File "/home/runner/work/trading_calendars/trading_calendars/tests/test_trading_calendar.py", line 296, in _verify_minute
2020-07-06T11:50:13.8251274Z     next_close_answer
2020-07-06T11:50:13.8251655Z AssertionError: Timestamp('1992-12-31 12:05:00+0000', tz='UTC') != Timestamp('1992-12-31 13:05:00+0000', tz='UTC')
2020-07-06T11:50:13.8252189Z     "Timestamp('1992-12-31 12:05:00+0000', tz='UTC') != Timestamp('1992-12-31 13:05:00+0000', tz='UTC')" = '%s != %s' % (safe_repr(Timestamp('1992-12-31 12:05:00+0000', tz='UTC')), safe_repr(Timestamp('1992-12-31 13:05:00+0000', tz='UTC')))
2020-07-06T11:50:13.8252842Z     "Timestamp('1992-12-31 12:05:00+0000', tz='UTC') != Timestamp('1992-12-31 13:05:00+0000', tz='UTC')" = self._formatMessage("Timestamp('1992-12-31 12:05:00+0000', tz='UTC') != Timestamp('1992-12-31 13:05:00+0000', tz='UTC')", "Timestamp('1992-12-31 12:05:00+0000', tz='UTC') != Timestamp('1992-12-31 13:05:00+0000', tz='UTC')")
2020-07-06T11:50:13.8253274Z >>  raise self.failureException("Timestamp('1992-12-31 12:05:00+0000', tz='UTC') != Timestamp('1992-12-31 13:05:00+0000', tz='UTC')")
2020-07-06T11:50:13.8253424Z
2020-07-06T11:50:13.8253486Z
2020-07-06T11:50:13.8253617Z ======================================================================
2020-07-06T11:50:13.8253774Z FAIL: test_open_and_close_for_session (tests.test_xlis_calendar.XLISCalendarTestCase)
2020-07-06T11:50:13.8254094Z ----------------------------------------------------------------------
2020-07-06T11:50:13.8254232Z Traceback (most recent call last):
2020-07-06T11:50:13.8254454Z   File "/home/runner/work/trading_calendars/trading_calendars/tests/test_trading_calendar.py", line 780, in test_open_and_close_for_session
2020-07-06T11:50:13.8254629Z     self.assertEqual(close_answer, found_close)
2020-07-06T11:50:13.8255003Z AssertionError: Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')
2020-07-06T11:50:13.8255532Z     "Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')" = '%s != %s' % (safe_repr(Timestamp('1992-12-31 13:05:00+0000', tz='UTC')), safe_repr(Timestamp('1992-12-31 12:05:00+0000', tz='UTC')))
2020-07-06T11:50:13.8256236Z     "Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')" = self._formatMessage("Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')", "Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')")
2020-07-06T11:50:13.8256915Z >>  raise self.failureException("Timestamp('1992-12-31 13:05:00+0000', tz='UTC') != Timestamp('1992-12-31 12:05:00+0000', tz='UTC')")
2020-07-06T11:50:13.8257066Z
2020-07-06T11:50:13.8257128Z
2020-07-06T11:50:13.8257256Z ======================================================================
2020-07-06T11:50:13.8257408Z FAIL: test_session_closes_in_range (tests.test_xlis_calendar.XLISCalendarTestCase)
2020-07-06T11:50:13.8257728Z ----------------------------------------------------------------------
2020-07-06T11:50:13.8257870Z Traceback (most recent call last):
2020-07-06T11:50:13.8258095Z   File "/home/runner/work/trading_calendars/trading_calendars/tests/test_trading_calendar.py", line 799, in test_session_closes_in_range
2020-07-06T11:50:13.8258428Z     found_closes, self.answers['market_close']
2020-07-06T11:50:13.8258879Z   File "/opt/hostedtoolcache/Python/2.7.18/x64/lib/python2.7/site-packages/pandas/util/testing.py", line 1049, in assert_series_equal
2020-07-06T11:50:13.8259202Z     check_less_precise, obj='{0}'.format(obj))
2020-07-06T11:50:13.8259440Z   File "pandas/src/testing.pyx", line 58, in pandas._testing.assert_almost_equal (pandas/src/testing.c:3887)
2020-07-06T11:50:13.8259697Z   File "pandas/src/testing.pyx", line 147, in pandas._testing.assert_almost_equal (pandas/src/testing.c:2769)
2020-07-06T11:50:13.8260164Z   File "/opt/hostedtoolcache/Python/2.7.18/x64/lib/python2.7/site-packages/pandas/util/testing.py", line 915, in raise_assert_detail
2020-07-06T11:50:13.8260346Z     raise AssertionError(msg)
2020-07-06T11:50:13.8260479Z AssertionError: Series are different
2020-07-06T11:50:13.8260547Z
2020-07-06T11:50:13.8260671Z Series values are different (0.02663 %)

Thanks @gerrymanoim. Not sure what‘s behind the failure to download the logs. I just see an error when I try to expand the corresponding section. Anyway, I‘m able to run the tests locally now, so will see if I can fix and update the PR.

You should also be able to get the logs in the menu on the side:

I think I've fixed the unit tests after adjusting the early close time to 13:05 (in WET). Please review.
The early close times (basically only New Year's Eve) before 2002, i.e. from before the acquisition by Euronext, are likely incorrect, but may have been incorrect before. I don't have any historical records or other sources to confirm.
Things to consider:

The predecessor of the current XLIS exchange which is part of Euronext was BVLP and was formed from two exchanges, one in Porto and one in Lisbon, in the 1990s. This means they may not have observed the same early close times that this package would currently list for XLIS: see (in Portugese) https://web.archive.org/web/20110723192615/http://www.millenniumbcp.pt/site/conteudos/40/article.jhtml?articleID=375367.
Mainland Portugal had changed the time zone from WET to CET between 1992 and 1996. Therefore, the early close times on New Year's Eve for the years 1992 to 1995 probably need to be adjusted if they are meant to be interpreted relative to the local time zone. The package currently doesn't consider this.

Might be a cleaner solution to cut off support for the old millennium. Personally, I'm only interested in most recent years and onward.

@jenskeiner - this makes sense to me, understood on the caveats. Thanks for the PR!


[QUERY] Pagination with cosmos - spring data. How to use the continuation token

Query/Question
How to make the pagination work with continuation token. Seems like the offset or the page is not honored with continuation token. When using continuation token, the records are retrieve from the previous rowid (if I am not wrong). And, the limit / count is honored.
Service (Pageable) -
CosmosPageRequest.of(offset, page, limit, continuationToken, sort)
or
CosmosPageRequest.of(page, limit, continuationToken, sort)
Above code does not work for page different than the previous end Record id. If continuationtoken stopped at row id 2, it starts again from rowid:2, no matter what I provide in offset or page values.
Also, how to paginate to a before page, when continuation token start at rowid:2, how to move to previous records - 0-2 (with limit 2).
If, I have to do everything by using @Query, do I have to have a separate query with count for counting the records to find the total count ?
Repo -
Page<NotesDO> findByPartIdAndOtherIdAndTypeAndTextContaining(String partId, String otherId, String type, String filter, Pageable page);
Why is this not a Bug or a feature Request?
Not sure, how this works.
Setup (please complete the following information if applicable):

OS: [macOs]
IDE: [Eclipse]
Library/Libraries: [ com.azure:azure-spring-data-cosmos:LATEST , com.azure:azure-cosmos:4.39.0]

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Query Added
[x] Setup information Added

@kushagraThapar could you please handle this issue?

@dsrini-open can you please provide some sample code of how you are trying to achieve pagination with offset? How are you trying to achieve pagination, via a Template or Repository?
Yes I believe you will have to perform a separate query to get the count. In a repository setup something like one of the following:
`Long countByTitleAndIntValue(String title, int intValue);
@Query(value = "select value count(1) from c where c.title = @title")
long countByQueryWithPrimitive(@Param("title") String title);`

@trande4884  - For offset I was trying to use the PageRequest object as below -
CosmosPageRequest.of(offset, page, limit, continuationToken, sort)
I am using the spring data without @Query as my previous example, and it works but the following code does only work from the continuation marker to X limit records (page/offset supplied above is pretty much useless, or not honored).
Page<NotesDO> findByPartIdAndOtherIdAndTypeAndTextContaining(String partId, String otherId, String type, String filter, Pageable page);
Also, with continuationToken method as above - I still see higher RUs - for page 2 of 3 records I see higher RUs (upto a total record count of the container)

For your use of CosmosPageRequest, if you pass in a Continuation Token that will be all that is used to get the next page of results. If you want to use offset and page than do not pass in a continuation token with your CosmosPageRequest.
Here is an example of using offset and then getting the next/previous pages:
final Criteria criteria = Criteria.getInstance(CriteriaType.IS_EQUAL, "firstName",
            Collections.singletonList(FIRST_NAME), Part.IgnoreCaseType.NEVER);
        final PageRequest pageRequest = CosmosPageRequest.of(1, 0, PAGE_SIZE_2,
            null, Sort.by(ASC, "id"));
        final CosmosQuery query = new CosmosQuery(criteria).with(pageRequest).with(pageRequest.getSort());
        final Page<PartitionPerson> page = cosmosTemplate.paginationQuery(query, PartitionPerson.class, containerName);

        final CosmosQuery query2 = new CosmosQuery(criteria).with(page.nextPageable()).with(page.nextPageable().getSort());
        final Page<PartitionPerson> nextPage = cosmosTemplate.paginationQuery(query2, PartitionPerson.class, containerName);

        final CosmosQuery query3 = new CosmosQuery(criteria).with(page.previousPageable()).with(page.previousPageable().getSort());
        final Page<PartitionPerson> prevPage = cosmosTemplate.paginationQuery(query3, PartitionPerson.class, containerName);


After open of the feedback dialog, background of other layered component is invisible.

After open of the feedback dialog, background of other layered component is invisible.
Other layered component use also div with css class .mat-dialog-container.
feedback-dialog component set "mat-dialog-container" invisible.
https://github.com/RickonChen/feedback/blob/190e9fb6e5ddaa2fab372fbf3cb9a6d0e041e661/src/app/feedback/feedback-dialog/feedback-dialog.component.css
/deep/ .mat-dialog-container {
padding: 0;
overflow: visible;
background-color: rgba(255, 255, 255, 0);
box-shadow: initial;
}
Expected: after closing feedback-dialog , component restore default css for .mat-dialog-container

Hi @reyzenkind , version 1.1.8 or newer should fix the issue you met


Modernize recipe

Change windows compiler to MSVC
Ensure no crates(2).toml files are generated
Build using fat LTO for speed and size improvement
Directly strip the binary instead of a post-processing step

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

        Hi! This is the friendly automated conda-forge-linting service.

        I wanted to let you know that I linted all conda-recipes in your             PR (```recipe/meta.yaml```) and found some lint.

        Here's what I've got...

For recipe/meta.yaml:

This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see https://github.com/conda-forge/conda-forge.github.io/issues/2102.
You are setting MACOSX_SDK_VERSION below c_stdlib_version, in conda_build_config.yaml which is not possible! Please ensure MACOSX_SDK_VERSION is at least c_stdlib_version (you can leave it out if it is equal).
If you are not setting c_stdlib_version yourself, this means you are requesting a version below the current global baseline in conda-forge (10.13). If this is the intention, you also need to override c_stdlib_version and MACOSX_DEPLOYMENT_TARGET locally.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.


Add Coordinates Module and Tests

Partially Fixes #121

@shreyasbapat

Thanks for reviewing. I will do these changes :)

Thanks a lot for the efforts! :)

With your permission, I added an extra commit in your PR

Thanks @rishi-s8 :)

Happy to do this.. :)


Parse.Push did not called in a afterSave Block

Describe your issue in as much detail as possible.
Push query and Push notification are not called in a cloud code afterSave block
Steps to reproduce
CLOUD FUNCTION AFTERSAVE:
Parse.Cloud.afterSave("schedule",function(req,res){
  console.log("does my after send");
  var user = req.object.relation("requestUser").query();
  user.notContainedIn("objectId",req.object.get("rejectUserList"));
  var pushQuery = new Parse.Query(Parse.Installation);
  pushQuery.matchesQuery('user',user);
  Parse.Push.send({
    where: pushQuery ,
    data: {
      alert: 'Test',
      //sound: 'default'
    }
  }, {
    useMasterKey: true,
    success: function(object) {
      // Push sent!
      console.log(object);
      res.success();
    },
    error: function(error) {
      console.log(error.message);
      res.error(error.message);
      // There was a problem :(
    }
  });
});

After Save the object , this is the out put i got in the logs
does my after send
verbose: {
"response": {
"updatedAt": "2016-07-14T18:07:49.002Z"
}
}
Then following with res of object related log saying the object has been updated !
BUT , No log to help me find out why my push is not send/called

Big Thanks advanced

Parse ios are not working as well <_<   However I cant pin down the issue Yet

Hi ,
did you upload the p12 certificate to the server and configure push adapter which points to it?
can you please share your parse-server config file or index.js file ?
P.S. I don't know if you use it or not but the push notifications wiki is well documented https://github.com/ParsePlatform/parse-server/wiki/Push

Yes I did  , First I use the Parse server push config , then I was able to successful push the notification through Dashboard  ,no luck on the Parse Cloud code afterSave block   ,   Then I setup the SNS push Adapter  , again no luck

I am wondering if Parse Dashboard using javascript api or rest ?

I am digging to Parse dashboard to find out how they send notification

I need help  T_T

afterSave() blocks do not have a res (or response) parameter by the way. I highly recommend that you use Promises instead of success/error callbacks in order to make your code easier to follow.

Thank you hramos  !
I will give a give latter on today

@hramos
So i did try to the Promises instead
 Parse.Cloud.afterSave("schedule",function(req){     console.log("does my after send");     var user = req.object.relation("requestUser").query();     user.notContainedIn("objectId",req.object.get("rejectUserList"));     var pushQuery = new Parse.Query(Parse.Installation);     pushQuery.matchesQuery('user',user);     Parse.Push.send({       where:{         pushQuery       },       data:{         alert:"promisi test",         sound: 'default'       }     },{useMasterKey: true}).then(       function () { //i get log saying success , However I do the Push is failed //Nothing more ! There is no error warning or logs           console.log("success");       },function (error) {         console.log(error.message);       }     ) });

why is git wont read that as CODE  >_>

So before The dashBoard shows sending  , now its shows failed LOL

Help please  ! The lack of doc on Push Promises  really make me confused

Hi @lifeisfunny . I will try to do it on my own and will let you know soon as i have an answer...

Hi @lifeisfunny. I tested it and it worked on my side so i don't see any issues with parse server (i am using the latest version 2.2.16)
I suggest you to do the following:
first try to send a push without any where conditions. Just send it to all the installations and see if its working for you.
The code on my side is the following:
Parse.Cloud.afterSave("GameScore",function(request){

	console.log("after save triggered");

	var query = new  Parse.Query(Parse.Installation);
	query.exists("deviceToken");

	var payload = {
		alert: "after save push"
	};

	Parse.Push.send({
		where: query,
		data: payload
	}, {
		useMasterKey : true,
		success: function() {
			console.log("push sent");
		},
		error: function(error) {
			console.log("push failed " + error.message);
		}
	});

});

Please let me know if it works for  you..

and this is the "Promise" way :)
Parse.Cloud.afterSave("GameScore", function (request) {

	console.log("after save triggered");

	var query = new Parse.Query(Parse.Installation);
	query.exists("deviceToken");

	var payload = {
		alert: "after save push"
	};

	Parse.Push.send({
		data: payload,
		where: query
	},
	{useMasterKey : true})
	.then(function(){
		console.log("Push sent");
	},function(error){
		console.log("Error while trying to send push " +  error.message);
	});
});

@ranhsd   yo Thanks man   I will give a try right now    ;)

@ranhsd  I still got no luck on my local test machine , should i give a try on the aws server ???
I got return success but push status stay on sending like before

No Luck
I gonna update to aws and give a try again   see how that works

I think it's best to move this off to Stack Overflow. We are using GitHub issues to track issues in Parse Server itself, and Stack Overflow is better suited for code-level questions such as this. You can also learn more about Promises at https://parse.com/docs/js/guide#promises
For code-level and/or implementation-related questions or technical support, please refer to Stack Overflow.

I dont get any syntax  error  , I do get a push success log after the success function .


Move CRS values away from magic strings

The ongoing quest to remove magic values continues... will merge this now as no major code changes but welcome thoughts if you've any @ox-baloo

Ideally should only be defined once in the source code - perhaps in utility.py? - but better than what we had before :)


add endpoint mode in service pretty

fixes #26905
- What I did

make endpoint mode show in docker service inspect xxx --pretty
fix some typos

Signed-off-by: allencloud<EMAIL_ADDRESS>

LGTM

code LGTM, but needs changes to documentation as well; a quick search;

docs/reference/commandline/service_inspect.md#inspect-a-service-using-pretty-print
docs/swarm/swarm-tutorial/inspect-service.md
docs/swarm/swarm-tutorial/rolling-update.md

PTAL @thaJeztah Updated. 😄


Adding DefaultValue code generation

See Issue #1670.
This deals with fixed default values only. There are also expressions which are returned in the metadata - e.g. newid() and getdate() - which I will address separately.

:shipit:

Checked in - commit 1647b7f.


No way to interrupt direnv when running it takes ages

What did you expect to happen?
I'm using direnv together with Nix in order to provide all my tools in a console. This is great that doom automatically runs direnv when using the direnv module, but sometimes I'd like to be able to cancel this. The reason is that it can sometimes take ages to compile a given direnv environment, and sometimes I just want to edit quickly a file. In the terminal I can press C-c to stop direnv, would it be possible to provide a similar command inside doom?
Steps to reproduce:

Install and configure direnv. For example, I use nix and home-manager, configured using:

{ config, pkgs, ... }:
# https://rycee.gitlab.io/home-manager/
{
  # Let Home Manager install and manage itself.
  programs.home-manager.enable = true;

  # Direnv
  programs.bash.enable = true;
  programs.direnv.enable = true;
  programs.direnv.enableNixDirenvIntegration = true;
}

Create a .envrc that takes some time to be generated, for example using echo "sleep 20" > .envrc (in real-life, this comes from shell.nix files that takes lots of time to build the packages)
Allow that folder to use direnv, by running direnv allow
Try to open with doom-emacs, with the module :tool direnv enabled, the file .envrc for example. Note that I think that you need to run emacs from another folder than the one where you created your direnv environment, otherwise I don't think it runs direnv.

Note that pressing C-g does not just stop direnv, but it cancel the whole file openning.
System information:

```
SYSTEM  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      /run/current-system/sw/bin/bash
        uname      Linux 5.4.66 #1-NixOS SMP Thu Sep 17 11:47:56 UTC 2020 x86_64
        path       (/run/wrappers/bin ~/.nix-profile/bin /etc/profiles/per-user/$USER/bin /nix/var/nix/profiles/default/bin /run/current-system/sw/bin /nix/store/ih9bwzlkp0r5p999fnrdx1m1xkm0kfb6-emacs-26.3/libexec/emacs/26.3/x86_64-pc-linux-gnu/)
EMACS   dir        ~/Documents/Informatique/Emacs_configurations/2020_doom/dot_emacs_dot_d/
        version    26.3
        build      nov. 03, 2020
        buildopts  --prefix=/nix/store/ih9bwzlkp0r5p999fnrdx1m1xkm0kfb6-emacs-26.3 --disable-build-details --with-modules --with-x-toolkit=gtk3 --with-xft CFLAGS=-DMAC_OS_X_VERSION_MAX_ALLOWED=101200
        features   XPM JPEG TIFF GIF PNG RSVG SOUND DBUS GSETTINGS GLIB NOTIFY LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD
        traits     (server-running envvar-file)
DOOM    dir        ~/Documents/Informatique/Emacs_configurations/2020_doom/dot_doom_dot_d/
        version    2.0.9
        build      grafted, HEAD -> develop, origin/develop, origin/HEAD 807f00a 2020-11-02 23:56:43 -0500
        elc-files  0
        modules    (:completion company (ivy +fuzzy +prescient +icons) :ui doom doom-dashboard doom-quit (emoji +unicode) hl-todo minimap modeline ophints (popup +defaults) vc-gutter vi-tilde-fringe :editor file-templates fold snippets :emacs dired electric undo vc :checkers syntax spell grammar :tools direnv (eval +overlay) lookup lsp magit :os tty :lang cc emacs-lisp (haskell +dante) (latex +latexmk +cdlatex +lsp +fold) lua markdown nix ocaml org rst sh web :config (default +bindings +smartparens))
        packages   (n/a)
        unpin      (n/a)
        elpa       (n/a)
```

As of d45155aec, direnv will no longer run more than once in some buffers. As of f7293fb, aborting direnv won't abort opening the file. With this your issue should be resolved.
Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

Works perfectly, thank you so much!


Update configuration rake task

When running locally the rake task to update our docs website configurations, and comparing it to what our docs website currently has, it appears our rake task is out of date with changes the docs team (or we) made directly to the website without updating the rake task. To see these changes:

Locally run bundle exec rake "newrelic:config:docs[html]"
Pull the latest ruby-agent-configuration.mdx file and do a diff with what our agent produces

We should do a comparision and update our rake task where it makes sense.
NOTE: Our configuration rake task runs on every release.

This has been resolved!


Todo app

create react app with react

use React hooks for state management and side Effect
use State to manage the state of various section and components
use Effect hook to save on the local storage and retrieve data
style the project using Css

@Fene-87 requested changes on this pull request.
Hi @Tobby8629
You did extremely great on this project! 👏 👏
There are however a few issues that you still need to work on to go to the next project but you are almost there! 🚦 🏃
Highlights 👍

App working as expected.
Correctly used Git-flow.
Good Quality code.
Efficiently implemented React Components, states, Events, etc.
Well done on the side menu👍

Required Changes ♻

Kindly install linters and other related packages.
I tried editing a task and was not able. You may implement that.

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better.
Kindly check the inline comments marked [OPTIONAL] under the review.
Cheers and Happy coding!👏 💻 🍷
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think the code review was unfair, you can request a second opinion using this form.


Stack trace line numbers incorrect using vite-node on Windows

Describe the bug
Stack trace line numbers are incorrect when using vite-node on Windows.
Using the following dependency versions:
"vite": "5.4.11",
"vite-node": "2.1.8",
"vitest": "2.1.8"
Reproduction
https://github.com/rmuchall/vite-node-bug
System Info
System:
    OS: Windows 11 10.0.26100
    CPU: (2) x64 Intel(R) Core(TM) i7-10870H CPU @ 2.20GHz
    Memory: 698.26 MB / 8.00 GB
  Binaries:
    Node: 22.12.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (129.0.2792.65)

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

In the minimal reproduction repo. The stack trace should be line 15 but is instead showing as line 10.

This might be fixed recently (but not released) https://github.com/vitest-dev/vitest/pull/6786
Can you try pkg.pr.new https://vitest.dev/guide/#using-unreleased-commits?

Many thanks for your super fast response.
I can confirm that using the fix from https://pkg.pr.new/vite-node@main successfully resolves this issue.
Line numbers are working correctly again. Thank you!

Fixed by https://github.com/vitest-dev/vitest/pull/6786.


Quotation marks

Quotation marks don’t seem to work properly in math mode with unicode-math (version 2011/01/25 v0.5b). MWE:
\documentclass{minimal}

\usepackage{fontspec}
\usepackage{unicode-math}
\setmathfont{Cambria Math}

\begin{document}
“…”---\(“…”\)

``…''---\(``…''\)

\textquotedblleft…\textquotedblright---\(\textquotedblleft…\textquotedblright\)
\end{document}

The output is:

When using Asana Math instead of Cambria Math then at least the TeX syntax ```…''` works.
The last syntax correctly produces a warning (“… cannot be used in math mode”) and is just included for correctness’ sake. I’d expect the first two variants to work, though.

I think this has been resolved. The comprehensive test example (thanks!) seems to work entirely except for florin. I'm on the fence about florin, but I guess I should go with my earlier decision (#195) not to add it as a maths symbol in absence of further evidence.


Add : to open commands section(Enhancement)

Similar to vim : in normal mode should open command section that can perform commands and interact with terminal.

check out ex-mode - it doesn't do all the vim ex-mode does, but it has a good start...


test: add delete secrets flag

Description
This pull request changes the following:

Add a new flag for network destroy command

Related Issues

Closes #77

:tada: This PR is included in version 0.27.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Log out

How to logout user?

there is no api that telegram would expose in order to logout user, so your backend must handle it.


Req: Ambilight support.

I would love it if I could assign 'ambilight' to a zone.
Razer already has such a feature, where it colors the peripherals to match the monitor infront of it. If you look up to a blue sky, your devices would turn blue. Look at some grass and they turn green, etz.
It adds a ton of immersion. Its great for games as well as movies.
https://www.youtube.com/watch?v=jrTWqH6886w

Ambilight is part of dev.

How do I get my hands on a dev build? I'm not too savvy with all this github stuff. :')

If you don't want to compile the source code, then you can't.
If you can compile the source code, then https://github.com/antonpup/Aurora/tree/dev.

Hi @antonpup.
I just noticed a bug in the Ambilight implementation.
By default Ambilight is taking about 0,2% of CPU for me. With Ambilight enabled it goes up to arround 5 - 6%.
The bug I've noticed is that once you enable the Ambilight Layer it takes up the extra CPU, when you hide it or even remove it completely, it keeps using CPU cycles and stays like that until you close Aurora completely and restart the app.

Yeah, I know what the problem is. Ambilight layer isn't exactly optimized. Essentially once an ambilight layer is initialized, it starts a static loop that constantly fetches an image that can be used by all ambilight layers, so if you have 30 ambilight layers, you only fetch image once instead of 30 times.
The problem is that I never implemented the way to detect when there are no instances of ambilight layer that need the images. Thus the loop never stops once started.


run_sql command via dbt rpc returns Object of type Decimal is not JSON serializable

Describe the bug
Executing a run_sql command via dbt rbc against a BigQuery profile returns Object of type Decimal is not JSON serializable. The equivalent command against Redshift, Snowflake, and PostgreSQL connections works correctly.
Steps To Reproduce
A model exists with the body with source as ( select * from {{source('recharge', 'orders')}} ) select * from source.
The query of the model is wrapped in a CTE limiting its results to 100 records:
with run_cte as (with source as ( select * from {{source('recharge', 'orders')}} )) select * from run_cte limit 100

And converted to base64:
d2l0aCBydW5fY3RlIGFzICh3aXRoIHNvdXJjZSBhcyAoIHNlbGVjdCAqIGZyb20ge3tzb3VyY2UoJ3JlY2hhcmdlJywgJ29yZGVycycpfX0gKSkgc2VsZWN0ICogZnJvbSBydW5fY3RlIGxpbWl0IDEwMA==

A request is made to the RPC Server with the run_sql command, with the following body:
{
    jsonrpc: "2.0",
    method: 'run_sql',
    id: 123,
    params:  {
      name: "query",
      timeout: 60,
      sql: d2l0aCBydW5fY3RlIGFzICh3aXRoIHNvdXJjZSBhcyAoIHNlbGVjdCAqIGZyb20ge3tzb3VyY2UoJ3JlY2hhcmdlJywgJ29yZGVycycpfX0gKSkgc2VsZWN0ICogZnJvbSBydW5fY3RlIGxpbWl0IDEwMA==
    }

Expected behavior
I would expect this to return the result set of the underlying sql statement.
Screenshots and log output
If applicable, add screenshots or log output to help explain your problem.
System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[x] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
0.16.01

The operating system you're using: macOS 10.13.6
The output of python --version: 3.7
Additional context
Add any other context about the problem here.

Thanks for the report @brettgriffin - this error occurs if a numeric column is found inside of a struct or array column in BigQuery


Programaticaly Prevent Hydration

Clear and concise description of the problem
Changing the structure of the state of your Pinia Store might cause problematic state. Therefore the hydration should be programaticaly preventable. E.g. when changing ur state from state: () => ({     filterStore: {filter: []},     }, to  state: () => ({     filterStore: [] as Filter[],     }, iterating over filterStore and accessing properties of each filter might cause undefined errors.
Suggested solution
I could imagine something like adding a return value to the beforeHydration hook, that defines wether to hydrate or start with a fresh state.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

This can be done with the afterRestore, so I guess its not fully necessary


Refs 1770: add cert expiry metric

Summary
this adds a new metric "content_sources_rh_cert_expiry_days", that signifies the number of days until the current RH cert expires
Testing steps
Ensure you have a cdn cert configured in your config.yaml, run the server, then run:
curl localhost:9000/metrics | grep expi

you'll see something like:
# HELP content_sources_rh_cert_expiry_days Number of days until the Red Hat client certificate expires
# TYPE content_sources_rh_cert_expiry_days gauge
content_sources_rh_cert_expiry_days 23

https://issues.redhat.com/browse/HMS-1770

/retest

[retest]

/retest