Distributed TPU Trainer breaks on Google Cloud Platform

🐛 Bug
I am training an image self-supervised model on the GCP TPU v3-8. The trainer makes it through 13 batches of the first epoch (each batch has 128 96x96 grayscale images per TPU core and takes ~70 seconds to compute) and proceeds to break. I ran the same code on Colab single TPU and it worked without a problem – I also implemented my model using native torch_xla distributed training and it worked without a hitch on the same GCP environment. This makes me wonder if the issue is with how PyTorch-Lightning does multiprocess spawning on TPU?
Environment

Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow): Trainer
PyTorch Lightning Version (e.g., 1.5.0): 1.7.0
Lightning App Version (e.g., 0.5.2):
PyTorch Version (e.g., 1.10): 1.11
Python version (e.g., 3.9): 3.8.5
OS (e.g., Linux): Linux
CUDA/cuDNN version:
GPU models and configuration:
How you installed PyTorch (conda, pip, source):
If compiling from source, the output of torch.__config__.show():
Running environment of LightningApp (e.g. local, cloud):
Any other relevant information:

Additional context
I am posting the full traceback for better reference:
> 2022-08-19 18:50:36.070503: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:50:36.071270: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey
/usr/local/lib/python3.8/dist-packages/pkg_resources/__init__.py:122: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/usr/local/lib/python3.8/dist-packages/pkg_resources/__init__.py:122: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
  warnings.warn(
/home/adam_catto_mssm_edu/.local/lib/python3.8/site-packages/pytorch_lightning/trainer/connectors/accelerator_connector.py:450: LightningDeprecationWarning: Setting `Trainer(tpu_cores=8)` is deprecated in v1.7 and will be removed in v2.0. Please use `Trainer(accelerator='tpu', devices=8)` instead.
  rank_zero_deprecation(
GPU available: False, used: False
TPU available: True, using: 8 TPU cores
IPU available: False, using: 0 IPUs
HPU available: False, using: 0 HPUs
https://symbolize.stripped_domain/r/?trace=7f3e760aaa10,7f3e75cd90bf&map=
*** SIGTERM received by PID 5410 (TID 5410) on cpu 46 from PID 3828; stack trace: ***
PC: @     0x7f3e760aaa10  (unknown)  (unknown)
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0  (unknown)  (unknown)
https://symbolize.stripped_domain/r/?trace=7f3e760aaa10,7f3d6bb7bcd9,7f3e75cd90bf&map=50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 18:51:06.336371    5410 coredump_hook.cc:320] RAW: Remote crash gathering disabled for SIGTERM.
E0819 18:51:06.341113    5410 process_state.cc:771] RAW: Raising signal 15 with default behavior
2022-08-19 18:51:06.443264: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:51:06.443345: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey
2022-08-19 18:51:24.066424: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:51:24.066488: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey
2022-08-19 18:51:25.003574: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:51:25.003640: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey
2022-08-19 18:51:29.867407: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:51:29.867473: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey
2022-08-19 18:51:31.852158: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:51:31.852220: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey
2022-08-19 18:51:31.983662: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:51:31.983726: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey
2022-08-19 18:51:32.151776: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:51:32.151841: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey
2022-08-19 18:51:32.671996: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TPURoundRobin" device_type: "CPU"') for unknown op: TPURoundRobin
2022-08-19 18:51:32.672059: E tensorflow/core/framework/op_kernel.cc:1676] OpKernel ('op: "TpuHandleToProtoKey" device_type: "CPU"') for unknown op: TpuHandleToProtoKey

  | Name             | Type       | Params
------------------------------------------------
0 | backbone         | ResNet     | 23.5 M
1 | online_encoder   | NetWrapper | 33.0 M
2 | online_predictor | MLP        | 2.1 M
3 | target_encoder   | NetWrapper | 33.0 M
------------------------------------------------
21.0 M    Trainable params
23.5 M    Non-trainable params
44.5 M    Total params
178.069   Total estimated model params size (MB)
Sanity Checking DataLoader 0: 100%|███████████████| 2/2 [00:34<00:00, 17.31s/it]/home/adam_catto_mssm_edu/.local/lib/python3.8/site-packages/pytorch_lightning/trainer/connectors/logger_connector/result.py:536: PossibleUserWarning: It is recommended to use `self.log('val_loss', ..., sync_dist=True)` when logging on epoch level in distributed setting to accumulate the metric across devices.
  warning_cache.warn(
Epoch 0:   2%|▏        | 13/591 [15:07<11:12:49, 69.84s/it, loss=1.87, v_num=13]2022-08-19 19:12:17.857636: E tensorflow/core/tpu/kernels/tpu_compilation_cache_external.cc:113] Computation requires more parameters (3496) than supported (limit 3305).
2022-08-19 19:12:17.857731: F tensorflow/core/tpu/kernels/tpu_program_group.cc:86] Check failed: xla_tpu_programs.size() > 0 (0 vs. 0)
https://symbolize.stripped_domain/r/?trace=7f3e75cd903b,7f3e75cd90bf,7f3d7ab78bcf,7f3d751ed922,7f3d751abebd,7f3d751fbdb0,7f3d751fb8ae,7f3d7105ded3,7f3d7669f1b8,7f3d7a62a8a0,7f3d7a62c633,7f3d7ab41cb1,7f3d7ab414e0,7f3d7ab298cb,7f3e75c7b608&map=b5462df73b9bb298b2bca5d2f02176eed80a2e90:7f3d6c719000-7f3d7da0ee30
*** SIGABRT received by PID 5414 (TID 6198) on cpu 24 from PID 5414; stack trace: ***
PC: @     0x7f3e75cd903b  (unknown)  raise
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0       3968  (unknown)
    @     0x7f3d7ab78bd0         16  tensorflow::internal::LogMessageFatal::~LogMessageFatal()
    @     0x7f3d751ed923        592  tensorflow::tpu::TpuProgramGroup::Initialize()
    @     0x7f3d751abebe       1488  tensorflow::tpu::TpuCompilationCacheExternal::InitializeEntry()
    @     0x7f3d751fbdb1        800  tensorflow::tpu::TpuCompilationCacheInterface::CompileIfKeyAbsentHelper()
    @     0x7f3d751fb8af        496  tensorflow::tpu::TpuCompilationCacheInterface::CompileIfKeyAbsent()
    @     0x7f3d7105ded4        912  tensorflow::XRTCompileOp::Compute()
    @     0x7f3d7669f1b9        432  tensorflow::XlaDevice::Compute()
    @     0x7f3d7a62a8a1       2128  tensorflow::(anonymous namespace)::ExecutorState<>::Process()
    @     0x7f3d7a62c634         48  std::_Function_handler<>::_M_invoke()
    @     0x7f3d7ab41cb2        128  Eigen::ThreadPoolTempl<>::WorkerLoop()
    @     0x7f3d7ab414e1         48  tensorflow::thread::EigenEnvironment::CreateThread()::{lambda()#1}::operator()()
    @     0x7f3d7ab298cc         80  tensorflow::(anonymous namespace)::PThread::ThreadFn()
    @     0x7f3e75c7b609  (unknown)  start_thread
https://symbolize.stripped_domain/r/?trace=7f3e75cd903b,7f3d6bb7bcd9,7f3e75cd90bf,7f3d7ab78bcf,7f3d751ed922,7f3d751abebd,7f3d751fbdb0,7f3d751fb8ae,7f3d7105ded3,7f3d7669f1b8,7f3d7a62a8a0,7f3d7a62c633,7f3d7ab41cb1,7f3d7ab414e0,7f3d7ab298cb,7f3e75c7b608&map=b5462df73b9bb298b2bca5d2f02176eed80a2e90:7f3d6c719000-7f3d7da0ee30,50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 19:12:25.499816    6198 coredump_hook.cc:365] RAW: Remote crash data gathering hook invoked.
E0819 19:12:25.499836    6198 coredump_hook.cc:411] RAW: Skipping coredump since rlimit was 0 at process start.
E0819 19:12:25.499860    6198 client.cc:222] RAW: Coroner client retries enabled (b/136286901), will retry for up to 30 sec.
E0819 19:12:25.499874    6198 coredump_hook.cc:473] RAW: Sending fingerprint to remote end.
E0819 19:12:25.499892    6198 coredump_socket.cc:124] RAW: Stat failed errno=2 on socket /var/google/services/logmanagerd/remote_coredump.socket
E0819 19:12:25.499896    6198 coredump_hook.cc:477] RAW: Cannot send fingerprint to Coroner: [NOT_FOUND] Missing crash reporting socket. Is the listener running?
E0819 19:12:25.499902    6198 coredump_hook.cc:550] RAW: Discarding core.
E0819 19:12:26.381038    6198 process_state.cc:771] RAW: Raising signal 6 with default behavior
2022-08-19 19:16:08.118354: W tensorflow/core/distributed_runtime/rpc/grpc_remote_master.cc:157] RPC failed with status = "UNAVAILABLE: Connection reset by peer" and grpc_error_string = "{"created":"@1660936568.118086051","description":"Error received from peer ipv4:<IP_ADDRESS>:51011","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Connection reset by peer","grpc_status":14}", maybe retrying the RPC
2022-08-19 19:16:08.121698: W tensorflow/core/distributed_runtime/rpc/grpc_remote_master.cc:157] RPC failed with status = "UNAVAILABLE: Connection reset by peer" and grpc_error_string = "{"created":"@1660936568.121551341","description":"Error received from peer ipv4:<IP_ADDRESS>:51011","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Connection reset by peer","grpc_status":14}", maybe retrying the RPC
2022-08-19 19:16:08.121850: W tensorflow/core/distributed_runtime/rpc/grpc_remote_master.cc:157] RPC failed with status = "UNAVAILABLE: Connection reset by peer" and grpc_error_string = "{"created":"@1660936568.121673841","description":"Error received from peer ipv4:<IP_ADDRESS>:51011","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Connection reset by peer","grpc_status":14}", maybe retrying the RPC
2022-08-19 19:16:08.122091: W tensorflow/core/distributed_runtime/rpc/grpc_remote_master.cc:157] RPC failed with status = "UNAVAILABLE: Socket closed" and grpc_error_string = "{"created":"@1660936568.121976147","description":"Error received from peer ipv4:<IP_ADDRESS>:51011","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Socket closed","grpc_status":14}", maybe retrying the RPC
2022-08-19 19:16:08.122420: W tensorflow/core/distributed_runtime/rpc/grpc_remote_master.cc:157] RPC failed with status = "UNAVAILABLE: Connection reset by peer" and grpc_error_string = "{"created":"@1660936568.122250817","description":"Error received from peer ipv4:<IP_ADDRESS>:51011","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Connection reset by peer","grpc_status":14}", maybe retrying the RPC
2022-08-19 19:16:08.122566: W tensorflow/core/distributed_runtime/rpc/grpc_remote_master.cc:157] RPC failed with status = "UNAVAILABLE: Connection reset by peer" and grpc_error_string = "{"created":"@1660936568.122414562","description":"Error received from peer ipv4:<IP_ADDRESS>:51011","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Connection reset by peer","grpc_status":14}", maybe retrying the RPC
2022-08-19 19:16:08.122676: W tensorflow/core/distributed_runtime/rpc/grpc_remote_master.cc:157] RPC failed with status = "UNAVAILABLE: Connection reset by peer" and grpc_error_string = "{"created":"@1660936568.122580450","description":"Error received from peer ipv4:<IP_ADDRESS>:51011","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Connection reset by peer","grpc_status":14}", maybe retrying the RPC
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3e75cd90bf&map=
*** SIGTERM received by PID 5421 (TID 5421) on cpu 49 from PID 3828; stack trace: ***
PC: @     0x7f3e75c853f4  (unknown)  do_futex_wait.constprop.0
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0  (unknown)  (unknown)
    @ ... and at least 1 more frames
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3d6bb7bcd9,7f3e75cd90bf&map=50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 19:16:10.582266    5421 coredump_hook.cc:320] RAW: Remote crash gathering disabled for SIGTERM.
E0819 19:16:10.611582    5421 process_state.cc:771] RAW: Raising signal 15 with default behavior
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3e75cd90bf&map=
*** SIGTERM received by PID 5515 (TID 5515) on cpu 31 from PID 3828; stack trace: ***
PC: @     0x7f3e75c853f4  (unknown)  do_futex_wait.constprop.0
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0  (unknown)  (unknown)
    @ ... and at least 1 more frames
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3d6bb7bcd9,7f3e75cd90bf&map=50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 19:16:10.685134    5515 coredump_hook.cc:320] RAW: Remote crash gathering disabled for SIGTERM.
E0819 19:16:10.710575    5515 process_state.cc:771] RAW: Raising signal 15 with default behavior
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3e75cd90bf&map=
*** SIGTERM received by PID 5519 (TID 5519) on cpu 79 from PID 3828; stack trace: ***
PC: @     0x7f3e75c853f4  (unknown)  do_futex_wait.constprop.0
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0  (unknown)  (unknown)
    @ ... and at least 1 more frames
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3d6bb7bcd9,7f3e75cd90bf&map=50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 19:16:10.788056    5519 coredump_hook.cc:320] RAW: Remote crash gathering disabled for SIGTERM.
E0819 19:16:10.813398    5519 process_state.cc:771] RAW: Raising signal 15 with default behavior
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3e75cd90bf&map=
*** SIGTERM received by PID 5523 (TID 5523) on cpu 5 from PID 3828; stack trace: ***
PC: @     0x7f3e75c853f4  (unknown)  do_futex_wait.constprop.0
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0  (unknown)  (unknown)
    @ ... and at least 1 more frames
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3d6bb7bcd9,7f3e75cd90bf&map=50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 19:16:10.888321    5523 coredump_hook.cc:320] RAW: Remote crash gathering disabled for SIGTERM.
E0819 19:16:10.913426    5523 process_state.cc:771] RAW: Raising signal 15 with default behavior
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3e75cd90bf&map=
*** SIGTERM received by PID 5527 (TID 5527) on cpu 26 from PID 3828; stack trace: ***
PC: @     0x7f3e75c853f4  (unknown)  do_futex_wait.constprop.0
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0  (unknown)  (unknown)
    @ ... and at least 1 more frames
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3d6bb7bcd9,7f3e75cd90bf&map=50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 19:16:10.988339    5527 coredump_hook.cc:320] RAW: Remote crash gathering disabled for SIGTERM.
E0819 19:16:11.013561    5527 process_state.cc:771] RAW: Raising signal 15 with default behavior
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3e75cd90bf&map=
*** SIGTERM received by PID 5531 (TID 5531) on cpu 56 from PID 3828; stack trace: ***
PC: @     0x7f3e75c853f4  (unknown)  do_futex_wait.constprop.0
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0  (unknown)  (unknown)
    @ ... and at least 1 more frames
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3d6bb7bcd9,7f3e75cd90bf&map=50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 19:16:11.083357    5531 coredump_hook.cc:320] RAW: Remote crash gathering disabled for SIGTERM.
E0819 19:16:11.108967    5531 process_state.cc:771] RAW: Raising signal 15 with default behavior
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3e75cd90bf&map=
*** SIGTERM received by PID 5535 (TID 5535) on cpu 69 from PID 3828; stack trace: ***
PC: @     0x7f3e75c853f4  (unknown)  do_futex_wait.constprop.0
    @     0x7f3d6bb7bcda        992  (unknown)
    @     0x7f3e75cd90c0  (unknown)  (unknown)
    @ ... and at least 1 more frames
