RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'

ComfyUI Error Report
Error Details

Node Type: Mecha Merger
Exception Type: TypeError
Exception Message: RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'

Stack Trace
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)

  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\comfy-mecha\nodes\merge_nodes.py", line 198, in execute
    merger.merge_and_save(

System Information

ComfyUI Version: v0.2.2-1-gc27ebeb
Arguments: ComfyUI\main.py --port 7821 --extra-model-paths-config D:\My Stuff\Extra Stuff\SwarmUI\Data/comfy-auto-model.yaml --preview-method latent2rgb
OS: nt
Python Version: 3.11.8 (tags/v3.11.8:db85d51, Feb  6 2024, 22:03:32) [MSC v.1937 64 bit (AMD64)]
Embedded Python: true
PyTorch Version: 2.2.2+cu121

Devices

Name: cuda:0 NVIDIA GeForce RTX 3060 : cudaMallocAsync

Type: cuda
VRAM Total:<PHONE_NUMBER>8
VRAM Free:<PHONE_NUMBER>2
Torch VRAM Total: 0
Torch VRAM Free: 0

Logs
2024-09-06 22:00:41,073 - root - INFO - Total VRAM 12287 MB, total RAM 32702 MB
2024-09-06 22:00:41,073 - root - INFO - pytorch version: 2.2.2+cu121
2024-09-06 22:00:41,073 - root - INFO - Set vram state to: NORMAL_VRAM
2024-09-06 22:00:41,074 - root - INFO - Device: cuda:0 NVIDIA GeForce RTX 3060 : cudaMallocAsync
2024-09-06 22:00:42,342 - root - INFO - Using pytorch cross attention
2024-09-06 22:00:42,816 - root - INFO - [Prompt Server] web root: D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\web
2024-09-06 22:00:42,818 - root - INFO - Adding extra search path checkpoints D:\My Stuff\Extra Stuff\SwarmUI\Models\Stable-Diffusion
2024-09-06 22:00:42,818 - root - INFO - Adding extra search path vae D:\My Stuff\Extra Stuff\SwarmUI\Models\VAE
2024-09-06 22:00:42,818 - root - INFO - Adding extra search path vae D:\My Stuff\Extra Stuff\SwarmUI\Models\VAE
2024-09-06 22:00:42,818 - root - INFO - Adding extra search path loras D:\My Stuff\Extra Stuff\SwarmUI\Models\Lora
2024-09-06 22:00:42,818 - root - INFO - Adding extra search path loras D:\My Stuff\Extra Stuff\SwarmUI\Models\Lora
2024-09-06 22:00:42,818 - root - INFO - Adding extra search path loras D:\My Stuff\Extra Stuff\SwarmUI\Models\LyCORIS
2024-09-06 22:00:42,818 - root - INFO - Adding extra search path upscale_models D:\My Stuff\Extra Stuff\SwarmUI\Models\ESRGAN
2024-09-06 22:00:42,818 - root - INFO - Adding extra search path upscale_models D:\My Stuff\Extra Stuff\SwarmUI\Models\RealESRGAN
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path upscale_models D:\My Stuff\Extra Stuff\SwarmUI\Models\SwinIR
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path upscale_models D:\My Stuff\Extra Stuff\SwarmUI\Models\upscale-models
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path upscale_models D:\My Stuff\Extra Stuff\SwarmUI\Models\upscale_models
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path embeddings D:\My Stuff\Extra Stuff\SwarmUI\Models\Embeddings
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path embeddings D:\My Stuff\Extra Stuff\SwarmUI\Models\embeddings
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path hypernetworks D:\My Stuff\Extra Stuff\SwarmUI\Models\hypernetworks
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path controlnet D:\My Stuff\Extra Stuff\SwarmUI\Models\controlnet
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path controlnet D:\My Stuff\Extra Stuff\SwarmUI\Models\ControlNet
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path clip_vision D:\My Stuff\Extra Stuff\SwarmUI\Models\clip_vision
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path clip_vision D:\My Stuff\Extra Stuff\SwarmUI\Models\clip_vision
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path custom_nodes D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\DLNodes
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path custom_nodes D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\ExtraNodes
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path clip D:\My Stuff\Extra Stuff\SwarmUI\Models\clip
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path unet D:\My Stuff\Extra Stuff\SwarmUI\Models\unet
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path diffusion_models D:\My Stuff\Extra Stuff\SwarmUI\Models\diffusion_models
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path gligen D:\My Stuff\Extra Stuff\SwarmUI\Models\gligen
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path ipadapter D:\My Stuff\Extra Stuff\SwarmUI\Models\ipadapter
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path yolov8 D:\My Stuff\Extra Stuff\SwarmUI\Models\yolov8
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path tensorrt D:\My Stuff\Extra Stuff\SwarmUI\Models\tensorrt
2024-09-06 22:00:42,820 - root - INFO - Adding extra search path clipseg D:\My Stuff\Extra Stuff\SwarmUI\Models\clipseg
2024-09-06 22:00:47,666 - root - INFO -
Import times for custom nodes:
2024-09-06 22:00:47,666 - root - INFO -    0.0 seconds: D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\websocket_image_save.py
2024-09-06 22:00:47,666 - root - INFO -    0.0 seconds: D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\DLNodes\ComfyUI-SAI_API
2024-09-06 22:00:47,666 - root - INFO -    0.0 seconds: D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\DLNodes\sd-dynamic-thresholding
2024-09-06 22:00:47,666 - root - INFO -    0.0 seconds: D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\ComfyUI-Custom-Scripts
2024-09-06 22:00:47,666 - root - INFO -    0.0 seconds: D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\DLNodes\ComfyUI-GGUF
2024-09-06 22:00:47,666 - root - INFO -    0.0 seconds: D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\DLNodes\ComfyUI_bitsandbytes_NF4
2024-09-06 22:00:47,666 - root - INFO -    0.1 seconds: D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\DLNodes\ComfyUI_TensorRT
2024-09-06 22:00:47,666 - root - INFO -    0.1 seconds: D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\ExtraNodes\SwarmComfyCommon
2024-09-06 22:00:47,666 - root - INFO -    0.4 seconds: D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\ComfyUI-Manager
2024-09-06 22:00:47,666 - root - INFO -    0.5 seconds: D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\DLNodes\comfyui_controlnet_aux
2024-09-06 22:00:47,666 - root - INFO -    1.0 seconds: D:\My Stuff\Extra Stuff\SwarmUI\src\BuiltinExtensions\ComfyUIBackend\ExtraNodes\SwarmComfyExtra
2024-09-06 22:00:47,668 - root - INFO -    2.2 seconds: D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\comfy-mecha
2024-09-06 22:00:47,668 - root - INFO -
2024-09-06 22:00:47,678 - root - INFO - Starting server

2024-09-06 22:00:47,678 - root - INFO - To see the GUI go to: http://<IP_ADDRESS>:7821
2024-09-06 22:46:16,100 - root - INFO - got prompt
2024-09-06 22:46:16,268 - root - ERROR - !!! Exception during processing !!! RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'
2024-09-06 22:46:16,281 - root - ERROR - Traceback (most recent call last):
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\comfy-mecha\nodes\merge_nodes.py", line 198, in execute
    merger.merge_and_save(
TypeError: RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'

2024-09-06 22:46:16,282 - root - INFO - Prompt executed in 0.13 seconds
2024-09-06 22:46:27,046 - root - INFO - got prompt
2024-09-06 22:46:27,163 - root - ERROR - !!! Exception during processing !!! RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'
2024-09-06 22:46:27,163 - root - ERROR - Traceback (most recent call last):
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\comfy-mecha\nodes\merge_nodes.py", line 198, in execute
    merger.merge_and_save(
TypeError: RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'

2024-09-06 22:46:27,164 - root - INFO - Prompt executed in 0.06 seconds
2024-09-06 22:47:27,612 - root - INFO - got prompt
2024-09-06 22:47:27,731 - root - ERROR - !!! Exception during processing !!! RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'
2024-09-06 22:47:27,733 - root - ERROR - Traceback (most recent call last):
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\comfy-mecha\nodes\merge_nodes.py", line 198, in execute
    merger.merge_and_save(
TypeError: RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'

2024-09-06 22:47:27,734 - root - INFO - Prompt executed in 0.06 seconds
2024-09-06 22:47:33,798 - root - INFO - got prompt
2024-09-06 22:47:33,915 - root - ERROR - !!! Exception during processing !!! RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'
2024-09-06 22:47:33,916 - root - ERROR - Traceback (most recent call last):
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\comfy-mecha\nodes\merge_nodes.py", line 198, in execute
    merger.merge_and_save(
TypeError: RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'

2024-09-06 22:47:33,917 - root - INFO - Prompt executed in 0.06 seconds
2024-09-06 22:47:47,320 - root - INFO - got prompt
2024-09-06 22:47:47,435 - root - ERROR - !!! Exception during processing !!! RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'
2024-09-06 22:47:47,436 - root - ERROR - Traceback (most recent call last):
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\comfy-mecha\nodes\merge_nodes.py", line 198, in execute
    merger.merge_and_save(
TypeError: RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'

2024-09-06 22:47:47,437 - root - INFO - Prompt executed in 0.06 seconds
2024-09-06 22:48:07,185 - root - INFO - got prompt
2024-09-06 22:48:07,298 - root - ERROR - !!! Exception during processing !!! MechaMerger.execute() missing 1 required positional argument: 'strict_weight_space'
2024-09-06 22:48:07,299 - root - ERROR - Traceback (most recent call last):
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: MechaMerger.execute() missing 1 required positional argument: 'strict_weight_space'

2024-09-06 22:48:07,300 - root - INFO - Prompt executed in 0.06 seconds
2024-09-06 22:50:04,128 - root - INFO - got prompt
2024-09-06 22:50:04,247 - root - ERROR - !!! Exception during processing !!! RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'
2024-09-06 22:50:04,248 - root - ERROR - Traceback (most recent call last):
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\My Stuff\Extra Stuff\SwarmUI\dlbackend\comfy\ComfyUI\custom_nodes\comfy-mecha\nodes\merge_nodes.py", line 198, in execute
    merger.merge_and_save(
TypeError: RecipeMerger.merge_and_save() got an unexpected keyword argument 'strict_weight_space'

2024-09-06 22:50:04,249 - root - INFO - Prompt executed in 0.07 seconds

Attached Workflow
Please make sure that workflow does not contain any sensitive information such as API keys or passwords.
{"last_node_id":24,"last_link_id":31,"nodes":[{"id":6,"type":"Float Mecha Hyper","pos":{"0":780,"1":80},"size":{"0":315,"1":58},"flags":{},"order":0,"mode":0,"inputs":[],"outputs":[{"name":"hyper","type":"MECHA_HYPER","links":[2],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Float Mecha Hyper"},"widgets_values":[0.1],"color":"#222","bgcolor":"#000"},{"id":8,"type":"Float Mecha Hyper","pos":{"0":780,"1":218},"size":{"0":315,"1":58},"flags":{},"order":1,"mode":0,"inputs":[],"outputs":[{"name":"hyper","type":"MECHA_HYPER","links":[4],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Float Mecha Hyper"},"widgets_values":[240830],"color":"#222","bgcolor":"#000"},{"id":13,"type":"Add Difference Mecha Recipe","pos":{"0":1537.5999755859375,"1":242},"size":{"0":367.79998779296875,"1":122},"flags":{},"order":11,"mode":0,"inputs":[{"name":"a (weight|delta space)","type":"MECHA_RECIPE","link":20},{"name":"b (delta space)","type":"MECHA_RECIPE","link":11},{"name":"alpha (1.0)","type":"MECHA_HYPER","link":null}],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[24],"shape":3}],"properties":{"Node name for S&R":"Add Difference Mecha Recipe"},"widgets_values":["default","default"],"color":"#232","bgcolor":"#353"},{"id":2,"type":"Model Mecha Recipe","pos":{"0":50,"1":80},"size":{"0":315,"1":82},"flags":{},"order":2,"mode":0,"inputs":[],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[18],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Model Mecha Recipe"},"widgets_values":["4thTailAnimeHentai_v045.safetensors","sdxl"],"color":"#223","bgcolor":"#335"},{"id":3,"type":"Ties Sum With Dropout Mecha Recipe","pos":{"0":1145,"1":80},"size":{"0":342.5999755859375,"1":302},"flags":{},"order":10,"mode":0,"inputs":[{"name":"deltas (delta space)","type":"MECHA_RECIPE_LIST","link":22},{"name":"apply_median (0.0)","type":"MECHA_HYPER","link":10},{"name":"apply_stock (0.0)","type":"MECHA_HYPER","link":null},{"name":"cos_eps (1e-06)","type":"MECHA_HYPER","link":null},{"name":"eps (1e-06)","type":"MECHA_HYPER","link":null},{"name":"ftol (1e-20)","type":"MECHA_HYPER","link":null},{"name":"k (0.2)","type":"MECHA_HYPER","link":2},{"name":"maxiter (100)","type":"MECHA_HYPER","link":null},{"name":"no_rescale (0.0)","type":"MECHA_HYPER","link":9},{"name":"probability (0.9)","type":"MECHA_HYPER","link":null},{"name":"seed (-1)","type":"MECHA_HYPER","link":4},{"name":"vote_sgn (0.0)","type":"MECHA_HYPER","link":3}],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[11],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Ties Sum With Dropout Mecha Recipe"},"widgets_values":["default","default"],"color":"#432","bgcolor":"#653"},{"id":16,"type":"Subtract Mecha Recipe","pos":{"0":415,"1":80},"size":{"0":315,"1":102},"flags":{},"order":7,"mode":0,"inputs":[{"name":"a (weight space)","type":"MECHA_RECIPE","link":18},{"name":"b (weight space)","type":"MECHA_RECIPE","link":19}],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[21],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Subtract Mecha Recipe"},"widgets_values":["default","default"],"color":"#322","bgcolor":"#533"},{"id":1,"type":"Model Mecha Recipe","pos":{"0":1590.39990234375,"1":80},"size":{"0":315,"1":82},"flags":{},"order":3,"mode":0,"inputs":[],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[23],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Model Mecha Recipe"},"widgets_values":["nai3likediffusion_v10.safetensors","sdxl"],"color":"#223","bgcolor":"#335"},{"id":7,"type":"Float Mecha Hyper","pos":{"0":780,"1":357},"size":{"0":315,"1":58},"flags":{},"order":4,"mode":0,"inputs":[],"outputs":[{"name":"hyper","type":"MECHA_HYPER","links":[3,9,10,25],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Float Mecha Hyper"},"widgets_values":[1],"color":"#222","bgcolor":"#000"},{"id":15,"type":"Model Mecha Recipe","pos":{"0":50,"1":242},"size":{"0":315,"1":82},"flags":{},"order":5,"mode":0,"inputs":[],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[19,20,26],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Model Mecha Recipe"},"widgets_values":["sd_xl_base_1.0.safetensors","sdxl"],"color":"#223","bgcolor":"#335"},{"id":20,"type":"Model Mecha Recipe","pos":{"0":50,"1":405},"size":{"0":315,"1":82},"flags":{},"order":6,"mode":0,"inputs":[],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[27],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Model Mecha Recipe"},"widgets_values":["realvisxlV40_v40LightningBakedvae.safetensors","sd1"],"color":"#223","bgcolor":"#335"},{"id":18,"type":"Mecha Recipe List","pos":{"0":780,"1":497},"size":{"0":315,"1":78},"flags":{},"order":9,"mode":0,"inputs":[{"name":"recipe_0","type":"MECHA_RECIPE","link":21},{"name":"recipe_1","type":"MECHA_RECIPE","link":28}],"outputs":[{"name":"recipes","type":"MECHA_RECIPE_LIST","links":[22],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Mecha Recipe List"},"widgets_values":[2],"color":"#432","bgcolor":"#653"},{"id":21,"type":"Subtract Mecha Recipe","pos":{"0":415,"1":262},"size":{"0":315,"1":102},"flags":{},"order":8,"mode":0,"inputs":[{"name":"a (weight space)","type":"MECHA_RECIPE","link":27},{"name":"b (weight space)","type":"MECHA_RECIPE","link":26}],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[28],"slot_index":0,"shape":3}],"properties":{"Node name for S&R":"Subtract Mecha Recipe"},"widgets_values":["default","default"],"color":"#322","bgcolor":"#533"},{"id":19,"type":"Weighted Sum Mecha Recipe","pos":{"0":1955.39990234375,"1":80},"size":{"0":367.79998779296875,"1":122},"flags":{},"order":12,"mode":0,"inputs":[{"name":"a (weight|delta space)","type":"MECHA_RECIPE","link":23},{"name":"b (weight|delta space)","type":"MECHA_RECIPE","link":24},{"name":"alpha (0.5)","type":"MECHA_HYPER","link":25}],"outputs":[{"name":"recipe","type":"MECHA_RECIPE","links":[29],"shape":3,"slot_index":0}],"properties":{"Node name for S&R":"Weighted Sum Mecha Recipe"},"widgets_values":["default","default"],"color":"#232","bgcolor":"#353"},{"id":24,"type":"ShowText|pysssss","pos":{"0":2743.199951171875,"1":80},"size":[315,58],"flags":{},"order":14,"mode":0,"inputs":[{"name":"text","type":"STRING","link":31,"widget":{"name":"text"}}],"outputs":[{"name":"STRING","type":"STRING","links":null,"shape":6}],"properties":{"Node name for S&R":"ShowText|pysssss"},"widgets_values":[""]},{"id":22,"type":"Mecha Merger","pos":{"0":2373.199951171875,"1":80},"size":[320,290],"flags":{},"order":13,"mode":0,"inputs":[{"name":"recipe","type":"MECHA_RECIPE","link":29}],"outputs":[{"name":"MODEL","type":"MODEL","links":null,"shape":3},{"name":"CLIP","type":"CLIP","links":null,"shape":3},{"name":"recipe_txt","type":"STRING","links":[31],"shape":3,"slot_index":2}],"properties":{"Node name for S&R":"Mecha Merger"},"widgets_values":["none","cuda","fp64","cpu","fp16","0.5G",0,true,true]}],"links":[[2,6,0,3,6,"MECHA_HYPER"],[3,7,0,3,11,"MECHA_HYPER"],[4,8,0,3,10,"MECHA_HYPER"],[9,7,0,3,8,"MECHA_HYPER"],[10,7,0,3,1,"MECHA_HYPER"],[11,3,0,13,1,"MECHA_RECIPE"],[18,2,0,16,0,"MECHA_RECIPE"],[19,15,0,16,1,"MECHA_RECIPE"],[20,15,0,13,0,"MECHA_RECIPE"],[21,16,0,18,0,"MECHA_RECIPE"],[22,18,0,3,0,"MECHA_RECIPE_LIST"],[23,1,0,19,0,"MECHA_RECIPE"],[24,13,0,19,1,"MECHA_RECIPE"],[25,7,0,19,2,"MECHA_HYPER"],[26,15,0,21,1,"MECHA_RECIPE"],[27,20,0,21,0,"MECHA_RECIPE"],[28,21,0,18,1,"MECHA_RECIPE"],[29,19,0,22,0,"MECHA_RECIPE"],[31,22,2,24,0,"STRING"]],"groups":[],"config":{},"extra":{"ds":{"scale":1.1,"offset":[-1380.1052760274542,21.959220043091136]}},"version":0.4}

Additional Context
I was experimenting with a recipe similar to https://github.com/6DammK9/nai-anime-pure-negative-prompt/blob/main/ch05/recipes/x191a-AstolfoMix-24083001-3360d18.mecha with less models to see how it works.

Note: realvisxlV40_v40LightningBakedvae.safetensors was mistakenly set to sd1 in the given workflow but the error still persists once corrected to sdxl.

I really appreciate these detailed reports! I had changed the version of the backing lib to 0.0.26 only in pyproject.toml, not in requirements.txt.
I hate that the requirements are in 2 places... Let me know if you have a suggestion with respect to this. Online people seem to explain that it's a good practice but I'm not really convinced.
In any case, it should be fixed as of the latest version of the node pack.


Add failOnError to suit

Rebuilt diff on top of suit from https://github.com/lovell/sharp/pull/925
Addresses https://github.com/lovell/sharp/issues/793
I found that setting option->set("fail", FALSE) still set the flag (!!), so that flag is set conditionally in this branch.
Added tests for [JPG, PNG] x [without flag, with flag and callback, with flag and promise] combinations.
I gave up on "punched file" support, as the error messages depend on where the "holes" are, and libvips and libjpeg don't always agree on the validity of a JPEG stream.

Coverage increased (+0.008%) to 99.023% when pulling f7019e4acbaee2073e789a010427598d10931d49 on mceachen:suit-failonerror into c38741587f4607a5819284333afb5591b00a9dea on lovell:suit.

Coverage increased (+0.008%) to 99.023% when pulling 47a0356c3e02bc8b66697e36a5097b7c0a4f03c2 on mceachen:suit-failonerror into c38741587f4607a5819284333afb5591b00a9dea on lovell:suit.

The linux builds are passing now. Mac builds fail in the same fashion as your other suit branch builds, like https://travis-ci.org/lovell/sharp/builds/282365910, so I think this PR is ready to merge.

I added a temporary commit 50563c4 so this PR will pass CI after the next rebase+push.

Coverage increased (+0.006%) to 99.021% when pulling eb1254fab9b139b2001bb368582680af05dfe76e on mceachen:suit-failonerror into 50563c48a52b1b16f0a64478bf01104d898a7efc on lovell:suit.

Coverage increased (+0.006%) to 99.021% when pulling 34ed224481ab58dbb36a327ead87679e30ef872c on mceachen:suit-failonerror into 50563c48a52b1b16f0a64478bf01104d898a7efc on lovell:suit.

Coverage increased (+0.006%) to 99.021% when pulling 34ed224481ab58dbb36a327ead87679e30ef872c on mceachen:suit-failonerror into 50563c48a52b1b16f0a64478bf01104d898a7efc on lovell:suit.

Coverage increased (+0.006%) to 99.021% when pulling 34ed224481ab58dbb36a327ead87679e30ef872c on mceachen:suit-failonerror into 50563c48a52b1b16f0a64478bf01104d898a7efc on lovell:suit.

Marvellous, thank you for all your work on this Matthew.

Thanks for sharp!


syz-repro : testImpl should return false if rep.Title does not match context ctx.crashTitle

Example :
2020/12/07 18:07:57 reproducing crash 'no output/lost connection': program crashed: WARNING: kernel stack regs has bad 'bp' value
2020/12/07 18:07:57 reproducing crash 'no output/lost connection': single: successfully extracted reproducer
2020/12/07 18:07:57 reproducing crash 'no output/lost connection': found reproducer with 9 syscalls

Should not use non contextual crashes to create reproducers.

Lots of kernel crashes have different manifestations, see:
https://groups.google.com/g/syzkaller/c/sR8aAXaWEF4/m/tTWYRgvmAwAJ
So we simply checking for equality will fix some subset of cases, but break another subset.

Does checking rep.Type == ctx.crashType improve the filtration instead of previous assertion of comparing titles?

Type is very generic. Besides HANG, I think all crashes are classified as just "crash".

New idea -
if ctx.crashTitle != rep.Title {
   // look for existing reproducers of rep.Title
   // if rep.Title exists and has previous crash reports / repros -> skip
   ctx.reproLogf(2, "program crash already documented")
   return false, nil
   // else
   return true, nil
}
return true, nil

Basically check if there is a previously documented manifestation of the mismatched crash title. If there is a report for that, then skip this hit. What are your thoughts @dvyukov

Will this do more good than harm on syzbot overall?

If we know one system call has a bug, then potentially any bugs resulting in a fall out from exploiting the system call could be considered noisy. This one feels like a double-edged sword. I can see some upsides, but there are definitely some downsides while generating reproducers for said noisy bugs.

Well, based on this I can only say that it may or may not be good :)

While I do not fully understand the scope of this; but one of the current outstanding impacts that I'm seeing :
2020/12/09 16:57:58 loop: repro on [0 1 3 2] finished 'BUG: soft lockup in tty_ioctl', repro=true crepro=true desc='WARNING: kernel stack regs has bad 'bp' value'
2020/12/09 16:57:58 loop: phase=4 shutdown=false instances=4/4 [0 1 3 2] repro: pending=0 reproducing=0 queued=0

The bug that syz-repro was trying to reproduce was not the one that it ended up doing and ended successfully because one of the bugs that it did reproduce already has a reproducer in workdir.

This should not hurt syzbot -
if ctx.crashTitle != rep.Title {
   if (rep.IsSuppressed) {
       return false, nil
   }
return true, nil

Thoughts about this delta @dvyukov ?

This is a known problem, also very negatively affects bisection.
But I don't see any simple solution. I suspect that if the tested system has lots of bugs, triggered by different inputs or triggered by all inputs episodically, and is non-deterministic doing the always right thing automatically is simply impossible. Improvements to the heuristics are welcome, but I don't think it's that simple as comparing titles. Also any improvement should be designed around a single particular case, it should consider the wider picture.
Another concrete aspect: if we hit a different bug (let's say we are somehow sure it is in fact different), does it mean that the program does not trigger the original bugs we are chasing? I think it does not necessary mean that.

I have an idea that might potentially increase syz-repro runtime but will likely reproduce more bugs.
If after the finished loop in syz-repro, we compare the bugs and if the intended bug is not the same as the discovered bug, we retry the syz-repro without loading the instruction that triggered the discovered bug (thereby minimizing the instruction count, but keeping all other parameters the same). We could restrict this retry limit through config parameters.

This makes sense.
But I think it's better be done before the repro process. This would save lots of time and allow to search larger set of potential candidates. Say, we identified 4 potential candidate programs (based on proc count), then we run each of them (maybe several times, if necessary) and see which one reproduces the target crash title precisely. If we found such crash, then we run the current minimization process on it. Otherwise... well, choose any.
Would this achieve your goal?
Though, it won't solve this case:
2020/12/09 16:57:58 loop: repro on [0 1 3 2] finished 'BUG: soft lockup in tty_ioctl', repro=true crepro=true desc='WARNING: kernel stack regs has bad 'bp' value'

Or, you mean doing reproduction on the same program, but skipping the simple minimization step that diverged it to a different crash?

I'll try to iron out the flow that I was picturing :
syz-manager event - crash, reason = 'BUG: something in function_1' , vms - x, programs - y, repro = 1
syz-repro startup : reproducing crash 'BUG: something in function_1'
Scenario 1
syz-repro event - crash, reason = 'BUG: unrelated in function_2' -> successfully extracted reproducer ->found reproducer with  syscalls
syz-repro event - finished reproducing. Checking bug discovered == bug reproducing for (retry limit = config.reproretrylimit)
syz-repro event - removing guilty program and rerunning syz-repro all over again
.. goes on until target bug is discovered or config.reproretrylimit is hit.
Scenario 2
syz-repro event - crash, reason = 'BUG: something in function_1' -> successfully extracted reproducer ->found reproducer with  syscalls
syz-repro event - finished reproducing. Checking bug discovered == bug reproducing for (retry limit = config.reproretrylimit)
syz-repro event - exit
I see your point in shortening the number of programs that we feed to syzkaller in the first place; however, I'd debate that it should be a part of syz-repro and not syz-manager since they can be run independently and syz-repro should be able to do that from the logfile. What are your thoughts @dvyukov ; I'm slowly getting the hang of the codebase :)

I'd debate that it should be a part of syz-repro and not syz-manager since they can be run independently and syz-repro should be able to do that from the logfile

This logic should be part of pkg/repro, syz-repro and syz-manager should contain no repro-related logic, these are just wrappers.
It may be better to guide the process along the way before we wasted hours pursuing already-known-to-be-wrong reproducer just to throw it away and retry. syzbot restarts managers every 12h or faster, and repro processes can take hours, if we make then several times slower, these repro processes will never finish (and of course for manual syz-manager runs day-long duration is a problem too).

Thanks for helping me understand the shared code between the two. I also see the benefit in reducing the runtime for all binaries. I think we should close this issue out and create a new tracker for trimming down the repro prog list.


index.html: Prefer HTTPS for assets

All assets are hosted on servers configured for HTTPS, so this is absolutely preferable in this day and age. In addition to privacy, there is an argument that there's no point in requesting resources over the Internet if you can't verify where they come from. Functionality is not changed at all.

Updated pull request to remove HTTPS from author's homepage (http://cjpatoilo.com).

Hi @alanorth Thanks for PR.


Feature/string match question type

This does generate slightly different JSON to the JSON in the example question because my implementation of "StringChoice" matches the explanation structure of a standard "Choice".
Example Question Schema:
      "explanation": {
        "type": "content",
        "value": "hello is lowercase!",
        "encoding": "markdown"
      }

Implemented Schema:
      "explanation": {
        "type": "content",
        "children": [
          {
            "type": "content",
            "value": "hello is lowercase!",
            "encoding": "markdown"
          }
        ],
        "encoding": "markdown"
      }

This doesn't make a difference to what is eventually rendered but it matches what other Choice types use.

Regarding explanations, I have often wondered why it's the complicated nested structure when it doesn't need to be; but I think it's because it's easier to add a new item without rewriting the whole JSON tag that way. Either way, sounds fine by me!


merge from arlac77/template-github,arlac77/template-kronos-module

package.json

chore(package): add >=14.0.0 remove >=13.13.0 (engines.node)

.travis.yml

chore(travis): (jobs.include)
chore(travis): remove 13.13.0 (jobs.include.node_js)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


shouldBe does not handle java long or Long but does handle Integer

Getting a unexpected assertion failure while converting assertj assertions to kotlin-test shouldBe style assertions.
Given this simple Java class:
public class Foo {
    public static final long MEANING_OF_LIFE = 42l;
}

This test fails with the above on the shouldBe line:
import io.kotlintest.shouldBe
import org.assertj.core.api.Assertions
import org.junit.jupiter.api.Test

class FooTest {
    @Test
    fun fooTest() {
        val v1: Int = Foo.MEANING_OF_LIFE.toInt()
        val v2 = java.lang.Integer.valueOf(42)
        val v3 = Foo.MEANING_OF_LIFE
        val v4 = java.lang.Long.valueOf(42)
        val v5 = Foo.MEANING_OF_LIFE.toLong()

        // assertj works for all cases
        Assertions.assertThat(v1).isEqualTo(42)
        Assertions.assertThat(v2).isEqualTo(42)
        Assertions.assertThat(v3).isEqualTo(42)
        Assertions.assertThat(v4).isEqualTo(42)
        Assertions.assertThat(v5).isEqualTo(42)

        // works
        v1 shouldBe 42
        // works
        v2 shouldBe 42
        // fails
        v3 shouldBe 42
        // fails
        v4 shouldBe 42
        // fails
        v5 shouldBe 42
    }
}

with:
java.lang.AssertionError: expected: 42 but was: 42
Expected :42
Actual   :42

So, it seems the only way I can make this work is calling toInt(). This seems to result from differences in the way kotlin numeric types differ from Java as explained here: https://kotlinlang.org/docs/reference/basic-types.html. But it makes testing Java code with Kotlin a bit more challenging. So, it might be worth investigating some kind of workaround and make shouldBe a bit more foregiving by maybe handling java primitive and boxed type explicitly.

Similar issues with doubles, I have to call toDouble() on them to make things work; toFloat() does not work.

I've added a quick fix and some tests. Basically I promote ints to longs, and floats to doubles where appropriate.
 Java has type conversions that kotlin does not have. Still, might be valid for shouldBe to be more foregiving. But otherwise the solution is to use the correct literals.

Yes, but the Java use case is a valid one.

Fix is applied in latest release 3.1.5


std.algorithm.copy uses too restricted array specialization

drug2004 (@drug007) reported this on 2016-07-28T19:17:17Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=16332
CC List

nick (@ntrel)

Description
In case of array `std.algorithm.copy` uses an array specialization that assumes that that arrays can be bitblt-ed and this assumption is false if array contains elements that can not be bitblt-ed but can be copied by elements.
For examples, a structure with indirections with copy ctor or custom `opAssign` can not be bitblt-ed:
```
struct Foo
{
    int[] i;
}

const(Foo)[] cfoo;
Foo[] foo;

cfoo.copy(foo); // doesn't compile because
                // 'copy' uses the array specialization:
                // foo[] = cfoo[];
```
but
```
struct Foo
{
    int[] i;

    ref Foo opAssign(const(Foo) other)
    {
        ...
    }
}

cfoo.copy(foo); // doesn't compile again because
                // `copy` again uses the same array specialization
                // foo[] = cfoo[]; <- this fails again
                // but should use:
                // foreach(idx; cfoo.length)
                //     foo[idx] = cfoo[idx];
```
That is for array `copy` should detect if it can be bitblt-ed or should be copied by element.

nick (@ntrel) commented on 2023-02-28T18:56:52Z
Complete example:

import std.algorithm : copy;

struct Foo
{
	int[] i;

	void opAssign(const(Foo) other)
	{
		i = other.i.dup;
	}
}

void main()
{
	const(Foo)[] cfoo;
	foreach (i; 1 .. 4)
		cfoo ~= Foo([i]);
	Foo[] foo = new Foo[](3);
	//cfoo.copy(foo); // NG, should be equivalent to:
	foreach(idx; 0 .. cfoo.length)
		foo[idx] = cfoo[idx];
	assert(foo == cfoo);
}


Setup project

For learning purposes i tried cloning project but i can't build it.
After doing "make bootstrap" some dependencies still missing

Hi @awessoEsso, thanks for reporting this issue you're seeing. Can you describe what build error you're getting, or what dependencies are still missing after running make bootstrap?

Thanks @ifbarrera
This are dependencies missing

I added $(PROJECT_DIR) in Framework Search Paths and it works.
Thanks you all for your help

I am also not able to build the project getting missing module (Prelude, Argo)


ModelAngelo v1.0.1 stopped after predicting Cα

Hi jamaliki,
I would like to express my gratitude for your contributions to model building. However, I encountered an issue while using ModelAngelo to generate a protein model. After the Cα prediction step, ModelAngelo displayed an error message in the log file and halted the GNN execution. I have included the error message below. I am confident that the format of the fasta file containing three peptide sequences is correct, and there are no unknown residues in the file. I'm currently unable to determine the cause of the program's termination. Could you kindly provide any guidance on resolving this problem?
Thank you in advance.
2023-06-30 at 17:31:00 | ERROR | Error in ModelAngelo
Traceback (most recent call last):
File "/opt/anaconda3/envs/model_angelo/bin/model_angelo", line 33, in
sys.exit(load_entry_point('model-angelo==1.0.1', 'console_scripts', 'model_angelo')())
│   │    └ <function importlib_load_entry_point at 0x7fd1ce563d90>
│   └
└ <module 'sys' (built-in)>
File "/opt/anaconda3/envs/model_angelo/lib/python3.10/site-packages/model_angelo-1.0.1-py3.10.egg/model_angelo/main.py", line 52, in main
args.func(args)
│    │    └ Namespace(volume_path='/Users/XMi/Desktop/52/1/corner1.mrc', protein_fasta='/Users/XMi/Desktop/52/1/seq.fasta', rna_fasta=Non...
│    └ <function main at 0x7fd1dafe8700>
└ Namespace(volume_path='/Users/XMi/Desktop/52/1/corner1.mrc', protein_fasta='/Users/XMi/Desktop/52/1/seq.fasta', rna_fasta=Non...

File "/opt/anaconda3/envs/model_angelo/lib/python3.10/site-packages/model_angelo-1.0.1-py3.10.egg/model_angelo/apps/build.py", line 241, in main
gnn_output = gnn_infer(gnn_infer_args)
│         └ {'num_rounds': 3, 'crop_length': 200, 'repeat_per_residue': 1, 'esm_model': 'esm1b_t33_650M_UR50S', 'aggressive_pruning': Tru...
└ <function infer at 0x7fd1daf1b400>
File "/opt/anaconda3/envs/model_angelo/lib/python3.10/site-packages/model_angelo-1.0.1-py3.10.egg/model_angelo/gnn/inference.py", line 92, in infer
protein = get_lm_embeddings_for_protein(lang_model, batch_converter, protein)
│                             │           │                └ Protein(atom_positions=None, atomc_positions=None, aatype=None, atom_mask=None, atomc_mask=None, residue_index=None, chain_in...
│                             │           └ <esm.data.BatchConverter object at 0x7fcf8e0e7fd0>
│                             └ ProteinBertModel(
│                                 (embed_tokens): Embedding(33, 1280, padding_idx=1)
│                                 (layers): ModuleList(
│                                   (0-32): 33 x TransformerLa...
└ <function get_lm_embeddings_for_protein at 0x7fd1daf1b520>
File "/opt/anaconda3/envs/model_angelo/lib/python3.10/site-packages/model_angelo-1.0.1-py3.10.egg/model_angelo/data/generate_complete_prot_files.py", line 34, in get_lm_embeddings_for_protein
protein_with_lm = add_lm_embeddings_to_protein(protein, lm_embeddings)
│                            │        └ array([[ 0.0707111 ,  0.16950509, -0.00793343, ..., -0.3184964 ,
│                            │                  -0.15484953, -0.44611225],
│                            │                 [ 0.24136926, -0.0...
│                            └ Protein(atom_positions=None, atomc_positions=None, aatype=None, atom_mask=None, atomc_mask=None, residue_index=None, chain_in...
└ <function add_lm_embeddings_to_protein at 0x7fd1daf19cf0>
File "/opt/anaconda3/envs/model_angelo/lib/python3.10/site-packages/model_angelo-1.0.1-py3.10.egg/model_angelo/utils/protein.py", line 897, in add_lm_embeddings_to_protein
assert len(lm_embeddings) == input_protein.unified_seq_len
│                 │             └ 233
│                 └ Protein(atom_positions=None, atomc_positions=None, aatype=None, atom_mask=None, atomc_mask=None, residue_index=None, chain_in...
└ array([[ 0.0707111 ,  0.16950509, -0.00793343, ..., -0.3184964 ,
-0.15484953, -0.44611225],
[ 0.24136926, -0.0...

AssertionError: assert len(lm_embeddings) == input_protein.unified_seq_len

Hi,
Sorry for my late reply. This seems to be an issue in the input sequence. Have you made sure there are no non standard amino acids in your input? Could you share the sequence file?
Best,
Kiarash.

Hi jamaliki,
Thank you for your help. I recreated a FASTA file and finally ModelAngelo proceeded.


Simple sparse checkout patterns

While correct the current "more complicated construction" of glob patterns for sparse checkouts became unnecessary as of the filtering added recently via ScanResult.filterPath() for any VCS path. Remove that complexity to simplify working with the code.
Note that the sparse checkout feature is planned to be removed so there is no reason why these "more correct but more complex" patterns need to be kept.

Merge despite the failing appeyor test (unrelated), the azure windows test succeeded btw.


[Bug]: Sync function is loaded on page load when accessing function as myFunc.data

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Using JSObject1.myFunc1.data in a widget binding automatically shows the message [JSObject1.myFunc1] will be executed automatically on page load even when the function myFunc1 is not an async function so this function will not have any settings on the JS objects and is executed on page load, i.e. a sync function runs on page load which is not allowed on the platform right now
Steps To Reproduce

Use following code on the editor - observe that this function is not asycn hence does not appear on the settings tab of the object

myFunc1: () => {
		console.log('Heloo')
	}

Use {{JSObject1.myFunc1.data}} on widget binding and observe the message appear stating the function will be executed on page load
Refresh the page and observe browser console print Hello since this function was executed on page load

Public Sample App
No response
Version
Cloud

Hey @ramsaptami ~ This seems to be by design. Why do we want to remove this functionality? I can in fact see a test case written on the server for this exact same scenario to work as it is working. :D

Ohhhkkkkk, that's very confusing now. Cause @ApekshaBhosale and I spoke about this and she mentioned sync functions should not be set to run on page load 🙊 @ApekshaBhosale what do we do here?


cx_oracle 8.0 not compatible with Python 2.x anymore

The cxoracle role does not install per default anymore, as cx_oracle==7.3 is the last version compatible with python 2.x.
cx_oracle 8.+ require Python 3.x . Currently this is not reflected in the role.

@matthiaslink77 Could you close this issue?

Good morning Thorsten, thanks a lot.
Yes - to just add the version to the package name was the fix I already provided in the text.
This issue was actually opened to fix it "properly", hence version 8.+ should be usable.
So I would rather like to keep this issue open.
Danke und beste Grüße, Matthias.

We should close this issue.
Reasons:

Python3 + Ansible has issues on OL7
Some Ansible modules - not the library inside ansible-oracle - have problems during execution of ansible-playbooks. Solution: Use Ansible with Python2 on OL7. This requires the old version of cx_Oracle.
Python3 + Ansible is working on OL8

I see no way to fix the issue with newer version of cx_Oracle on OL7 with Python3.


support jdk1.7

the latest version depend jdk1.8 too high.

Oracle's public updates for Java 7 have ended in April 2015. I would therefore advise against running these.
If you really want, you could try to compile Membrane's source code using a Java 7 compiler. Most of it should work and you might not need the other parts. Note though, that this is not officially supported.

We still maintain 4.0.X that runs with jdk 1.6. The difference to 4.2.X are some very few features like OAuth 2.

In versions 4.2.x inside the README.txt we have the following:
"Make sure you have installed Java 1.6 or higher." but it should say "Java 1.8" right? Anyway I would suggest that Membrane SP would come pre-packaged with the right jdk version, and if Oracle's jdk license doesn't allow that, you could maybe think about OpenJDK.
windows openjdk1.8 - https://github.com/ojdkbuild/ojdkbuild
Linux openjdk1.8 - http://www.linuxfromscratch.org/blfs/view/svn/general/openjdk.html

Create the folder MEMBRANE_HOME/jdk and extract the right jdk version on it

Should then change the following scripts:
-- Linux service-proxy.sh --

#!/bin/bash

## resolve links - $0 may be a link to Membrane's home
PRG="$0"

# need this for relative symlinks
while [ -h "$PRG" ] ; do
  ls=`ls -ld "$PRG"`
  link=`expr "$ls" : '.*-> \(.*\)$'`
  if expr "$link" : '/.*' > /dev/null; then
    PRG="$link"
  else
    PRG="`dirname "$PRG"`/$link"
  fi
done

saveddir=`pwd`

MEMBRANE_HOME=`pwd`

# make it fully qualified
export MEMBRANE_HOME=`cd "$MEMBRANE_HOME" && pwd`

# REN defined vars - remember to do the same for *.bat file
export JAVA_HOME="$MEMBRANE_HOME/jdk"

cd "$saveddir"
# echo Using Membrane at $MEMBRANE_HOME

CLASSPATH="$MEMBRANE_HOME/conf"
CLASSPATH="$CLASSPATH:$MEMBRANE_HOME/starter.jar"

# REN defined vars - remember to do the same for *.bat file
CLASSPATH="$CLASSPATH:$JAVA_HOME/bin"
export CLASSPATH
cd "$MEMBRANE_HOME"

major=$($JAVA_HOME/bin/java -version 2>&1 | head -n 1 | cut -d'"' -f2 | cut -d'.' -f2)

if [ "$major" -lt "8" ]
then
    echo "You are running Java $major. Membrane needs atleast Java 8. Please install a newer Java version from http://www.oracle.com/technetwork/java/javase/downloads/index.html"
fi

echo Membrane Router running...
$JAVA_HOME/bin/java  -classpath "$CLASSPATH" com.predic8.membrane.core.Starter "$@"

-- Windows service-proxy.bat --
@echo off
if not "%MEMBRANE_HOME%" == "" goto homeSet
set "MEMBRANE_HOME=%cd%"
if exist "%MEMBRANE_HOME%\service-proxy.bat" goto homeOk

:homeSet
if exist "%MEMBRANE_HOME%\service-proxy.bat" goto homeOk
echo Please set the MEMBRANE_HOME environment variable to point to
echo the directory where you have extracted the Membrane software.
goto end

:homeOk
set "CLASSPATH=%MEMBRANE_HOME%"
set "CLASSPATH=%MEMBRANE_HOME%/conf"
set "CLASSPATH=%CLASSPATH%;%MEMBRANE_HOME%/starter.jar"

REM REN defined vars - remember to do the same for *.sh file
set JAVA_HOME=%MEMBRANE_HOME%/jdk
set PATH=%JAVA_HOME%/bin;%PATH%

for /f "tokens=3" %%g in ('java -version 2^>^&1 ^| findstr /i "version"') do (
    set JAVAVER=%%g
)
set JAVAVER=%JAVAVER:"=%

for /f "delims=. tokens=2" %%v in ("%JAVAVER%") do (
    set JAVAVER=%%v
)

if %JAVAVER% LSS 8 echo "You are running Java %JAVAVER%. Membrane needs atleast Java 8. Please install a newer Java version from http://www.oracle.com/technetwork/java/javase/downloads/index.html"

echo Membrane Router running...
java  -classpath "%CLASSPATH%" com.predic8.membrane.core.Starter %1 %2 %3 %4 %5 %6 %7 %8 %9

Regards and keep up the nice work,
MS


Remove check for "Unnamed" name in ProjectInfo.fromPb()

Currently, when using ListProjects, projects without a name are given the name "Unnamed" when returned by ListProjects.  As a result, we explicitly set the name to null if a project's name is "Unnamed" in ProjectInfo.fromPb When this is fixed, we can stop this behavior.

This has been added to our feature backlog: https://github.com/GoogleCloudPlatform/google-cloud-java/wiki/Feature-backlog . This issue will be closed but is linked in the backlog and can continue to be used for comment and discussion.


fix: add ref to catalog entries

This PR adds the ref property so that we can checkout the specific branch/commit.
A valid ref can be a SHA1 tag or a branch name
it resolves #142

I forgot to make the ref optional. Updating


[plex] fix port definition indentation

Special notes for your reviewer:
After upgrading plex from chart 1.0.0 to 1.3.1 plex stopped responding.
In my deployment the port key wasn't set.
After fixing the indentation, the deployment get the ports exposed again.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [radarr])

Thanks for fixing this!  I has the same problem. Do you mind bumping the chart version?

Now i'm not really sure if it completely fixed it...
Did you tried it?? I can't make it work with remote connections...

It was a problem with my confirguration... :)
I just bumped the chart version


zbar: 0.23.1 -> 0.23.90

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mchehab/zbar/releases.
meta.description for zbar is: "Bar code reader"
meta.homepage for zbar is: "https://github.com/mchehab/zbar"
meta.changelog for zbar is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.23.90 with grep in /nix/store/1p6bnaa3g1gpay6v2nddv57622kcsibw-zbar-0.23.90

directory tree listing: https://gist.github.com/3e3f2e4c53f33d2bfc404fcfdf7b6e24

du listing: https://gist.github.com/314f34c1de57dcf6e4b2d58a61499cab

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

11 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
electrum
gnome-keysign
zbar

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1p6bnaa3g1gpay6v2nddv57622kcsibw-zbar-0.23.90
ls -la /nix/store/1p6bnaa3g1gpay6v2nddv57622kcsibw-zbar-0.23.90/bin

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

3 packages built:

electrum
gnome-keysign
zbar

Maintainer pings
cc @delroth @7c6f434c for testing.

Result of nixpkgs-review pr 113638 at 0172521d run on aarch64-linux 1

2 packages built:

gnome-keysign
zbar

1 suggestion:

warning: unclear-gpl
lgpl21 is a deprecated license, check if project uses lgpl21Plus or lgpl21Only and change meta.license accordingly.
Near pkgs/tools/graphics/zbar/default.nix:93:5:
   |
93 |     license = licenses.lgpl21;
   |     ^


Fatal Error on player 2 trying to join a lan game.

In borderlands 2 the game loads fine for both players (using alpha 6), but whenever player 2 loads into the game they instantly crash with the this error
Any help would be appreciated.
Edit: Seems to be an issue with the steam overlay, which is a shame as I need it for the steam controller.
Well time to find a workaround (or just use a xbox controller).

The problem still exists in Alpha v7. In order to fix simply disable Steam Overlay.
Steam > Settings > In-Game > uncheck the box next to "Enable the Steam Overlay while in-game
note - this does disable steam controller support as well


Begin updating transactions

Now that categories is mostly done (#205), it's time to update Transactions.
I might need to add some more stuff to the BE to support this (or just mock it out); in the meantime, I'm opening this PR.

Gonna close this 'cause I need to mock out the API first (https://github.com/jmeas/moolah/issues/243)


💡[Feature]: Quantum Circuit Probability Prediction using ML

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The Quantum Circuit Probability Predictor is a machine learning-based application designed to predict the probability of measuring a specific quantum state after applying a series of quantum gates to a qubit. Leveraging the principles of quantum mechanics and classical machine learning, this project aims to create a robust model that accurately estimates the probabilities associated with different quantum states resulting from varied input parameters.
Use Case
The following are the variety of use cases for the model:
Quantum Key Distribution (QKD): Enhances secure key exchange in cryptographic protocols.
Quantum Classification: Improves accuracy in machine learning classifiers.
Molecular Simulation: Predicts chemical reactions and material properties.
Quantum Approximate Optimization Algorithm (QAOA): Solves combinatorial optimization problems.
Game Theory Models: Analyzes strategies in quantum games.
Quantum Auctions: Optimizes bidding strategies in auction scenarios.
Quantum Error Correction: Enhances fault tolerance in quantum systems.
Biological Sensing: Improves accuracy of medical sensors through quantum measurements.
Genomic Data Analysis: Identifies genetic variations impacting diseases.
Generative Quantum Models: Generates new data samples similar to classical GANs.
Reinforcement Learning: Enhances decision-making processes in AI models.
Benefits
Following are the applications where Quantum Circuit forms the base:
Speed: Quantum circuits can process information in parallel, potentially offering exponential speedup for specific computations over classical algorithms.
Enhanced Accuracy: Quantum probability distributions can capture complex correlations, improving the accuracy of predictions in tasks like classification and simulation.
Resource Efficiency: Quantum algorithms may require fewer resources (like memory and time) for certain computations, optimizing performance.
Handling Complex Systems: Quantum circuits excel in modeling and predicting behaviors in complex systems, such as molecular interactions or financial markets.
Optimization: Quantum circuits can efficiently tackle combinatorial optimization problems, yielding better solutions than classical methods.
Improved Cryptography: Leveraging quantum mechanics enhances security protocols through quantum key distribution and other cryptographic methods.
Robustness Against Noise: Quantum algorithms can be designed to be less sensitive to certain types of noise, improving performance in real-world applications.
Innovative Applications: Enables new applications in various fields, such as drug discovery, climate modeling, and artificial intelligence, that were previously infeasible with classical computing.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

If possible please assign me this project as its quite efficient , interesting to carry out and effective in the field of ML Researc.
please label it under Level2 or 3 project as its quite heavy aspect from research point of view and also under Hacktober tag. I am an GSSoC Extd Contributor

we are not accepting new documentation like this, see the pinned issues,


MMDet-COCO Export Error

Data Format MMDET-COCO is not marked as "(import-only)", but I can't see how it's exporting in the code. I am using version 1.7.0.

When exporting from a yolo project => mmdet:
$ datum --loglevel debug project export --format mmdet_coco -o ./coco -- --save-media
DEBUG: Cannot import extra dep=tensorflow for plugin_name=ac.
DEBUG: Cannot import extra dep=tensorflow for plugin_name=roboflow_tfrecord.
DEBUG: Cannot import extra dep=tensorflow for plugin_name=roboflow_tfrecord.
DEBUG: Cannot import extra dep=tensorflow for plugin_name=tf_detection_api.
DEBUG: Cannot import extra dep=tensorflow for plugin_name=tf_detection_api.
DEBUG: Cannot import extra dep=tensorflow for plugin_name=tf_detection_api.
ERROR: Exporter for format 'mmdet_coco' is not found

I would appreciate any help! I followed the basic installation instructions and the basic project setup.

This one is my ignorance & lack of experience I think!
I believe what I am looking for is exporting with the coco format & using the instances_*.json as described here.
Sorry to post an issue over nothing, I was looking for a bit! If my logic is wrong please yell at me 😄.
Thank you for a really neat project!


Update ci and issue templates

@rtripath89 This updates the CI (and issue templates) for this repo, should allow it to build.


Default args as keywords

This should be aligned with https://github.com/arkency/ruby_event_store/pull/27 but let's not wait for new ruby_event_store release. Will apply further changes in next PR.


About iDashboard

I like your settings.php reference to the version, but perhaps you can link back to the github page when clicking on the icon on the left?
Or even just an about portion of the script?
I know these are more mature features for a pre-release.
I am trying to keep this dashboard going since my coding is subpar ;)

you want it to link to the main Github page? or just that versions page?

Whatever you think!
Just trying to make it easier for people to get back here and utilize the issue feature.

hmmmm, an about portion might work


promsql.ParseStmts() crashes on input starting with I=

After fuzzing promql.ParseStmts() (see #667), crashes were found when the input starts with I=, ex: I=-/, I=0---0d and I=3E8/-=, but also one case with M=-=-0-0. (Ran 2,6M different cases so far)
The stack traces generally look to be on the form
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x28 pc=0x3f696]

goroutine 1 [running]:
github.com/prometheus/prometheus/promql.(*parser).recover(0xc2080a2620, 0xc2080b3e20)
	/var/folders/sx/dbshyxqs4ks06n4f91r1qb800000gn/T/go-fuzz-build553606002/src/github.com/prometheus/prometheus/promql/parse.go:326 +0x113
github.com/prometheus/prometheus/promql.(*UnaryExpr).Type(0xc20801f820, 0xa040d0)
	/var/folders/sx/dbshyxqs4ks06n4f91r1qb800000gn/T/go-fuzz-build553606002/src/github.com/prometheus/prometheus/promql/ast.go:213 +0x66
github.com/prometheus/prometheus/promql.(*UnaryExpr).Type(0xc20801f840, 0x20)

But there's also a few cases where go-fuzz decided to kill things after 10 seconds without any output...

Same underlying bug as #940 and fixed in #954.
The examples were added as another regression test.


[BEAM-13182]  Add diagrams to backend readme

[BEAM-13182]  Add diagrams for RunCode and Validators/Preparators to backend readme

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

@daria-malkova Are you still working on this?

uuu I love these. Thanks!


Get review from ES spec editor

We should resolve the design problems first.

Done. There is a question about whether step 9a should be len + n (my preference, based on implementer feedback) or len - abs(n) (@allenwb's preference, based on consistency with indexOf). If that is a blocker for advancement I'll change it.


400 error with The Path property ... of ODataMessageWriterSetting.ODataUri must end with the navigation property which the contained elements being written belong to

See also: https://github.com/ncw/rclone/issues/3039
Category

[ ] Question
[ ] Documentation issue
[x] Bug

Expected or Desired Behavior
https://graph.microsoft.com/v1.0/drives/{drive_id}/items/{item_id}:/photo should produce correct response
Observed Behavior
400 error with message

"message": "The Path property ... of ODataMessageWriterSetting.ODataUri must end with the navigation property which the contained elements being written belong to.",

Steps to Reproduce

Create folder named "photo" within a parent folder
Call api https://graph.microsoft.com/v1.0/drives/{drive_id}/items/{item_id}:/photo where {item_id} is the id of the parent folder.

This error is caused by having "photo" as directory name.
Thank you.

thanks bot!

I'd like to add some related things: If there is a trailing colon in the path (E.g., /drives/{drive_id}/items/{item_id}:/photo:), there seems to be no problem. And, there is actually an issue similar to this: #941. And, this seems to affect both OneDrive for Business and OneDrive Personal.

Thanks @qx-juilliard - this is definitely a weird one.

Thanks @qx-juilliard - this is definitely a weird one.
Do you by any chance have the request-id and date values that would have also been returned in the response along with that error message?

  "error": {
    "code": "BadRequest",
    "message": "The Path property 'drives('b%my_drive_id')/items('my_path_id%3A')/photo' of ODataMessageWriterSetting.ODataUri must end with the navigation property which the contained elements being written belong to.",
    "innerError": {
      "request-id": "3f4dee5b-dee4-48ab-804d-2797e609c1f5",
      "date": "2019-03-10T04:52:16"
    }
  }

Thanks for the details - that's exactly what we needed!

We're drilling in to what's going on now, but at least the work around suggested by @Cnly appears to work. I'd definitely recommend using that while we work on fixing the underlying issue.

Hey all, I tried reproing this again and it seems like it was fixed by Graph. Do you all concur? If so, I'll mark this issue as resolved.


added common parse() for connection parameters

Proposal:

re-use same function to parse a connection string into parameters map.

@mloskot let me disagree http://en.cppreference.com/w/cpp/container/map/operator_at  T operator[](const T&) should work in this case.

@mloskot I'm talking about key here, not return value.

@mloskot I'm talking about key here, not return value.

@snikulov Sorry for confusion, I should have said in https://github.com/SOCI/soci/pull/547#discussion_r127269132 that I mean
Regardless if value below is char* or string const&, copy of value is made

Sorry if it was unclear, but my main point was that even if these changes are necessary, it would be better to make them as separate commits, e.g. one commit for adding sudo: required, another commit changing const char* to std::string (although I am still not sure why is it needed) etc.
On a related note, it would also be great if we could agree to use the standard format for the commit messages, i.e., in brief, write them in imperative mood with 50 char summary and body wrapped to 72 columns and explaining what was done in the commit and why (see e.g. https://chris.beams.io/posts/git-commit/ for more details).

And on the topic of "having a single version of the broken code instead of multiple ones": I don't think this is quite correct, I believe you copied the wrong version (sqlite3 one, apparently) instead of a better one (mysql one). I.e. it looks like mysql wouldn't crash on foo=" parameter before, but would now. I don't care about MySQL one way or the other, but this does seem like regression to me (admittedly, SQLite is unchanged because it was already broken).

@vadz

it would be better to make them as separate commits

I agree.

it would also be great if we could agree to use the standard format for the commit messages, i.e., in brief, write them in imperative mood with 50 char summary and body wrapped to 72 columns and explaining what was done in the commit and why

I agree. I try to follow this guidelines most of the time, especially in ad-hoc PRs I submit to variety projects - good commit message can help defending the change :-)

@mloskot @vadz ok. thank you for a guideline.

BTW, pretty much de-facto gold standard for commit messages is http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html


Any chance you could do a new build to NPM soon?

I'm hoping to get the changes to #45 into my project.

Say no more, 2.1.8 released!

Thanks!


ng-double click overriden

Hi!
I was wondering. using this directive blocks the ng-dblclick events, just the same as the older versions of pure jquery ui. I know that people have been using some hacks (I know i did) to trigger selection only after a few pixels have been moved with the mouse.
Is this supported in your directive or should I implement it myself?
Kind Regards
Hubert Sobków

neverming i just used delay option on it! :D

This is the way! ;)


[explore] hide "Time Grain" Viz.is_timeseries=False

Both for Druid and SQLA

i don't believe this is an issue in explore V2.


ajustando scrip de lint

Coverage remained the same at 100.0% when pulling 35d49932cc7a46c4a7d81e791ab55d1e28b85855 on fixLint into 1a9e6a022b828f699673714d0b9decaaf9201bf7 on master.

Coverage remained the same at 100.0% when pulling 35d49932cc7a46c4a7d81e791ab55d1e28b85855 on fixLint into 1a9e6a022b828f699673714d0b9decaaf9201bf7 on master.


yamale: 4.0.4 -> 5.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for yamale is: A schema and validator for YAML
meta.homepage for yamale is: https://github.com/23andMe/Yamale
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.0.0 with grep in /nix/store/pplwniqjqd7gvki92mckj57ffgidldqg-python3.11-yamale-5.0.0
found 5.0.0 in filename of file in /nix/store/pplwniqjqd7gvki92mckj57ffgidldqg-python3.11-yamale-5.0.0

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

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath
chart-testing
opsdroid
python311Packages.python-fx
python311Packages.qiling
python311Packages.yamale
python312Packages.python-fx
python312Packages.qiling
python312Packages.yamale
yamale

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pplwniqjqd7gvki92mckj57ffgidldqg-python3.11-yamale-5.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/7fede6446e9119b9d3ee99c10ca7e75a8f9ce48c#yamale

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pplwniqjqd7gvki92mckj57ffgidldqg-python3.11-yamale-5.0.0
ls -la /nix/store/pplwniqjqd7gvki92mckj57ffgidldqg-python3.11-yamale-5.0.0/bin

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

2 packages failed to build:

python312Packages.qiling
python312Packages.qiling.dist

13 packages built:

chart-testing
opsdroid
opsdroid.dist
python311Packages.python-fx
python311Packages.python-fx.dist
python311Packages.qiling
python311Packages.qiling.dist
yamale (python311Packages.yamale)
yamale.dist (python311Packages.yamale.dist)
python312Packages.python-fx
python312Packages.python-fx.dist
python312Packages.yamale
python312Packages.yamale.dist

Maintainer pings
cc @rtburns-jpl for testing.

Already on master.


Splunk 6.6.0 Support

We are looking for Splunk 6.6.0 support and would like to know when an upgraded version will be out to support this release.
Thank you

Hi Farriesk,
Thanks for the feedback regarding 6.6.0 support. I have tested the current release with Splunk 6.6.0 and it is compatible. I have updated Splunk Base to show support for 6.6.0.
Regards,
Paul Nguyen


Captured Flag

Issue: #349
DOC Link:
https://docs.google.com/document/d/1i0O7LuwXnOPFesbDQF83Q207Ti-LxCFU/edit?usp=sharing&ouid=118226958913089808969&rtpof=true&sd=true

@kushal7201 Add screenshot of the course completion and mention how you found the key

@rakim-0  I have already added the screenshot in the PR and the code in the DOC file

I meant that the screenshot should be put the in the doc not in the PR itself.


Question: View above the HMSegmentedControl

Is there a way to insert a static (i.e. non parallax) view above the HMSegmentedControl - so the control does not appear at the top of the screen. For instance, if one wanted to put content above the control that shows regardless of selected segment.
Or is VGParallaxHeader the preferred approach to this - but 'turning off' the parallax effect?

Any thoughts on how best to achieve this?

Hi @jwardle
I think you can use the sticky view property of the VGParallaxHeader but I'm not sure to understand well what you want to achieve..

That is one way to achieve it I guess. I was more referring to a view above the HMSegmentedContol - like a TableView Header view, rather than having to use the parallax header, as one may not want the view above the segmented control to be 'parallaxed'. Does that make more sense?

If you don't want a parallax effect, you can use the VGParallaxHeaderModeCenter or VGParallaxHeaderModeTop when you set your header. But it wont be like a tableview header, I guess you would need a VGParallaxHeaderModeBottom but it doesn't exist. I think the sticky view property would do the trick.


fix(checks): align AVD-AWS-0107 and AVD-AWS-0105 checks with CIS Benchmarks

This PR includes alignment of AVD-AWS-0107 and AVD-AWS-0105 checks with AWS CIS benchmarks v1.2 and v1.4.
AVD-AWS-0107
Before: The check is triggered if a CIDR defines more than one public IP
Now: The check is triggered if the rule contains a CIDR that defines all available IP addresses, and uses TCP or UDP protocols for SSH or RDP ports.
Severity changed from CRITICAL to HIGH.
Ref:

https://docs.aws.amazon.com/securityhub/latest/userguide/ec2-controls.html#ec2-13
https://docs.aws.amazon.com/securityhub/latest/userguide/ec2-controls.html#ec2-14

AVD-AWS-0105
Before: The check is triggered if a CIDR defines more than one public IP
Now: The check is triggered if the rule contains a CIDR that defines all available IP addresses and uses the TCP protocol for SSH or RDP ports. Severity changed from CRITICAL to MEDIUM and check added to aws-cis-1.4 compliance.
Ref:

https://docs.aws.amazon.com/securityhub/latest/userguide/ec2-controls.html#ec2-21

Fixes:

https://github.com/aquasecurity/trivy/issues/7267

Related PRs:

https://github.com/aquasecurity/trivy-checks/pull/256

@nikpivkin lgtm, should we merge it?

@simar7 Can you take a look https://github.com/aquasecurity/trivy-checks/pull/256 ?

@simar7 Can you take a look #256 ?

merged


add --version flag on cli for xcaddy itself

so I can easier tell what version of xcaddy I am running can you please add a --version flag.  I mean the version of xcaddy not caddy2.
xcaddy --version
Even better if it doesn't impact (i.e. <1000ms) compile time have it always check and report if it needs to update and offer to go get -u right there.

Funny, today I tried the same thing :D Would be great to have this flag!
hnrk@host1:~$ xcaddy --version
go list -m: not using modules
2021/02/19 10:11:41 [ERROR] exec [go list -m]: exit status 1:
hnrk@host1:~$ xcaddy version
go list -m: not using modules
2021/02/19 10:11:48 [ERROR] exec [go list -m]: exit status 1:

Makes it easier to see if there's already a newer version available that fixed bugs in currently installed version.


functions/codelabs/gopher: tree is not installed by default

UX issue: The codelab recommends using Cloud Shell but references the tree command at the bottom of step 2 of the tutorial, which does not come with Cloud Shell out of the box. I would recommend providing link/instructions on how to install it or at least note that it doesn't come with Cloud Shell.

Thank you for reporting this! I updated the snippet to include installing tree:
$ sudo apt-get install tree # Optional.
$ tree # Optional.
.
├── cmd
│   └── main.go     # Binary to run the function locally.
├── go.mod          # Go module definition.
├── gophercolor.png # The gopher!
├── gopher.go       # Go file with the function.
└── gopher_test.go  # Go test file.


Row/column indexing error?

When running this code, I get the following error:
 File "./visualize-tsne/modules.py", line 267, in _scatter
    image[x0 + dx:x0 + dx + x1, y0 + dy:y0 + dy + y1] = small_img
ValueError: could not broadcast input array from shape (80,65,3) into shape (65,80,3)

This can be fixed by adding the following line:
if np.max(image[x0 + dx:x0 + dx + x1, y0 + dy:y0 + dy + y1]) > 0:
  continue
--> small_img = small_img.transpose(1,0,2)
image[x0 + dx:x0 + dx + x1, y0 + dy:y0 + dy + y1] = small_img

But then the images are all rotated 90 degrees.
Simply switching the indices lead to some other issues.

I returned to the code last week as i wanted to add UMAP projections and found out a few bugs that i'm now fixing. I'll look into that too. Hopefully I'll have time to push an improved version this week.

meanwhile
try changing line 251 to
image = np.zeros((self.output_img_size + self.each_img_size, self.output_img_size + self.each_img_size, 3)) * self.background_color
that should solve it

project updated


What's the status of rev B HW? Was it tested? Is FW available for rev B hardware?

%subj% see https://rusefi.com/forum/viewtopic.php?p=49347#p49347

Rev B works great. Current Beer Money Motorsports ECUs use the rev B module.
Same firmware works on rev A or B.


FR: caltialize headers rule

Nice plug-in!
How difficult is it to add new rules? One that will reformat headers to Capitalized would be great!

Are you asking about # Title Case Headers or # Just the first word of a header ?

All of those options seem good to have! A smart option that skips words like 'the' and 'of' would also be great.

I can try and work on this when I have some time later but anyone should feel free to beat me to it!

Thanks for adding this! What's the correct way for me to add the rule? capitalize-headings titleCase=true shows an error saying it's not recognized .

Have you installed the plugin from the repo manually? I haven't pushed a new release with the new rule yet, will do that sometime this week.

ah! no, I have it installed though the appstore. thanks again for adding it. look fwd to giving it a run


Incorrect Type Definition of ChaincodeResponse

Shim.success and Shim.error functions return SuccessResponse and ErrorResponse. The return types are defined using JSDoc and both type definitions are also defined using JSDoc in the same file.
However, for the TypeScript definition, ChaincodeResponse is used instead. It requires three properties including status, message, and payload. But both users Shim.success and Shim.error do not return an object with all three properties at the same time. In this case, I believe the type definition of ChaincodeResponse is incorrect.

I agree. Perhaps the TypeScript types would be better defined like this?
interface SuccessResponse {
    status: RESPONSE_CODE.OK;
    message?: string;
    payload: Uint8Array;
}

interface ErrorResponse {
    status: RESPONSE_CODE.ERROR;
    message: string;
    payload?: Uint8Array;
}

type ChaincodeResponse = SuccessResponse | ErrorResponse;

export class Shim {
    static error(msg: Uint8Array): ErrorResponse;
    static success(payload?: Uint8Array): SuccessResponse;
    // ...
}

So any fix can properly address your issue, I'm interested to know the impact of this typing mismatch on your use of the API.

I think the fix could be the following:
interface SuccessResponse { // <- message is unnecessary for SuccessResponse
    status: ChaincodeStub.RESPONSE_CODE.OK;
    payload: Uint8Array;
}

interface ErrorResponse { // <- payload is unnecessary for ErrorResponse
    status: ChaincodeStub.RESPONSE_CODE.ERROR;
    message: string;
}

type ChaincodeResponse = SuccessResponse | ErrorResponse;

export class Shim {
    static error(msg: string): ErrorResponse; // <- this should be string instead of Uint8Array
    static success(payload?: Uint8Array): SuccessResponse;
    // ...
}

I was writing test cases for my chain code and discovered the issue. Do you think we can make a pull request?

Definitely you are correct that the error function should take a string parameter: error(msg: string): ErrorResponse.
The only slight concern is that the ChaincodeResponse returned from the ChaincodeInterface methods really can be anything that fits the shape:
interface ChaincodeResponse {
    status: number;
    message?: string;
    payload? Uint8Array;
}

However, this is really an implementation detail only affecting the low-level shim API for implementing chaincode, and the values that actually make sense better fit your type definitions.
Please feel free to open a PR to modify the types as you've described.


satisfy test: the server queries the chain for badge data at the associated address (1 day)

[ ] Plugin queries POAP contract for token balances for the logged in user
[ ] Write the getter in a way that will query multiple badge contracts

Keys:value pairs for multiple badge contracts and multiple badge IDs


Cannot run cargo doc on Windows; Linux works fine

Whenever I run cargo doc on any project, cargo panics with the error:
$ cargo new test
$ cd test
$ cargo doc
thread '<main>' panicked at 'called `Option::unwrap()` on a `None` value', C:\bot\slave\nightly-dist-rustc-win-64\build\src\libcore\option.rs:362

If cargo doc is run with RUST_BACKTRACE=1, it outputs a not-so-useful backtrace on Windows:
$ RUST_BACKTRACE=1 cargo doc
thread '<main>' panicked at 'called `Option::unwrap()` on a `None` value', C:\bot\slave\nightly-dist-rustc-win-64\build\src\libcore\option.r
s:362
stack backtrace:
   1:           0x7f4684 - main
   2:           0x80ea89 - main
   3:           0x7655a7 - main
   4:           0x765d3a - main
   5:           0x80e52a - main
   6:           0x823e99 - main
   7:           0x821191 - main
   8:           0x5a4466 - main
   9:           0x5a479c - main
  10:           0x5a4a2e - main
  11:           0x4f5309 - main
  12:           0x464403 - main
  13:           0x5321d8 - main
  14:           0x55a65b - main
  15:           0x4d4cfc - main
  16:           0x4ce197 - main
  17:           0x4ca2cb - main
  18:           0x4e3287 - main
  19:           0x41db3e - main
  20:           0x40936d - main
  21:           0x4044ae - main
  22:           0x40212a
  23:           0x810e1c - main
  24:           0x810df9 - main
  25:           0x80f36c - main
  26:           0x4013b5
  27:           0x4014e8
  28:     0x7ffd672316ad - BaseThreadInitThunk

This will only fail on Windows. Running cargo doc on Linux will successfully generate the rustdocs without panicking.
cargo test and cargo build both work on Windows and Linux without panicking.
cargo --version:

Windows: cargo 0.0.1-pre-nightly (dd7c7bd 2015-03-04) (built 2015-03-05)
Linux: cargo 0.0.1-pre-nightly (dd7c7bd 2015-03-04) (built 2015-03-04)

Because I had some old Rust installers laying around, I tested the issue with older versions. It fails on a58ffd7, but it works without panicking on 43755c0. This leads me to believe that the regression was introduced between these two commits.

Hm I can't seem to reproduce this with the Cargo built on 3/9, does this still reproduce for you?

Recompiling Cargo with the 2015-03-09 rustc. I get the same issue.
cargo --version

Windows: cargo 0.0.1-pre (66849de 2015-03-10) (built 2015-03-10)

Because it might be useful to know, I'm running x86-64 builds as well.
I'll work on getting a meaningful backtrace.

I've found gdb better at getting backtraces, but I've also found it's more reliable on 32-bit than 64-bit, but times may change!

Just tested on 32-bit. It gives the same issue.

thread '<main>' panicked at 'called `Option::unwrap()` on a `None` value', C:/bot/slave/nightly-dist-rustc-win-64/build/src/libcore\option.rs:362
[Inferior 1 (process 2568) exited with code 0145]
(gdb) bt
No stack.

:(
Is cargo not compiled with debug symbols by default? Is there any way to get them?

Okay, gdb says the issue occurs on this line: https://github.com/rust-lang/cargo/blob/master/src/cargo/sources/path.rs#L102
Using some good ol' println-based debugging, the values of p and root are:
p: "C:\src\rust\cargo-test\test\.gitignore"
root: "c:\src\rust\cargo-test\test"

I removed .gitignore to see if it had anything to do with the prefixed dot. Nope, same problem.
p: "C:\src\rust\cargo-test\test\Cargo.toml"
root: "c:\src\rust\cargo-test\test"

use std::path::Path;
fn main() {
    let p = Path::new(r"C:\src\rust\cargo-test\test\Cargo.toml");
    println!("{:?}", p.relative_from(r"C:\src\rust\cargo-test\test"));
    println!("{:?}", p.relative_from(r"c:\src\rust\cargo-test\test"));
}

Some("Cargo.toml")
None

A difference in the hard drive letter's case is throwing it off. Is this a bug in Rust or in Cargo, then? :)

Ah, this sounds like a Rust bug in that case, could you open an issue about it?

Thanks for investigating!


Tweet evaluator updates

I've added getters for Tweet replies and of utc offset (both of these are getters that we need to update the Gnip-Tweet-Evaluation repo).

I've already re-built the github pages to match this branch, so go ahead and check those out.


Codable firestore

Hi guys! So this is a WIP PR to solve #627. It is based on #815.
In general, code is almost 1-to-1 port of JSONEncoder from Foundation and PlistEncoder with some minor changes to fit it to Firestore. Most of the code is just boilerplate and the most interesting part is in
func unbox<T : Decodable>(_ value: Any, as type: T.Type) throws -> T?

in FirestoreDecoder and
func box_<T : Encodable>(_ value: T) throws -> NSObject?

in FirestoreEncoder.
I also created internal types Firestore.Encoder and Firestore.Decoder to able to test without needing DocumentReference and DocumentSnapshot. Everything is internal now without any public methods, so that we can already start testing and deciding if it's the right approach without the pain of approving the public API
//сс @wilhuff @paulb777

I signed it!

@wilhuff I merged master into this branch... And now I am not sure what should I do :) Should I create another PR against master?

Just keep going. If you're really concerned about the clarity of the PR
stack, feel free to rebase your changes and force push to your repository.
We're going to squash merge your change into canonical history so it
doesn't matter too much if your changes are all that clear at the commit
level.
On Tue, Feb 27, 2018 at 7:44 AM Oleksii Dykan<EMAIL_ADDRESS>wrote:

@wilhuff https://github.com/wilhuff I merged master into this branch...
And now I am not sure what should I do :) Should I create another PR
against master?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-ios-sdk/pull/838#issuecomment-368922101,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJxjkPzXejXuGEt0sJQM_mbBBiYa9jahks5tZCLagaJpZM4SPic9
.

The base PR from which this started has since been merged to master. I've retargeted this PR against master and now the diff is clean again.

Any progress on this? Would be great to have this part of the SDK.

Thanks for the hard work @alickbass @wilhuff!
Do you have any updates on the status of this issue/pull request. Would love to use it soon!

A great work @alickbass @wilhuff. Thank you both.
Any updates about this PR? It's a really needed feature.

Hi guys! What's the progress on this beautiful and highly anticipated feature?

Any update on this?

Closing and continuing in #2178


boost urls broken/outdated.

Note: If you use the fuzzy expressions such as 'can't use/no effect/problem/error', but don't give any relevant auxiliary information according to the template below, this issue will be not replied.

Describe the bug
trying to download boost 1.75.0 (the most recent version in this repository) fails.
Expected behavior
The urls provided by the package point to current boost repositories.
Error output
xmake output:

xmake config

note: try installing these packages (pass -y to skip confirm)?
in xmake-repo:
-> boost 1.75.0
please input: y (y/n)
y
=> download https://github.com/xmake-mirror/boost/releases/download/boost-1.75.0/boost_1_75_0.tar.bz2 .. failed
=> download https://dl.bintray.com/boostorg/release/1.75.0/source/boost_1_75_0.tar.bz2 .. failed
we can also download these packages manually:

https://github.com/xmake-mirror/boost/releases/download/boost-1.75.0/boost_1_75_0.tar.bz2
https://dl.bintray.com/boostorg/release/1.75.0/source/boost_1_75_0.tar.bz2
to the local search directories:
boost_1_75_0.tar.bz2
and we can run xmake g --pkg_searchdirs=/xxx to set the search directories.
error: download failed!

https://github.com/xmake-mirror/boost/releases/download/boost-1.75.0/boost_1_75_0.tar.bz2
returns a 404 Page not found.
https://dl.bintray.com/boostorg/release/1.75.0/source/boost_1_75_0.tar.bz2
returns a 403 Forbidden.
Related Environment
I don't think this is necessary.
Additional context
The root causes seem to be:

The xmake-mirror repository  does not contain the newest boost versions (1.72.0 is the latest).

bintray is shutting down. Boost has moved to jfrog. See boostorg/boost#502
the new link seems to be:
https://boostorg.jfrog.io/artifactory/main/release/1.75.0/source/boost_1_75_0.tar.bz2

It has been fixed, https://github.com/xmake-io/xmake-repo/pull/387
and I will update boost mirror files.

Thank you for the quick fix guys.


Add numpy docstrings to CIF object

The core ones addressed here https://github.com/bobleesj/cifkit/pull/54
Try to refactor the code more before writing more docstrings.


Can't select Amazon Linux 2023 (Default) as the build image

Environment information
-

Description
The default pre-selected build setting image was Amazon Linux 2023 (default) for my NextJS App Router Amplify App. After changing the build image between Amazon Linux 1, Amazon Linux 2, and/or Custom Build Image, the interface does not allow you to change back to Amazon Linux 2023 (default).
I require Amazon Linux 2023 (default) as the build image for my application to run so I am currently blocked without a way to successfully build my app

@renchris 👋 , thanks for reaching out. I was able to reproduce this behavior and marking this as a bug.
In the meantime, as a workaround you can manually update the _CUSTOM_IMAGE environment variable for your app amplify:al2023  to use the Amazon Linux 2023 default image.

@renchris we have deployed a fix for this issue. Can you please confirm if you are now able to switch back to the Amazon Linux 2023 image in the console? Thanks!

I can now select and switch back to the Amazon Linux 2023 (default) build image. Thanks!

This still happened to me in a project in my apps that were on Linux 2 before the release of Linux 2023. The environment variable allowed me to switch, though.


Add column layout plugin example

Another example of nested elements for columns layout plugin
https://github.com/facebook/lexical/assets/132642/7b825e11-3fa9-4983-95da-6b1c5713d7c0

@fantactuka This is fantastic! Thank you raising the PR!

hey @zurfyx whats the exportDOM here?
like i want to use this to generate HTML, and I'm not sure what html does this node outputs?


Auto-Build 2022-01-01 21:40 can't crop

-c:v libx264 -vf crop=
Auto-Build 2022-01-01 21:40 can't crop
Auto-Build 2021-12-31 12:20 worked

You should report that to upstream ffmpeg.
It's very unlikely that these builds randomly break the crop filter.
Your commandline is also incomplete.