https://symbolize.stripped_domain/r/?trace=7f3e75c853f4,7f3d6bb7bcd9,7f3e75cd90bf&map=50c831e765011c7eb7163b7f3cb5c4b6:7f3d5d3d1000-7f3d6bee9f00
E0819 19:16:11.186153    5535 coredump_hook.cc:320] RAW: Remote crash gathering disabled for SIGTERM.
E0819 19:16:11.212888    5535 process_state.cc:771] RAW: Raising signal 15 with default behavior
Traceback (most recent call last):
  File "run_gcp.py", line 137, in <module>
    pretrainer.fit(model=ssl_model, datamodule=pretraining_data)
  File "/home/adam_catto_mssm_edu/.local/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 700, in fit
    self._call_and_handle_interrupt(
  File "/home/adam_catto_mssm_edu/.local/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 652, in _call_and_handle_interrupt
    return self.strategy.launcher.launch(trainer_fn, *args, trainer=self, **kwargs)
  File "/home/adam_catto_mssm_edu/.local/lib/python3.8/site-packages/pytorch_lightning/strategies/launchers/xla.py", line 83, in launch
    _save_spawn(
  File "/home/adam_catto_mssm_edu/.local/lib/python3.8/site-packages/pytorch_lightning/strategies/launchers/xla.py", line 168, in _save_spawn
    return xmp.spawn(wrapped, args=args, nprocs=nprocs, join=join, daemon=daemon, start_method=start_method)
  File "/usr/local/lib/python3.8/dist-packages/torch_xla/distributed/xla_multiprocessing.py", line 389, in spawn
    return torch.multiprocessing.start_processes(
  File "/usr/local/lib/python3.8/dist-packages/torch/multiprocessing/spawn.py", line 198, in start_processes
    while not context.join():
  File "/usr/local/lib/python3.8/dist-packages/torch/multiprocessing/spawn.py", line 140, in join
    raise ProcessExitedException(
torch.multiprocessing.spawn.ProcessExitedException: process 0 terminated with signal SIGABRT

cc @JackCaoG @steventk-g @Liyang90 @tchaton @rohitgr7 @kaushikb11

I encounter the same problem using both pytorch 1.12 and pytorch 1.10. For me it happens sometimes in the first 10 steps while once it finished an epoch and then crashed.

Have you tried
import torch_xla.core.xla_model as xm
print(xm.xla_device())

after this error. I am having similar error

For anyone else waiting for this fix, I found the following command-line instruction fixes the problem when using Vertex AI Workbench:
pip uninstall torch_xla

We run tests on gcloud and don't see any issues related to the top post. Closing
Happy to discuss if this is still a problem


Mamba2 Parallelization questioned. Very similar to the 'UltraLight VM-UNet: Parallel Vision Mamba Significantly Reduces Parameters for Skin Lesion Segmentation' article.

Hi, we found your mamba2 parallelization very similar to the previous 'UltraLight VM-UNet: Parallel Vision Mamba Significantly Reduces Parameters for Skin Lesion Segmentation' in lightweight medical image segmentation. And there is no discussion or citation of it in the paper. Wu et al. have already discussed the advantage of significant parameter reduction by parallelizing mamba, but what is the significance of mamba2?
Parallelization in mamba2:

Parallelization in UltraLight VM-UNet:

this doesn't seem to be talking about the same form of parallelism (tensor parallelism). i don't think these contributions are very related; the architectural modifications are not the main focus of mamba-2
note that mamba-2 was finalized more than 6 months ago! we're very happy that this paper and others are excited about applying and improving mamba, but, we don't have room to discuss every follow-up work :(


Large model

Thanks for the nice afford with this app, I was wondering if I could- use it with the large model because I can see that with the multilanguage the transscription the large model have much better results than the one you are using. I have the large model on my Ubuntu server and test it with Gradio it gives a much better transcription. The question is how to adjust the script the use the large model from my local server?. also I saw in your demo on hugging face there is a microphone I do miss it.
Thanks

The purpose of this project is to run whisper directly in your browser, instead of a local server, so, I won't be modifying it to support an API. However, feel free to separate the frontend from the backend if you wish to reuse the user interface.

Hi @xenova,
We added it to the models list as 'Xenova/whisper-large': [1550]. I download the model, but I get the error "RangeError: offset is out of bounds" during the transcription phase. I get the same error on devices with these different RAMs. How can I operate the Large model?

whisper-web\src\components\AudioManager.tsx
`    const models = {
// Original checkpoints
'Xenova/whisper-tiny': [41, 152],
'Xenova/whisper-base': [77, 291],
'Xenova/whisper-small': [249],
'Xenova/whisper-medium': [776],
'Xenova/whisper-large-v2': [23776],
'Xenova/whisper-large-v3': [17776],
    // Distil Whisper (English-only)
    'distil-whisper/distil-medium.en': [402],
    'distil-whisper/distil-large-v2': [767],
};`

@midpoint what do the numeric values (in the parenthesis) represent?


aurelia-flux definitions

Adding aurelia-flux definitions.

aurelia-flux/aurelia-flux.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/aurelia-flux
http://bower.io/search/?q=aurelia-flux
others?

[ ] has a test file? (aurelia-flux/aurelia-flux-tests.ts or others)
[ ] pass the Travis-CI test?

please rename aurelia-flux/aurelia-flux.test.ts to aurelia-flux/aurelia-flux-tests.ts

I did as you asked, but travis build is stil in progress.

As aurelia-flux provides decorators, aurelia-flux-tests.ts conaints some.

please use .tscparams like this https://github.com/borisyankov/DefinitelyTyped/blob/master/core-decorators/core-decorators-tests.ts.tscparams

Hello and thank you for your contribution!
Due to an excessively long queue of pull requests that have become stale, we are "declaring bankruptcy" and closing all PRs opened before May 1, 2016. If you'd still like to merge this code in, please open a new PR that has been merged and rebased with the master branch.
Going forward, we are committing to review or merge all PRs on a regular basis so this bankruptcy will not occur again. We apologize for the incovenience and hope you will continue to contribute to DefinitelyTyped in the future.
Thanks
The TypeScript and DefinitelyTyped teams


Update aws-java-sdk-dynamodb to 1.12.145

Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.145.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

labels: library-update, early-semver-minor, semver-spec-minor

Superseded by #225.


Dev/greazer/telem updates

Add some additional telemetry to track gather use.
Updated the header at the top of gathered notebooks and script to point to a survey.

Codecov Report

Merging #10631 into master will decrease coverage by 0.17%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #10631      +/-   ##
==========================================
- Coverage   60.79%   60.62%   -0.18%
==========================================
  Files         579      583       +4
  Lines       31403    31551     +148
  Branches     4469     4487      +18
==========================================
+ Hits        19091    19127      +36
- Misses      11342    11450     +108
- Partials      970      974       +4

Impacted Files
Coverage Δ

src/client/common/utils/localize.ts
95.19% <ø> (ø)

src/client/telemetry/index.ts
87.38% <ø> (ø)

src/client/datascience/constants.ts
99.71% <100.00%> (+<0.01%)
:arrow_up:

src/client/datascience/gather/gather.ts
34.84% <100.00%> (+2.03%)
:arrow_up:

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

...t/common/insidersBuild/insidersExtensionService.ts
97.18% <0.00%> (-2.82%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

...ascience/interactive-ipynb/nativeEditorProvider.ts
52.24% <0.00%> (-1.13%)
:arrow_down:

... and 22 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 dbf4d70...a6dcd48. Read the comment docs.

Made suggested change by Rich before submitting.


xplat: ArrayBuffer oob access recovery [JIT] [ASMJS]

AsmJs/constloads.js depends on ArrayBuffer out of bound access recovery feature. Needs xplat implementation to re-enable this test. Excluded by #1591.

@obastemur

Fixing correctness #1703


Black screen before splash is loaded

Hi,
I don't know why but when app is launched it loads a black screen and some miliseconds later start the splash screen image. Before last update it works fine.
Capacitor Version
@capacitor/core: "^3.5.0"
https://user-images.githubusercontent.com/32843723/170036253-de173f39-f761-499d-90af-0a113247259b.mp4

I don't think this is related to this tool


Makefile doesn't compile

Bug 1: It is usually expected that make (with no arguments) will recompile the binaries from the source code. However, instead the Makefile prints an error suggesting the user run make package, make install, or make clean.
Bug 2: make clean ought to delete the binaries so that they will be rebuilt from source.
Bug 3: make install should depend on the binaries so that they will be rebuilt from source if they are missing.

Here's a minimal patch would maybe fix the problems. It's not ideal and I haven't been able to test it fully because compilation fails with gcc-8.3, but it's a start.
diff --git a/Makefile b/Makefile
index aa51c18..02e00b8 100644
--- a/Makefile
+++ b/Makefile
@@ -1,14 +1,19 @@
VERSION=$(shell gawk '/^VERSION/ {print $1}' bin/mksdiso | cut -f2 -d")
BUILD_DIR=build/mksdiso-$(VERSION)-all
-default:
+default: build
+
+help:
@echo "Usage: make <package|install|clean>"
@echo "   package | Build debian Package"
@echo "   install | install to /usr/local/bin"
@echo "   clean   | cleanup package build directory"
exit 0
-package:
+build:

cd src; make

+package: build
mkdir -p $(BUILD_DIR)/usr/bin $(BUILD_DIR)/usr/share/mksdiso $(BUILD_DIR)/DEBIAN
cp debian/control $(BUILD_DIR)/DEBIAN/
cp bin/* $(BUILD_DIR)/usr/bin/
@@ -18,7 +23,7 @@ package:
dpkg-deb --build $(BUILD_DIR)
Local install, modifes mksdiso-data-path to /usr/local/share/mksdiso
-install:
+install: build
cp -r bin/* /usr/local/bin/
sed -i 's/^DATADIR=.*/DATADIR=/usr/local/share/mksdiso/' /usr/local/bin/mksdiso
mkdir -p /usr/local/share || true


Numpy version for M1 mac

Good afternoon, I wanted to use your library in my project, but unfortunately. Installing dependencies requires "numpy>=1.19.5,<1.20", but on M1 it throws an error with numpy ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 80 from PyObject. I have researched how to fix this error and they say to raise the numpy version. Is it possible to update the dependencies for this project to work with numpy 1.20+ as without this I get a version conflict.

Hi,
I think you can use a higher version of numpy. BTW on M1 I suggest using conda (although I haven't tested it but I heard it provides better compatibility for M1).

@gaotianyu1350 I also couldn't install SimCSE with numpy 1.20+ on M1. Is it possible to update dependencies?

I think any numpy version could work. You can just install the number that works on your machine.


Rebuild for gfortran 7 for OSX (fixed)

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] 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)
[x] Ensured the license file is being packaged.

Closes #6

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) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge/rpfits This PR is ready to merge!

Thanks @beckermr!


Fall back to English when content is in an unsupported locale

The content schema locales include some locales which are not supported by Rails by default, such as tk and zh. This triggers an exception in ApplicationController when it attempts to set the application locale from the content locale.
I think this is an edge case of #1117, which fixed the way the application locale was extracted from the content.
This was causing flaky tests when a random content item was generated. For example, help_controller_test would fail about 20% of the time when a content item with an unsupported language was generated. Example seed: 47089.
This fix checks whether the content's locale is in the list locales supported by the Rails application, and falls back to English if not.
A better long-term fix might be to align the locales in govuk-content-schemas with the available locales in GOVUK Rails applications. I'm just proposing this as a short-term fix to prevent errors on any real pages in these languages, and also fix the flaky test.

In case it's useful for anyone: the list of content locales is in definitions.json in govuk-content-schemas.
Of those, the locales not supported by Rails by default are: dr, hy, ka, ps, si, so, tk, zh, zh-hk, zh-tw.

That's really odd, because I got the list of locales in definitions.json from checking Rails!
https://github.com/alphagov/govuk-content-schemas/pull/364
Perhaps it would be better to update that list?

@tijmenb Looks like government-frontend configures its own list of locales and translations, whereas most apps use the Rails defaults: https://github.com/alphagov/government-frontend/tree/master/config/locales

Ah, that's of course where available_locales comes from.. Can we force/override available_locales somehow? Would be great to have one canonical list of languages that GOV.UK supports.

Maybe we all already know this but the reason for the list being different to rails defaults is that it's the list of languages available in whitehall, mostly for embassies and such to provide content in the languages widespread in their locality.


Create node.js.yml

Would having something connected to GitHub Actions be helpful for our project/grading? If yes, is this the best way to do it? If no, is there some other way that we can do some of the autotests/etc. that are listed in the project rubric?

Found a better (less unsuccessful!) way to do this.


2.x Upgrade rxjava and karyon versions

NetflixOSS » eureka » eureka-pull-requests #189 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » eureka » eureka-pull-requests #190 SUCCESS
This pull request looks good


[WFLY-10525] Upgrade to Galleon 1.0.1.Final and Galleon Plugins 1.0.1.Final

Upgrade releases of Galleon and WildFly Galleon plugins in wildfly.
This upgrade will allow creating the correct file permissions defined by wildfly-core galleon-pack.
Jira issue: https://issues.jboss.org/browse/WFLY-10525
cc: @aloubyansky

@aloubyansky @yersan Do we need to make the full and feature galleon-packs do something similar to https://github.com/wildfly/wildfly-core/pull/3347/files#diff-219ed0dff7fc73b291eb9e4a3a17b64aR5 or is that all handled by the core galleon pack?

The versions should change in full but that package and the task are inherited from core.


Create Sneeze Board Sample Extension Part 2

Improve sneeze board client. Learning practice objectives:

[ ] Improve React skills
[ ] Use external libraries in webviews (color picker)
[ ] Cache data from server
[ ] Use WebSocket in extension
[ ] Create user settings
[ ] Continue to Exercise PAPI and get feedback
[ ] Improve accuracy of prophecy of Jesus' return*

Part 1 set up the base. Here are some ideas for improvements and some larger items that we did not get to that could be good to flesh out in an extension.
*This is a false prophecy.

@tjcouch-sil Wasn't there a color picker that we couldn't use intially? Can we use it now or has that been done already?

@tjcouch-sil Wasn't there a color picker that we couldn't use intially? Can we use it now or has that been done already?

Good idea! Added to the description


DOES NOT CONNECT WITHTL-SG1016DE  &  TL-SG108E

When I try to connect to one of those two models I get a "Can not authenticate" error.
With the TL-SG1016PE it works perfectly.
All the best.

I'll send you what you asked for, if you need anything else tell me.

2023-05-07 12:06:50.893 ERROR (MainThread) [homeassistant.util.logging] Exception in async_write_ha_state when dispatching 'systemmonitor_update': ()
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 579, in state
numerical_value = int(value)
ValueError: invalid literal for int() with base 10: 'off'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 585, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 649, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 591, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 583, in state
raise ValueError(
ValueError: Sensor sensor.process_octave_cli has device class None, state class measurement unit None and suggested precision None thus indicating it has a numeric value; however, it has the non-numeric value: off (<class 'str'>)
html.zip
Thank you.

 Can you configure them without using the Easy Smart utility, just from the browser? Are their web interfaces accessible by the specified IP addresses from the browser?

yes, of course, both switches have web interface and are accessed via web browser and tplink utility.
In the previous post I attached the html file with said access web page, the "html.zip" file, I compressed it so that I could attach it.
Anything you need I can provide.
Greetings, thank you for your time and your work.

I'm afraid that I initially chose the wrong way to develop the component. Maybe I should have tried using the protocol that the Easy Smart Configuration Utility uses. Instead, I focused on trying to use GET/POST requests and then parsing the resulting html pages.
Apparently, different switch models have different behavior and different page layout, which prevents the component from being universal.
Perhaps I will try to add support for the broadcast protocol used in EasySmart to the component, but it is difficult for me to predict when this will be implemented


Update MAINTAINERS.md

Update list of current maintainers and emeritus maintainers
Description
Describe what this change achieves.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
Version
List the OpenSearch version to which this PR applies, e.g. 2.14, 2.12--2.14, or all.
Frontend features
If you're submitting documentation for an OpenSearch Dashboards feature, add a video that shows how a user will interact with the UI step by step. A voiceover is optional.
Checklist

[ ] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@kolchfa-aws Thanks for catching Stephen's username :)


Changed riak_search.query default to enabled and commented

This PR changes the job control settings added in 2.2 so that they are commented with their associated default values. Doing so reduces friction in the (unlikely) case that a new install is downgraded to a previous version.

+1 ec28d08

@borshop merge


user experience updated

AB#47757806

closing this PR because it changes 5 files instead of 1, and updating from "main" branch didn't reduce 5 to 1 files changed.
Replaced by PR 2933?  (Update UX item in Best Practices)


UI/UX feedback

Searching for non-existen stock ticker crashes the app
https://investory-app.herokuapp.com/stocks/intl

Navigating to news items shows blank page
https://investory-app.herokuapp.com/stocks/i6zt4/c1.u/rcs1o3f/rxsWvi0wY/lHL9p/wNa:d12Gaeo/oka6jshnPCEp.5li76g2ntPscmMhtszPEe6wedE

Adding a non-existent stock ticker to backtest yeilds no results

Editing portfolio would be better if it's populated with existing portfolio data.

Light up the nav item for the section you're currently in.

Why is "Bactest Portfolio" its own section? When the portfolio you create is in "My Stocks?"

Go all in on "Inve$story" for the entire app. E.g. instead of "Investment $tory."

Searching for non-existen stock ticker crashes the app
https://investory-app.herokuapp.com/stocks/intl
Navigating to news items shows blank page
https://investory-app.herokuapp.com/stocks/i6zt4/c1.u/rcs1o3f/rxsWvi0wY/lHL9p/wNa:d12Gaeo/oka6jshnPCEp.5li76g2ntPscmMhtszPEe6wedE
Adding a non-existent stock ticker to backtest yeilds no results
Editing portfolio would be better if it's populated with existing portfolio data.
Light up the nav item for the section you're currently in.
Why is "Bactest Portfolio" its own section? When the portfolio you create is in "My Stocks?"
Go all in on "Inve$story" for the entire app. E.g. instead of "Investment $tory."

Thank you George for the feedback! I implemented some enhancements to address the problems:

Added better error-handling features
Currently using sandbox API so news won't redirect. Will switch API accounts for news to show up
Renamed "Backtest Portfolio" to "Add Portfolio" so it's clear that it is a form. Because it's the main feature of the app, I want to make sure users have access to the form wherever they are in the app
Unified branding by using "Inve$tory" whenever appropriate


Why is there preemption?

Thank you for always good answer.
This is the debugging log for simpleExp that ran one thread spin for 10ms and sleep for 10ms in the FIFO scheduler.
But preemption occurs several times before finish work.
Why is there preemption?

A task preemption typically occurs because another thread in CFS (or a different higher priority scheduling class, such as the real-time classes) woke up. We have Linux give CFS tasks higher priority than ghOSt tasks, so when a CFS task wakes up, it gets strict priority over ghOSt.
Do you know if you running the ghOSt agent on a core that is busy with other things? You could use SchedViz or another tool to see which thread is causing the preemption and narrow down the debugging from there. It may just be a kworker or something similar.

A task preemption typically occurs because another thread in CFS (or a different higher priority scheduling class, such as the real-time classes) woke up. We have Linux give CFS tasks higher priority than ghOSt tasks, so when a CFS task wakes up, it gets strict priority over ghOSt.
Do you know if you running the ghOSt agent on a core that is busy with other things? You could use SchedViz or another tool to see which thread is causing the preemption and narrow down the debugging from there. It may just be a kworker or something similar.

Thank you for your kind answer. So, does this mean that on a ghOSt core, not only are ghOSt threads running, but also default Linux tasks (CFS tasks), and these CFS tasks could have higher priority, causing ghOSt tasks to be preempted? Or, is the core running both the agent and the tasks in a multithreaded manner, causing task preemption when the agent processes its work? I tried installing the testing tools, but I couldn’t complete the setup due to environment configuration issues

Yes, there are also default Linux tasks running on those cores, which results in preemption. Take a look at these kernel params, which can help move these tasks onto other cores: isolcpus, nohz_full, rcu_nocbs, and irq_affinity. e.g., something like the following could be helpful to you:
isolcpus=nohz,domain,5-6 nohz_full=5-6,rcu_nocbs=5-6,irq_affinity=0-4,7-15

Just be sure to replace the numbers above with the correct core numbers on your system (e.g., I assume you have a 16-core system above).
The ghOSt agents themselves could also cause preemptions, but this only happens when they forcibly wake up, such as when one agent sends an interrupt to another (via Agent::Ping()) or if an agent registers a timer signal handler and then the timer fires.

Yes, there are also default Linux tasks running on those cores, which results in preemption. Take a look at these kernel params, which can help move these tasks onto other cores to avoid preemptions on the ghOSt cores: isolcpus, nohz_full, rcu_nocbs, and irq_affinity. e.g., something like the following could be helpful to you:
isolcpus=nohz,domain,5-6 nohz_full=5-6,rcu_nocbs=5-6,irq_affinity=0-4,7-15

Just be sure to replace the numbers above with the correct core numbers on your system (e.g., I assume you have a 16-core system above).
The ghOSt agents themselves could also cause preemptions, but this only happens when they forcibly wake up, such as when one agent sends an interrupt to another (via Agent::Ping()) or if an agent registers a timer signal handler and then the timer fires.

Thank you for answer !

Yes, there are also default Linux tasks running on those cores, which results in preemption. Take a look at these kernel params, which can help move these tasks onto other cores to avoid preemptions on the ghOSt cores: isolcpus, nohz_full, rcu_nocbs, and irq_affinity. e.g., something like the following could be helpful to you:
isolcpus=nohz,domain,5-6 nohz_full=5-6,rcu_nocbs=5-6,irq_affinity=0-4,7-15

Just be sure to replace the numbers above with the correct core numbers on your system (e.g., I assume you have a 16-core system above).
The ghOSt agents themselves could also cause preemptions, but this only happens when they forcibly wake up, such as when one agent sends an interrupt to another (via Agent::Ping()) or if an agent registers a timer signal handler and then the timer fires.

Thank you for answer!


Integrate Cognito with Dockstore

Current docstore software has support for certain security integrations (Google, Facebook, etc..), but not Cognito.  This is the effort to show the U-ADS team how to integrate with Cognito.

Ramesh already helped other team members enough, and enough help was provided. Closing this.


Create New Sparkpost Adapter

I'm having problems with the existing SparkPostAdapter project and it uses an old version of elixir and bamboo. I'm writing my own with tests to debug the problem I'm having. I keep getting an html response of 301 moved whenever I use bamboo with sparkpost. When I use sparkposts' elixir library it all works fine. So it can't be my credentials or their service. Hopefully, the new sparkpost adapter will either solve the problem or elude to a solution.
Sorry about opening a PR without permission, I thought it was going to happen against my forked copy.
feedback and thoughts would be appreciated. If this gets solved without a new adapter I'll close the PR.

@genericlady I commented on the PR. It's totally fine that you opened it first :)
You may want to open an issue on the SparkPost adapter Repo as they will know how to help more. I've never used Sparkpost so sadly, I'm not in a position to help with it. Feel free to comment here even after I close this

@paulcsmith Thanks so much, you're so kind!
I will do exactly what you say, open issues against SparkPost adapter repo and help out there. Have a good weekend!


Add more cpu options to HostConfig

addresses #565

Current coverage is 46.07% (diff: 66.66%)

Merging #567 into master will increase coverage by 0.12%

@@             master       #567   diff @@
==========================================
  Files           130        130
  Lines          4314       4326    +12
  Methods           0          0
  Messages          0          0
  Branches        638        638
==========================================
+ Hits           1982       1993    +11
- Misses         2144       2145     +1
  Partials        188        188

Powered by Codecov. Last update b2476cd...d213266


3bot default landing page should go to admin if not deployed with any other package with domains

if the system is deployed only for 3bot usage it should redirect / to -> /admin

duplicate of https://github.com/threefoldtech/js-sdk/issues/505 ?


feat!: don't create Storage account

Storage account should be explicitly created outside of the SQL module, preferably using the Storage module to use its full feature set.
Fixes #75

Tests pass 🎉


A migrated user should land on the Search page the very first session when they are nudged over to newdot

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: NA
Reproducible in staging?:  Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: NA
If this was caught during regression testing, add the test name, ID and link from TestRail: NA
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: NA
Expensify/Expensify Issue URL: NA
Issue reported by: @flaviadefaria
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C07NMDKEFMH/p1733514796643789
Action Performed:

Migrate a user
Sign in after the user has been migrated

Expected Result:
The migrated user should land on the Search page the very first session when they are nudged over to newdot
Actual Result:
The user lands on the Inbox page
Workaround:
NA
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Oh my bad, @ZhenjaHorbach, for sure payment will still be issued for you.


How to use Arc<> in new_service_def()

Hi, I'm new to rust, so I have a problem bothering me, hoping to get help.
I define a struct called Peer, wrapped it using Arc, then use a new thread to start PRC server:
fn start_server(p: Arc<Peer>) {
...
server.add_service(PeerSrvServer::new_service_def(p));
...
}

then I get compile error:
the trait bound `std::sync::Arc<demo_with_grpc::peer::Peer>: demo_with_grpc::peerpb_grpc::PeerSrv` is not satisfied

So what's the correct way to write the code?
Many thanks!

You are getting that error because only your underlying Peer struct implements the interface that you are needing. Arc<Peer> is a different type altogether, and according to the compiler, does not implement that interface.
A way to work around this:

pass only the strict instance to your function mentioned above.
if you still need to share that instance with other threads (if so, why?) then wrap it in an Arc after the function call.

Solved it.
The reason why I need to share the instance with other threads is that my instance needs to be both rpc client and server. I'm constructing a p2p system.

@thedodd thank you for help answering!

Absolutely.


Upgrade Composable to v3.2.0

Prop 4
Height 420000
https://explorers.l0vd.com/composable-mainnet/gov/4 Upgrade time est 2023-07-03 19:52:03 EST
Prop is mistaken in its title (3.1.0), this upgrade is for 3.2.0. Please refer to upgrade description in proposal and this release tag: https://github.com/notional-labs/composable-centauri/releases/tag/v3.2.0

Given that there is yet another another launch version, 3.2.2, I'm going to hold off on attempting to update this PR again until a version is confirmed as being live.

Given that there is yet another another launch version, 3.2.2, I'm going to hold off on attempting to update this PR again until a version is confirmed as being live.

So should we merge this for now, then?

Given that there is yet another another launch version, 3.2.2, I'm going to hold off on attempting to update this PR again until a version is confirmed as being live.

So should we merge this for now, then?

Ready to go!


update rootless-install to 23.0.3

release notes: https://github.com/moby/moby/releases/tag/v23.0.3

All green now; bringing this one in, and will deploy


firebase phone authentication on dual sim phone

On dual sim phone i am using firebase_auth 0.11.0 version, where i am doing otp verification and finding below problems,

I found that on one of the sim which is primary on phone is sending otp only once and subsequent verification is happening instantaneously without waiting for user entering the OTP.
Now I want that OTP should be sent always without instantaneous verification.

On the secondary Sim, I am getting OTP along with the instant verification happening both at the same time. Now interesting part is when I enter the OTP sent then it gave platform exception saying: OTP expired and resend is required.

Any help is appreciated.
Thanks in Advance.

@deepaksinghdangi
The issue at https://github.com/flutter/flutter/issues/32562 has been closed and moved here. Future collaboration on this issue will be done here.

@deepaksinghdangi can you confirm it's the same with current flutter stable and firebase_auth 0.14.0+5?

Hi @deepaksinghdangi
This platform is not met for assistance on personal code.
Please see https://flutter.dev/community for resources for asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


rebased multiple loudness metadata

These are the changes from #100, rebased onto 2076-2, with a few fix-ups I spotted.
closes #84

Think I'm done with this if CI passes; it probably wants squishing into one commit.

Apparently this was already merged \o/


Show list of webview2 processes for a host app

In the Host Apps tab, under the details group, maybe a new tree view of the msedgewebview2.exe processes used by the selected host app.

Probably don't need this after all. The host app list gets multiple entries per hostapp x browser process. Child processes under the browser process isn't very useful. Current state is probably good enough.


Improve design of package size selection

This pr is to improve the design of the application and provide a better user experience.
Added a package size selector component that displays an icon for each option.
The options are mocked locally within the component for now.
Each option can be toggled and displays a purple background when selected.
Screenshot

Disclaimer.
Svg coloring (svg turning white when selected) was achieved by setting the filter property
in css. No support for IE11.

That's fine... nobody likes IE11 anyway 😉

Beautiful!
Thank you so much for the help and patience ❤


segfault in AlleleParser with 1.1.0 SeqLib development version

I'm running the lighterweight SeqLib fork from @walaj (PR #338) that builds cleanly on OSX and running into an issue. Here's is a reproducible test case:
https://s3.amazonaws.com/chapmanb/testcases/fb_allele_segfault.tar.gz
That exits with a string index error:
alignment: HS20_09413:8:1311:3352:83704
alignment: HS20_09413:8:1311:12434:81100
alignment: HS20_09413:8:1311:21344:58394
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::at

In a debugger, it looks like it's unhappy when parsing an alignment:
Program received signal SIGABRT, Aborted.
(gdb) bt
#0  0x00007ffff6de5c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007ffff6de9028 in __GI_abort () at abort.c:89
#2  0x00007ffff76efb05 in __gnu_cxx::__verbose_terminate_handler() () from /usr/local/share/bcbio_nextgen/anaconda/bin/../lib/libstdc++.so.6
#3  0x00007ffff76edca6 in ?? () from /usr/local/share/bcbio_nextgen/anaconda/bin/../lib/libstdc++.so.6
#4  0x00007ffff76edcd3 in std::terminate() () from /usr/local/share/bcbio_nextgen/anaconda/bin/../lib/libstdc++.so.6
#5  0x00007ffff76edef2 in __cxa_throw () from /usr/local/share/bcbio_nextgen/anaconda/bin/../lib/libstdc++.so.6
#6  0x00007ffff7743197 in std::__throw_out_of_range(char const*) () from /usr/local/share/bcbio_nextgen/anaconda/bin/../lib/libstdc++.so.6
#7  0x00007ffff774d3aa in std::string::at(unsigned long) () from /usr/local/share/bcbio_nextgen/anaconda/bin/../lib/libstdc++.so.6
#8  0x0000000000464b52 in AlleleParser::registerAlignment(SeqLib::BamRecord&, RegisteredAlignment&, std::string&, std::string&) ()
#9  0x0000000000467932 in AlleleParser::updateAlignmentQueue(long, std::vector<Allele*, std::allocator<Allele*> >&, bool) ()
#10 0x000000000046f8e6 in AlleleParser::getPartialObservationsOfHaplotype(Samples&, int, std::vector<Allele*, std::allocator<Allele*> >&) ()
#11 0x000000000046dbbe in AlleleParser::buildHaplotypeAlleles(std::vector<Allele, std::allocator<Allele> >&, Samples&, std::map<std::string, std::vector<Allele*, std::allocator<Allele*> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::vector<Allele*, std::allocator<Allele*> > > > >&, std::map<std::string, std::vector<Allele*, std::allocator<Allele*> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::vector<Allele*, std::allocator<Allele*> > > > >&, std::map<Allele*, std::set<Allele*, std::less<Allele*>, std::allocator<Allele*> >, std::less<Allele*>, std::allocator<std::pair<Allele* const, std::set<Allele*, std::less<Allele*>, std::allocator<Allele*> > > > >&, int) ()
#12 0x0000000000409dd2 in main ()

This works correctly in the 1.1.0 release so is something to help clean up #338 for more widespread use before pulling that in. Happy to provide any other info that would help and thanks for looking into the issue.

Good catch and thanks for the easy-to-recreate example. The issue was an over-aggressive check for empty quality strings that quit early for a 0 quality score (i.e. "!"). I just commented out those two lines.
I updated SeqLib and the PR freebayes branch to handle this. It works on the provided example.

Jeremiah;
Thanks so much for the quick fix. I updated the bioconda recipe with this update, much appreciated.


Feature/#25 ドキュメントの作成

Codecov Report

Merging #26 into develop will increase coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop      #26      +/-   ##
===========================================
+ Coverage    94.50%   94.55%   +0.04%
===========================================
  Files           27       27
  Lines          783      790       +7
===========================================
+ Hits           740      747       +7
  Misses          43       43

Impacted Files
Coverage Δ

kabutobashi/attributes/__init__.py
100.00% <ø> (ø)

kabutobashi/core.py
100.00% <ø> (ø)

kabutobashi/crawler/__init__.py
100.00% <ø> (ø)

kabutobashi/crawler/crawler.py
87.50% <ø> (ø)

kabutobashi/crawler/page.py
100.00% <ø> (ø)

...tobashi/crawler/stock_crawler/stock_detail_page.py
100.00% <ø> (ø)

...hi/crawler/stock_crawler/weeks_52_high_low_page.py
98.24% <ø> (ø)

kabutobashi/io/__init__.py
100.00% <ø> (ø)

kabutobashi/method/__init__.py
100.00% <ø> (ø)

kabutobashi/method/adx.py
90.90% <ø> (ø)

... and 17 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 7de905b...ee9e1d8. Read the comment docs.


RFP - Infinitex

Infinitex : A LaTeX and WYSIWYG editor with academic search functionality and other helpful tools
GitHub source: https://github.com/fetacore/Infinitex
GitHub releases: https://github.com/fetacore/Infinitex/releases

Status: Review

https://chocolatey.org/packages/infinitex
https://chocolatey.org/packages/infinitex.install
https://chocolatey.org/packages/infinitex.portable

The packages are approved. Thank you!


[Bug]: Users are getting errors when saving changes - 'Internal server error while processing request'

Is there an existing issue for this?

[X] I have searched the existing issues

Description
We've seen multiple users complain about users being unable to save the changes.
Steps To Reproduce
Internal Convo - https://theappsmith.slack.com/archives/CGBPVEJ5C/p1703091470645489
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
v1.9.57

The erroneous piece of code related to capturing telemetry has been reverted. 500 errors are not happening anymore.


Failed to call service media_player/play_media. 'NoneType' object is not iterable

Describe the bug
Cannot call routines. Everything else seems to work like TTS. This used to work as of a few days ago so I am not sure what has changed
To Reproduce
Steps to reproduce the behavior:

Go to 'Developer Tools
Go to Services
Use media_player.play_media and:

entity_id: media_player.echo_spot
media_content_id: weather
media_content_type: routine

Expected behavior
When I try to CALL SERVICE I get:
Failed to call service media_player/play_media. 'NoneType' object is not iterable
Screenshots

System details

Home-assistant (version): 2021.01.7
Hassio (Yes/No): Yes
alexa_media  (version from const.py or HA startup): 3.6.2
alexapy (version from pip show alexapy or HA startup): 1.22.2
Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered: Yes

Logs
Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/alexa_media/media_player.py:1273
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 7:47:35 AM (5 occurrences)
Last logged: 7:50:11 AM

[1796920992] 'NoneType' object is not iterable
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 135, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1445, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1480, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
    await self.hass.helpers.service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 593, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 664, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 630, in _handle_entity_call
    await result
  File "/config/custom_components/alexa_media/helpers.py", line 161, in _catch_login_errors
    result = await func(*args, **kwargs)
  File "/config/custom_components/alexa_media/media_player.py", line 1273, in async_play_media
    await self.alexa_api.run_routine(
  File "/usr/local/lib/python3.8/site-packages/alexapy/helpers.py", line 146, in wrapper
    return await func(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/alexapy/alexaapi.py", line 605, in run_routine
    for automation in automations:
TypeError: 'NoneType' object is not iterable

Additional context

I have the same problem.... the routine worked about 4 hours ago and has stopped working in that time.
Home Assistant Version: 2021.01.5, Supervisor Version 2021.01.7, media player version 3.6.2 and I do use 2FA.
I also deleted the intergration and reinstalled/reuthorised and the problem persists

I have the same problem.... the routine worked about 4 hours ago and has stopped working in that time.
Home Assistant Version: 2021.01.5, Supervisor Version 2021.01.7, media player version 3.6.2 and I do use 2FA.
I also deleted the intergration and reinstalled/reuthorised and the problem persists

Same here. Automation/script to run routine worked last night, now throwing this error. I have not done anything except reboot home assistant earlier today to reflect an unrelated config change.

Same here. Automation/script to run routine worked last night, now throwing this error. I have not done anything except reboot home assistant earlier today to reflect an unrelated config change.

Same here, must be a change on amazons side thats breaking this.

Same here, must be a change on amazons side thats breaking this.

Is this only for routines or do other things like sequences break?

Is this only for routines or do other things like sequences break?

Looks like Amazon removed the page we needed to find the routines. I'll need to investigate if there's a replacement or not. If there isn't, then we won't be able to do this anymore.

Looks like Amazon removed the page we needed to find the routines. I'll need to investigate if there's a replacement or not. If there isn't, then we won't be able to do this anymore.

Ok I found the new url. Preparing a new release.

Ok I found the new url. Preparing a new release.


Do not re-route when searching in route-disabled listing

When using a grid in a component with the listing mixin, the onSearch method of the listing mixin will always re-route the page in the updateRoute method even if disableRouteParams is set true.
https://github.com/shopware/platform/blob/5453c5a7c5a2194b65b4a123696389e570e5a512/src/Administration/Resources/administration/src/app/mixin/listing.mixin.js#L189-L199
This PR fixes this by returning early, if disableRouteParams is set true, which does not re-route the page. This behaviour is similar to the methods onPageChange or onSortColumn which also return early. https://github.com/shopware/platform/blob/5453c5a7c5a2194b65b4a123696389e570e5a512/src/Administration/Resources/administration/src/app/mixin/listing.mixin.js#L175-L178 https://github.com/shopware/platform/blob/5453c5a7c5a2194b65b4a123696389e570e5a512/src/Administration/Resources/administration/src/app/mixin/listing.mixin.js#L209-L218

hey @hanneswernery
thanks for your PR :+1:  we need to test the changes first. please give us some time.

thanks for your contribution! :+1: :tada: :blue_heart:


How to assign independent mapping quality scores to split read alignments for bam files?

Hi,
I want to apply the tool to some TCGA samples, which already have the bam files available. I see the second step is using BWA with -q option. I think the preprocessing of TCGA sample did not use this option. So how can I do this in samtools or similar tools?

Best,
Shixiang

I think you can use bazam and bwa to realign you bam file.

Thanks :)


Error message not readable during release process

🐛 Bug report
Current Behavior
error message not displaying correctly during staging/production release process.

Expected behavior
Error message shows real errors.
Reproducible example
run yarn staging or yarn production
Suggested solution(s)
Will need to log object key values. right now full object is attempting to log.
Additional context

Your environment

npx envinfo --npmPackages '@availity/*' --binaries

Fixed in #457


Empty logs on Docker

Describe the bug
Logs are being empty despite lots of messages printed to the console
To Reproduce
Steps to reproduce the behavior:

Run Miscord in Docker

Expected behavior
Logs should contain the same messages as the console
Specifications:

OS: Docker
Version (miscord -v): 4.1.1
Node.js version (node -v): 10.latest

Mentioned before in #331.


added .gitignore, changed pom.xml, improved downloadSpigot.bat

I'm Japanese and my English is not good (I may use translations) please understand...
Changes:

don't let git commit files that don't want... (.gitignore)
"org.spigotmc:spigot:1.15-R0.1-SNAPSHOT" is when run "downloadSpigot.bat", it doesn't add it to the local repository. The build fails, so I changed to a more reliable method.  (1.13CommandAPI/commandapi-${mc-ver}/pom.xml , 1.13CommandAPI/commandapi-core/pom.xml)
I changed the batch file a bit because I didn't want the garbage left in the root folder after I built Spigot. (downloadSpigot.bat)

Please let us know if you have any problems.
If you don't need this pull request or only need part of it, you may close it.

Hi! Currently, my downloadSpigot.bat file is misleading. (今、私 の downloadSpigot.bat は 紛らわしです).
When you run BuildTools.jar, the spigot jar is automatically added to your local machine's maven repository. As a result, this pull request is not needed.
However, I like your .gitignore file and will include it!.

I understand!
However, in the current version of downloadSpigot.bat, the 1.15 dependency Probably not resolvable; change to 1.15.2 because it adds a dependency on 1.15.2 I think you need to do that.
So I think you need to change the pom.xml, I think.
(Probably this is why the build failed :()
Then, the ".gitignore" is supposed to be based on my batch file, and it's supposed to be It doesn't ignore Spigot or Bukkit folders. So, "libs/" and "build-works" are no longer needed and you can add
I think you'll need to add a "work/", "Bukkit/", "Spigot/", "BuildData/", "CraftBukkit/"
ありがとうございました！

自分の英語や翻訳の質が不安なので、日本語も残しておきます
わかりました！
しかしながら、現在のdownloadSpigot.batでは、1.15の依存関係はおそらく解決できません。1.15.2の依存関係が追加されるため、1.15.2に変更する必要があるように思います。
なので、pom.xmlを変更する必要があると私は思います。
(おそらくこれが原因でビルドに失敗しました :()
それから、この".gitignore"は、私のバッチファイルを基準に考えられており、Spigot や Bukkitフォルダーをignoreしません。なので、"libs/"や"build-works"は不要になり、追加で
"work/"、"Bukkit/"、"Spigot/"、"BuildData/"、"CraftBukkit/" の追加が必要になると思います。
ありがとうございました！

I have updated the Linux/MacOS version (downloadSpigot.sh) which is a lot better (in this commit: ad6580707b7122bb1e607e30b48c47df80fc31c8). I hope to update downloadSpigot.bat later to be just as good.
少しの日本語ができます。私は日本語がじょうずじゃありません。でも、どういたしまして！


Fix issue with GC killing the call

Move CallClient and CallAgent to the global scope

@juancamilor : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @juancamilor - Would you make this content update in the private repo instead? Thank you! We'll close this PR.


Use official github actions cache for Windows

Noticed windows builders are using the old cache plugin I had set up in a fork. We should try the new one now it has had some time to stabilize.

Aren't there newer versions than v2 now? I thought I found much higher numbers last time I checked (on phone now).

Aren't there newer versions than v2 now? I thought I found much higher numbers last time I checked (on phone now).

Looks like latest is v2.1.4

Aren't there newer versions than v2 now? I thought I found much higher numbers last time I checked (on phone now).
And if there are newer versions, we should use latest for all CI builds.

specifying @2 will use 2.2 as it's the latest :)

also it can wait until Monday was just a passing thought as to why we have problems sometimes on windows, according to them they fixed some of the problems

Thanks!

Cherry-picked for 3.2.4.


[engine] check_for_waiting_pull_request needs to also check CheckRuns

Cocoon is getting support for github checks api, once the luci builds start creating checkRuns the status will not be added.  The check_for_waiting_pull_request handlers will need to validate status and checkRuns from github.

This is blocking enabling the checks api on the engine repository.


Stop slider animation on display and dimension changes

Description
The original bug description covered the case when a single 3D image layer is played, removed, and then readded - in which case it was still playing.
This PR fixes that issue by stopping the playback animation whenever the number of sliders changes. When a 3D image is playing and is then removed Dims.ndim goes from 3 to 2.
I also handled the similar case when the display goes from 2 to 3, in which case we should also stop now.
It's possible there are some more cases I haven't thought of, or there might be a good general place to put stop that would catch everything, but I couldn't think of one. Open to ideas and other test cases!
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References
Closes #3998.
How has this been tested?

[x] added new tests to reproduce the original bug and a variant
[ ] all tests pass with my change
[x] I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

@tlambert03 : I assigned you to review only because I saw your name from git blame around my changes - feel free to unassign if you're unfamiliar with this code.

oh yeah... this pile of garbage is mine :joy:

The test failures (ubuntu-latest 3.9 pyqt5 and macos-latest 3.9 pyqt5) are new and inexplicable (at least to me...) - any ideas?

The test failures (ubuntu-latest 3.9 pyqt5 and macos-latest 3.9 pyqt5) are new and inexplicable (at least to me...) - any ideas?

I changed the animation worker thread to connect from the finished signal to the play_stopped signal rather than the play_stopped.emit method. I think that's a potential fix because I believe Qt does a few more checks when connecting signals->slots or signals->signals rather than signals->methods/functions. But I don't know enough about the details about Qt, qtpy, pyqt, and pyside. Any insight would be appreciated.

I marked this as a draft because I don't exactly understand my fix yet and don't want to add a flaky test to napari. When I do understand it, I'll unmark it as a draft and will likely merge it soon after.

After looking at this fresh, I am happy enough with this.
I understand a little more about what's going on under the hood of pyqt5, when we connect to a Python callable instead of a signal. In particular, when the callable is recognizable as a signal, the receiver is the QObject that owns that signal.
When we previously connected to play_stopped.emit, the instance that emit is bound to is of the type pyqtSignal, which isn't recognizable as a QObject, at which point pyqt has to create a slot proxy and moves it to the thread of the receiver.
My understanding ends when trying work our what receiver will be our case. Is it just the instance of pyqtSignal? In that case maybe we truly confused pyqt's guessing logic and made it behave really strangely? Note that pyside has a notion of a global receiver, which may explain why it avoided similar issues.

@tlambert03 : as you approved this already and nothing really changed, I'll likely merge this in 24 hours.
Lessons learned from this PR. Avoid connecting to plain Python callables when possible. And really avoid connecting to callables bound to instances of pyqtSignal!

Lessons learned from this PR. Avoid connecting to plain Python callables when possible. And really avoid connecting to callables bound to instances of pyqtSignal!

works for me!  given the number of actively burning fires, anything that works is 100% welcome!  Merge any time!


Update cilium to v1.12.10

Issue #, if available:
Description of changes:
Update the Cilium version to v1.12.10.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


[Bug]: Replica cluster require a restart after promote

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
No response
Version
1.22.2
What version of Kubernetes are you using?
1.29
What is your Kubernetes environment?
Self-managed: kind (evaluation)
How did you install the operator?
YAML manifest
What happened?
when replica cluster promoted, archive_mode changed from always to on but primary is not restart, once scale up the cluster, primary will restart.
Cluster resource
No response
Relevant log output
No response
Code of Conduct

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

More description
For the replica clusters, if the replica cluster has one instances,  the archive_mode is set to always in primary.
once the designated primary is promote to primary, the archive_mode is changed to on, but primary did not have a restart. this restart delay to the time when scale up the new cluster, as primary restart in scale up is not as expected, we should restart primary during the promoting time.

when we promote a cluster, the instance reconciler will write new custom.conf file with archive_mode=on, and return a reloadNeeded=true flag
	// Reconcile cluster role without DB
	reloadClusterRoleConfig, err := r.reconcileClusterRoleWithoutDB(ctx, cluster)

But this reload will not happen, as in this line we get replica cluster promoted by pg_ctl promote, this function return a restart=true to indicates that a pg_ctl promote is called.
restarted, err := r.reconcilePrimary(ctx, cluster)

 `pg_ctl promote` does not use the changed configuration file in custom.conf,

as following code show, the instance reload only been called when there is no restart. so we miss the reload here
if reloadNeeded && !restarted {
		contextLogger.Info("reloading the instance")
		if err = r.instance.Reload(ctx); err != nil {
			return reconcile.Result{}, fmt.Errorf("while reloading the instance: %w", err)
		}
		if err = r.processConfigReloadAndManageRestart(ctx, cluster); err != nil {
			return reconcile.Result{}, fmt.Errorf("cannot apply new PostgreSQL configuration: %w", err)
		}
	}

And in next reconfile loop, as there is no file change, there is no reload needed.
so the reload is skipped here.


Bug: Nord theme is using the wrong colors

If the theme is intended to be based on Nord colors:
#3d4252 should be  #3b4252
#d8dee9 should be #d8dee9
Steps to fix

Update the theme file with the correct colors

Do you want to open a PR with this change?

I've created a pull request: #10466


Model request:  EXAONE-3.5-2.4B-Instruct

these EXAONE models are nice

I'll try implementing this

Yes saw the release from LG - very cool! It looks like a custom arch I think? https://huggingface.co/LGAI-EXAONE/EXAONE-3.5-32B-Instruct/blob/main/config.json

Hope this gets implemented soon! :)


Feature: additional endpoint configuration for RO

Would like to be able to provide a configuration to spicedb that states an endpoint for writing and an endpoint for reading.
This provides the ability for removing bottlenecks in the network and obtaining HA by scaling out on what is a very read intensive application.

@elebiodaslingshot just to clarify, are you referring to different endpoints to separate reads and writes towards the backing datastore? or the SpiceDB API?

(assuming the answer to @vroldanbet's question is that you want separate SpiceDB api endpoints)
You should be able to achieve this with the operator today: spin up two SpiceDB clusters talking to the same datastore, and configure one of them as read-only.
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: readwrite
spec:
  config:
    datastoreEngine: postgres
  secretName: spicedb-config
---
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: readonly
spec:
  config:
    datastoreEngine: postgres
    datastoreReadonly: "true"
  secretName: spicedb-config
---
apiVersion: v1
kind: Secret
metadata:
  name: spicedb-config
stringData:
  datastore_uri: "postgres://<your backend>"
  preshared_key: "averysecretpresharedkey"

That will result in two clusters, one of which is readonly, and two Services in the cluster that you can route traffic to.
Is that what you were looking for? Did you try it and run into an issue?

@elebiodaslingshot just to clarify, are you referring to different endpoints to separate reads and writes towards the backing datastore? or the SpiceDB API?

yes, seperate reads and writes towards the backing datastore

(assuming the answer to @vroldanbet's question is that you want separate SpiceDB api endpoints)
You should be able to achieve this with the operator today: spin up two SpiceDB clusters talking to the same datastore, and configure one of them as read-only.
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: readwrite
spec:
  config:
    datastoreEngine: postgres
  secretName: spicedb-config
---
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: readonly
spec:
  config:
    datastoreEngine: postgres
    datastoreReadonly: "true"
  secretName: spicedb-config
---
apiVersion: v1
kind: Secret
metadata:
  name: spicedb-config
stringData:
  datastore_uri: "postgres://<your backend>"
  preshared_key: "averysecretpresharedkey"

That will result in two clusters, one of which is readonly, and two Services in the cluster that you can route traffic to.
Is that what you were looking for? Did you try it and run into an issue?

This is a solution but results in loss of a consolidated api

@elebiodaslingshot I'm afraid supporting this is not trivial, not because it can't be implemented - it would be trivial to add this to SpiceDB - but because it has implications for the consistency model exposed by SpiceDB.
TL;DR: before we can separate read/write traffic, MySQL and PostgreSQL datastore implementations, need to be reengineered to support read-replicas.
See, one of SpiceDB's key features is its tunable consistency model, which clients can define, and leverages ZedTokens to represent a consistent snapshot of the system's state. Correct me if this is not your case though: typically folks want to use separated endpoints in order to send traffic to either a primary or to a cluster of replicas, with the goal of offroading read traffic from the primary for scalability reasons. While this does not break the consistency model by itself, it could depending on the configuration of the backing datastore: a cluster of read replicas will typically lag behind its primary, which can lead to an inconsistent view of the world for SpiceDB and end up defeating the foundations of the service to defeat the "New Enemy Problem". A cluster of read replicas with synchronous replication is possible, but would probably defeat the initial goal of scaling database reads.
Datastores like CockroachDB and Spanner don't have this problem because they have first-class support primitives to expose the underlying MVCC of the database, which SpiceDB leverages to implement its consistency model. We are aware there are options to explore on the PostgreSQL and MySQL side, but the engineering required for adding support for separated endpoints dwarfs in comparison to supporting consistent world-view over lagged replicas.
Needless to say, SpiceDB could support such separation if you are willing to accept that none of the consistency models exposed in our API will honor its semantics and that everything becomes eventually consistent.

This is an excellent response and much appreciated. I have taken a look at Zookies which solve the consistency "somewhat" as it does not guarantee the latest ACL but one newer than the timestamp on the Zookie, correct me if I am wrong. Basing my stuff off this paper: https://www.usenix.org/system/files/atc19-pang.pdf
To your one question yes that is the usecase here to offload from the primary. I think given that our usecase doesnt represent a banking platform eventual consistency is fine especially if we get Zookies implemented across our systems.
Parhaps we should have went with cockroachDB maybe down the road we can switch.

@elebiodaslingshot zookies won't solve the latest ACL nor they are meant for that - it's a causality token. But SpiceDB allows you to ask for the "freshest ACL at the time of the request" with fully_consistent.
That's the thing - you won't be able to rely on zookies if you are offloading traffic to a read-replica, unless SpiceDB is modified to account to replication across primaries and replicas. As I said, we know there are options to explore.
What I'm suggesting is that you can't relly on any of the consistency options we provide in our API the moment you hit a replica, because it could be lagged, and SpiceDB works on the assumption that it's talking to an instance that has the freshest state of the world.

Ok, I see now. I think that answers everything then.

Opened https://github.com/authzed/spicedb/issues/1320 and https://github.com/authzed/spicedb/issues/1321


fix: adjusted SCP to allow workload accounts the ability to create budgets

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
This adjusts a SCP by removing a blocked permission...
"aws-portal:ModifyBilling"

... to allow workload accounts the ability to create and manage their own Budgets. See here for required permissions.

Should this not be: budgets:ModifyBudget.  We definitely do not want sub-account users modifying the Account/Billings tab...

Should this not be: budgets:ModifyBudget. We definitely do not want sub-account users modifying the Account/Billings tab...

The user also must have ModifyBilling to create a budget. "To allow IAM users to modify these console [Budgets] pages, you must allow both ModifyBilling and ViewBilling." Since the workload accounts are within an AWS Organization and consolidated billing, those screens don't present any option to modify.

I'm not comfortable opening this up for all customers and going to suggest this be a customer specific customization, for those that feel it is appropriate to their user base.  You also need to be careful, if the ASEA provided budget is removed, it will cause the SM to fail (in certain situations).


Environment and Computer Specs Used During Training and Testing

Hello,
Sorry to ask again, but I couldn't find it in your paper, but what were the specs of the computer used for your training and testing? I saw on the paper that you had 2 GPUs.

For the checkpoints provided in this repo, I use two 1080Ti.

Thank you!
On Sun., Dec. 1, 2019, 01:00 D-X-Y<EMAIL_ADDRESS>wrote:

For the checkpoints provided in this repo, I use two 1080Ti.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/D-X-Y/landmark-detection/issues/54?email_source=notifications&email_token=AC7NDCQSHAGTK3LSZ7HVBLTQWNHH7A5CNFSM4JTJ7KIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQ54AY#issuecomment-560061955,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7NDCR2K6J22PUFWKCXVKDQWNHH7ANCNFSM4JTJ7KIA
.

You are welcome.


Adds additional fields in (google) feed to show price in square meter…

Adds additional fields in (google) feed to show price in square meters for stone products.

Implementation is done on top-level projects. PR can be discarded.


Add how to fully remove PowerToys (and the settings) to the docs

Provide a description of requested docs changes
Add how to fully remove PowerToys (and the settings) to the docs. Including cleanup %programfiles%\PowerToys and %localappdata%\Microsoft\PowerToys (and etc if I am missing anything(.

There is a cleanup script:

https://github.com/microsoft/PowerToys/tree/main/tools/CleanUp_tool
https://github.com/microsoft/PowerToys/tree/main/tools/CleanUp_tool_powershell_script

There is a cleanup script:

https://github.com/microsoft/PowerToys/tree/main/tools/CleanUp_tool
https://github.com/microsoft/PowerToys/tree/main/tools/CleanUp_tool_powershell_script

I didn't know we have this! I think we'll need to see if this is outdated. Last commit is in 2020 😄

looking at this, the tool is old based on reg keys.  it needs IMO to pull data from the WSX or a shared file for reg stuff.

what is left behind in %programfiles%\PowerToys

Sometimes there are files that failed to update left in %programfiles%\PowerToys that need to be manually deleted. But this is not always reproducible.

We need more tangible proof.  I feel like script is more powerful than the cpp since if you uninstall PT, it won't do any good.


Pandoc, ReStructuredText support?

Pweave also supports pandoc and rst formats. Is there any plan to incorporate these in this plugin? If you don't have the time for it, do you have any idea approximately how long it might take?

Probably just a matter of swapping out the tex syntax for another, especially if the file extension is sufficient to distinguish between the variants. I'm not likely to try it soon, but would welcome a pull request.

Hrm... for markdown, this can be avoided entirely by using vim-pandoc and adding this to your .vimrc:
    au BufNewFile,BufReadPost *.Pmd,*.pmd,*.mdw set filetype=pandoc
    au BufNewFile,BufReadPost *.Pmd,*.pmd,*.mdw PandocHighlight python

So maybe it's not worth adding markdown support. Not sure about rst.


Fix overextending of variable name

Before: outPath=./output_$outPlattform_$outArch
Variable referenced is outPlattform_
The shell includes the subsequent underscore as part of the variable name.
Before: outPath=./output_${outPlattform}_$outArch
Variable referenced is outPlattform

Thanks!


Merging EDF Scheduler to the mainline tree

This is an initial tested and verified kernel implementation for the EDF scheduler type. Using EDF the kernel always needs to assure that the tasks meet its deadline.
Added some examples for the use of EDF scheduling to verify the schedulability of the system.
Added # macros guards so the kernel can compiled with the static priority scheduler or the EDF Scheduler.

This is an initial tested and verified kernel implementation for the EDF scheduler type. Using EDF the kernel always needs to assure that the tasks meet its deadline.
Added some examples for the use of EDF scheduling to verify the schedulability of the system.
Added # macros guards so the kernel can compiled with the static priority scheduler or the EDF Scheduler.


Add signals for adding and removing nodes from groups.

This PR is in response to proposal: https://github.com/godotengine/godot-proposals/issues/766
It adds four new signals in total, two to Node and two to SceneTree. The two new signals on Node are:

grouped(node: Node, group: StringName)
ungrouped(node: Node, group: StringName)

These are emitted when a node is added to, or removed from a group (respectively). They will be emitted regardless of whether or not the node is currently part of the SceneTree, as we're connecting to the individual Node itself.
I had some debate on whether I should include node as one of the arguments sent with the signal, but I decided to include it in the end, as it allows these signals to be connected to multiple different nodes, but use the same method and still make it possible to determine which node emitted the signal.
The remaining two signals belong to SceneTree, and mirror those for Node, but have a distinctly different behavior.

node_grouped(node: Node, group: StringName)
node_ungrouped(node: Node, group: StringName)

These signals will emit for any node, but only so-long as they are currently inside the scene-tree. node_grouped will be emitted for each group a node belongs to, when it enters the scene-tree. Correspondingly, node_ungrouped will emit for each group a node belongs to, when it leaves the scene-tree. If a node is added to, or removed from a group while inside the scene-tree, the corresponding signal will emit.
I would like to note that I'm open to suggestions for better signal-names. I don't believe the signal names for SceneTree fully convey their difference from those on Node, but I'm unable to come up with a better set of names. I originally had node_added_to_group/added_to_group as examples, but I don't think those are any more descriptive--just physically longer.
The benefits of this approach:
Interested parties have the option of narrowly watching group changes to specific nodes, or widely watching changes to entire groups, with the additional benefit of being alerted when nodes belonging to certain groups enter and exit the tree.
This greatly simplifies any code that requires up to date information on changes to groups (such as code that would track enemies with specific traits or types), as scripts can now be updated on the specific changes and the nodes affected, vs asking the tree for all nodes in a group and comparing it to a cached version.
The deficiencies of this approach:
Upon game start, for nodes in the default scene, there is no point within GDScript, in which you can connect these signals before they would be emitted, if the nodes have groups that were added in the editor. Or to put it another way, editor defined groups will only emit a receivable signal if the scene is instantiated after the game is started.
There is also the issue that the engine itself uses some groups internally, and these will be occasionally added and removed from nodes, with no way of filtering them out from user-defined groups. This means that receivers of these signals will need to filter based on group, and not implicitly trust that only user-defined groups will trigger these to emit.

Don't forget to fix the conflicts.

Don't forget to fix the conflicts.

Sorry, completely overlooked. I tried to squash the commits, and maybe I'm just not competent enough with git, but any attempt at squashing causes git to complain about the conflict again, so I've left it as the original commit and the conflict resolve merge.

I've checked the CI error. It's a static error, that is not clear to me and I'm not sure how to solve it. Probably @akien-mga can help with it.

I've checked the CI error. It's a static error, that is not clear to me and I'm not sure how to solve it. Probably @akien-mga can help with it.

The log shows it, there's a style issue:
https://travis-ci.org/github/godotengine/godot/jobs/688979874
The following differences were found between the code to commit and the clang-format rules:

--- a/scene/main/scene_tree.cpp	2020-05-19 20:25:26.939861491 +0000
+++ b/scene/main/scene_tree.cpp	2020-05-19 20:25:35.959795372 +0000
@@ -119,12 +119,10 @@
 }

 void SceneTree::node_grouped(Node *p_node, const StringName &p_group) {
-
 	emit_signal(node_grouped_name, p_node, p_group);
 }

 void SceneTree::node_ungrouped(Node *p_node, const StringName &p_group) {
-
 	emit_signal(node_ungrouped_name, p_node, p_group);
 }

Is this change still expected to go in 4.0 (it's been inactive over a year)? It would be very useful to be able to get these signals when nodes are added/removed from groups... Thanks.

We've rejected the proposal, so I'm closing this PR. Thanks for contributing nonetheless!

Very disappointed to see this wasn't accepted. Groups are really only useful for statically evaluated things without some notion of signaling for group addition/removal. Almost all games have some element of dynamic spawning to their scenes so this seems like a pretty big oversight.
Case in point, I have some actors with statically categorized groups (i.e. applied in the editor) but that spawn dynamically (enemies). If I added all groups myself via script, I could call my own function that wraps Node.add_to_group but this doesn't work for groups that were configured by the editor because core is what is doing the group add on node spawn.
As it is, the best user-land solution that I can come up with is to have a global GroupManager class that keeps its own concept of "groups", exposes a function to wrap Node.add_to_group and also has to watch the scene tree for nodes added with groups already applied. At this point I'm basically writing my own groups implementation and the only bit missing is the core editor integration. The ergonomics are worse (having to call a wrapped method), it doesn't work with shared code (which might dynamically add groups without using my wrapper), and it violates the principle of least surprise since the editor already has a groups implementation a teammate would reasonably expect to be able to use.
It's certainly possible to work around, but groups feels like an incomplete feature at the moment and given the PR was done and is fairly light touch, I think it would be worth giving it a second look for feature completeness sake.


Release for L/Unix

Hey bro, Ret player & Programmer. Any plan to make a release on MacOS? Anything I could help, though I do not know C#.... I work on macos.

Operating Systems
As our project uses WPF, it is limited to Windows only for now. However, we may consider Linux / macOS releases at a later point. If you're a Linux or macOS user who wants to help us test releases for those systems, contact us.

I second this but also for Linux.  As of right now due to the requirement of Webview2, this cannot be run on Wine.  I believe Webview2 requires dotnet 4.7.2 but Winetricks cannot install beyond dotnet 4.6.2.  So I gotta run Windows in a virtual machine in order to run RetSim.

no worries. afk -ed. no more wow.


Apel plugin: Build pyauditor from source for docker image

Instead of installing pyauditor from PyPI it is now built from the current version of the git repo
Closes #452

No update in the changelog, because we already have this line:
- Apel plugin: Docker image ([@QuantumDancer](https://github.com/QuantumDancer))

Cross-check, that really the latest version is used:
$ docker buildx build -t auditor-apel-plugin -f containers/auditor-apel-plugin/Dockerfile .
$ docker run -it --rm auditor-apel-plugin /bin/bash
root@56360699644f:/app# pip freeze
auditor-apel-plugin @ file:///code/plugins/apel
certifi==2023.7.22
cffi==1.15.1
charset-normalizer==3.2.0
cryptography==41.0.3
idna==3.4
pycparser==2.21
python-auditor @ file:///code/pyauditor/python_auditor-0.1.0-cp38-cp38-linux_x86_64.whl#sha256=2a72126082fbf80cbc456505f3111c9fbcd4cf070ef0680b6f49015e0f21a720
requests==2.31.0
urllib3==2.0.4


mUU sends malformed hubcli command when more than one point update is available for a major macOS version

Describe the bug
Have a Mac running macOS 13.6. It is missing macOS 13.6.1 and macOS 13.6.2.
:PublicAssetSets:macOS in /private/var/macOSUpdater/OS.plist has entries for both macOS 13.6.1 and macOS 13.6.2.
Line 1076 of macOSUpdater.sh greps "ProductVersion = $currentMajor" in which the return value is:
ProductVersion = 13.6.1
ProductVersion = 13.6.2
Once macOSUpdater.sh trims "ProductVersion =" out, it is left with
13.6.1
13.6.2
macOSUpdater then tries to send the following MDM command (as confirmed with Crescendo):
/usr/local/bin/hubcli mdmcommand --osupdate --productversion 13.6.1\n13.6.2 --installaction DownloadOnly
This causes hubcli to return the man page for hubcli mdmcommand.
Reproduction steps

Have a Mac that is running a version of macOS that is at least 2 point versions older than the latest version of macOS available. For example, current version of macOS Ventura as of this writing is macOS 13.6.2. So grab a Mac that is running macOS 13.6 (missing macOS 13.6.1 and macOS 13.6.2).
Ensure mUU is configured to install "latest" version of macOS available and execute macOSUpdater.sh (either manually or as a WSONE script).

Expected behavior
When macOSUpdater.sh matches more than one major OS version in /private/var/macOSUpdater/OS.plist, it should pick the highest version number returned by the command in line 1076 of macOSUpdater.sh.
Additional context
No response

macOSupdater.log

OS.plist.zip


Fix unittest for analogRead() issues

initial unittest has some commented tests. Need fix.

partial fix with godmode for mA_DDC() as that does only 2 analogReads.
mA_AC is currently not possible,

partial fix with godmode for mA_DDC() as that does only 2 analogReads.
mA_AC is currently not possible,


API_streams shows zero connected clients

Home Assistant release with the issue:

0.80-0.83.x
Last working Home Assistant release (if known):
0.79.3
Operating environment (Hass.io/Docker/Windows/etc.):

Hassio
Component/platform:

API Stream Sensor
Description of problem:
The sensor doesn't update since 0.80.0
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
sensor:
  - platform: api_streams

Traceback (if applicable):

Additional information:

Duplicate of #17397.

@fabaff, issue #17397 was closed without resolving it or any other good reason.

I'm unable to reproduce the issue. I see my sensor.connected_clients entity updating when I connect to websocket stream

For what it's worth, I had to follow the suggestion of creating the sse.html file and browsing to that to get a client to show up. Perhaps the frontend no longer uses /api/stream?

How were you triggering a change in this sensor before?

@aneisch, I believe that I have some settings that use API, hower, I still don't see that it would change the values of the sensor.

This issue hasn't been resolved so far.