[Bug]: TimeoutError During Benchmark Profiling with Torch Profiler on vLLM v0.6.0

Your current environment

The output of `python collect_env.py`
PyTorch version: 2.4.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: 14.0.0-1ubuntu1.1
CMake version: version 3.27.7
Libc version: glibc-2.35

Python version: 3.8.18 (default, Sep 11 2023, 13:40:15)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.4.119-19-0009.11-x86_64-with-glibc2.17
Is CUDA available: True
CUDA runtime version: 12.4.131
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA A800-SXM4-80GB
Nvidia driver version: 470.182.03
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_engines_precompiled.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_engines_runtime_compiled.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_graph.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_heuristic.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops.so.9.1.0
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Address sizes:                   48 bits physical, 48 bits virtual
Byte Order:                      Little Endian
CPU(s):                          232
On-line CPU(s) list:             0-231
Vendor ID:                       AuthenticAMD
Model name:                      AMD EPYC 7K83 64-Core Processor
CPU family:                      25
Model:                           1
Thread(s) per core:              2
Core(s) per socket:              58
Socket(s):                       2
Stepping:                        1
BogoMIPS:                        4890.80
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid amd_dcm tsc_known_freq pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext perfctr_core invpcid_single ssbd ibrs ibpb stibp vmmcall fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr wbnoinvd arat umip pku ospke vaes vpclmulqdq rdpid fsrm
Hypervisor vendor:               KVM
Virtualization type:             full
L1d cache:                       3.6 MiB (116 instances)
L1i cache:                       3.6 MiB (116 instances)
L2 cache:                        58 MiB (116 instances)
L3 cache:                        512 MiB (16 instances)
NUMA node(s):                    2
NUMA node0 CPU(s):               0-115
NUMA node1 CPU(s):               116-231
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full AMD retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected

Versions of relevant libraries:
[pip3] numpy==1.24.4
[pip3] nvidia-cublas-cu11==<IP_ADDRESS>
[pip3] nvidia-cublas-cu12==<IP_ADDRESS>
[pip3] nvidia-cuda-cupti-cu11==11.7.101
[pip3] nvidia-cuda-cupti-cu12==12.1.105
[pip3] nvidia-cuda-nvrtc-cu11==11.7.99
[pip3] nvidia-cuda-nvrtc-cu12==12.1.105
[pip3] nvidia-cuda-runtime-cu11==11.7.99
[pip3] nvidia-cuda-runtime-cu12==12.1.105
[pip3] nvidia-cudnn-cu11==<IP_ADDRESS>
[pip3] nvidia-cudnn-cu12==<IP_ADDRESS>
[pip3] nvidia-cufft-cu11==<IP_ADDRESS>
[pip3] nvidia-cufft-cu12==<IP_ADDRESS>
[pip3] nvidia-curand-cu11==<IP_ADDRESS>
[pip3] nvidia-curand-cu12==<IP_ADDRESS>
[pip3] nvidia-cusolver-cu11==<IP_ADDRESS>
[pip3] nvidia-cusolver-cu12==<IP_ADDRESS>
[pip3] nvidia-cusparse-cu11==<IP_ADDRESS>
[pip3] nvidia-cusparse-cu12==<IP_ADDRESS>
[pip3] nvidia-dali-cuda120==1.36.0
[pip3] nvidia-ml-py==12.560.30
[pip3] nvidia-nccl-cu11==2.14.3
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] nvidia-nvimgcodec-cu12==<IP_ADDRESS>
[pip3] nvidia-nvjitlink-cu12==12.4.99
[pip3] nvidia-nvtx-cu11==11.7.91
[pip3] nvidia-nvtx-cu12==12.1.105
[pip3] pynvml==11.5.0
[pip3] pyzmq==26.2.0
[pip3] torch==2.4.0
[pip3] torchvision==0.19.0
[pip3] transformers==4.44.2
[pip3] transformers-stream-generator==0.0.4
[pip3] triton==3.0.0
[pip3] tritonclient==2.43.0
[conda] numpy                     1.24.4                   pypi_0    pypi
[conda] nvidia-cublas-cu11        <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-cublas-cu12        <IP_ADDRESS>                 pypi_0    pypi
[conda] nvidia-cuda-cupti-cu11    11.7.101                 pypi_0    pypi
[conda] nvidia-cuda-cupti-cu12    12.1.105                 pypi_0    pypi
[conda] nvidia-cuda-nvrtc-cu11    11.7.99                  pypi_0    pypi
[conda] nvidia-cuda-nvrtc-cu12    12.1.105                 pypi_0    pypi
[conda] nvidia-cuda-runtime-cu11  11.7.99                  pypi_0    pypi
[conda] nvidia-cuda-runtime-cu12  12.1.105                 pypi_0    pypi
[conda] nvidia-cudnn-cu11         <IP_ADDRESS>                 pypi_0    pypi
[conda] nvidia-cudnn-cu12         <IP_ADDRESS>                 pypi_0    pypi
[conda] nvidia-cufft-cu11         <IP_ADDRESS>                pypi_0    pypi
[conda] nvidia-cufft-cu12         <IP_ADDRESS>                pypi_0    pypi
[conda] nvidia-curand-cu11        <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-curand-cu12        <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-cusolver-cu11      <IP_ADDRESS>                 pypi_0    pypi
[conda] nvidia-cusolver-cu12      <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-cusparse-cu11      <IP_ADDRESS>                pypi_0    pypi
[conda] nvidia-cusparse-cu12      <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-ml-py              12.560.30                pypi_0    pypi
[conda] nvidia-nccl-cu11          2.14.3                   pypi_0    pypi
[conda] nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
[conda] nvidia-nvjitlink-cu12     12.4.99                  pypi_0    pypi
[conda] nvidia-nvtx-cu11          11.7.91                  pypi_0    pypi
[conda] nvidia-nvtx-cu12          12.1.105                 pypi_0    pypi
[conda] pynvml                    11.5.0                   pypi_0    pypi
[conda] pyzmq                     26.2.0                   pypi_0    pypi
[conda] torch                     2.4.0                    pypi_0    pypi
[conda] torchvision               0.19.0                   pypi_0    pypi
[conda] transformers              4.44.2                   pypi_0    pypi
[conda] transformers-stream-generator 0.0.4                    pypi_0    pypi
[conda] triton                    3.0.0                    pypi_0    pypi
[conda] tritonclient              2.43.0                   pypi_0    pypi
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.6.0@32e7db25365415841ebc7c4215851743fbb1bad1
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    CPU Affinity    NUMA Affinity
GPU0     X      116-231 1

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

🐛 Describe the bug
I am attempting to profile the performance of vLLM v0.6.0 by following the vLLM profiling documentation.
Here’s the process I followed:

Set up the profiler environment:

export VLLM_TORCH_PROFILER_DIR=/app/vllm_profile

Launched the OpenAI server:

python -m vllm.entrypoints.openai.api_server --tensor-parallel-size 1 \
--model /mnt/llm_dataset/willhe/ckpt/Meta-Llama-3.1-8B-Instruct-quantized.w8a8 \
--trust-remote-code --max-model-len 8192

Launched the benchmark process:

python benchmark_serving.py --backend vllm --model /mnt/llm_dataset/willhe/ckpt/Meta-Llama-3.1-8B-Instruct-quantized.w8a8 \
--dataset-name sharegpt --dataset-path sharegpt.json --num-prompts 2 --profile

Error Encountered:
While running the benchmark, I encountered a TimeoutError: Server didn't reply within 5000 ms in the vLLM OpenAI server log. The relevant section of the log is as follows:

WARNING 09-10 16:07:55 api_server.py:327] Torch Profiler is enabled in the API server. This should ONLY be used for local development!
INFO 09-10 16:07:55 api_server.py:459] vLLM API server version 0.6.0
INFO 09-10 16:07:55 api_server.py:460] args: Namespace(allow_credentials=False, allowed_headers=['*'], allowed_methods=['*'], allowed_origins=['*'], api_key=None, block_size=16, chat_template=None, code_revision=None, collect_detailed_traces=None, cpu_offload_gb=0, device='auto', disable_async_output_proc=False, disable_custom_all_reduce=False, disable_frontend_multiprocessing=False, disable_log_requests=False, disable_log_stats=False, disable_logprobs_during_spec_decoding=None, disable_sliding_window=False, distributed_executor_backend=None, download_dir=None, dtype='auto', enable_auto_tool_choice=False, enable_chunked_prefill=None, enable_lora=False, enable_prefix_caching=False, enable_prompt_adapter=False, enforce_eager=False, engine_use_ray=False, fully_sharded_loras=False, gpu_memory_utilization=0.9, guided_decoding_backend='outlines', host=None, ignore_patterns=[], kv_cache_dtype='auto', limit_mm_per_prompt=None, load_format='auto', long_lora_scaling_factors=None, lora_dtype='auto', lora_extra_vocab_size=256, lora_modules=None, max_context_len_to_capture=None, max_cpu_loras=None, max_log_len=None, max_logprobs=20, max_lora_rank=16, max_loras=1, max_model_len=8192, max_num_batched_tokens=None, max_num_seqs=256, max_parallel_loading_workers=None, max_prompt_adapter_token=0, max_prompt_adapters=1, max_seq_len_to_capture=8192, middleware=[], model='/mnt/llm_dataset/willhe/ckpt/Meta-Llama-3.1-8B-Instruct-quantized.w8a8', model_loader_extra_config=None, ngram_prompt_lookup_max=None, ngram_prompt_lookup_min=None, num_gpu_blocks_override=None, num_lookahead_slots=0, num_scheduler_steps=1, num_speculative_tokens=None, otlp_traces_endpoint=None, override_neuron_config=None, pipeline_parallel_size=1, port=8000, preemption_mode=None, prompt_adapters=None, qlora_adapter_name_or_path=None, quantization=None, quantization_param_path=None, ray_workers_use_nsight=False, response_role='assistant', return_tokens_as_token_ids=False, revision=None, root_path=None, rope_scaling=None, rope_theta=None, scheduler_delay_factor=0.0, seed=0, served_model_name=None, skip_tokenizer_init=False, spec_decoding_acceptance_method='rejection_sampler', speculative_disable_by_batch_size=None, speculative_draft_tensor_parallel_size=None, speculative_max_model_len=None, speculative_model=None, speculative_model_quantization=None, ssl_ca_certs=None, ssl_cert_reqs=0, ssl_certfile=None, ssl_keyfile=None, swap_space=4, tensor_parallel_size=1, tokenizer=None, tokenizer_mode='auto', tokenizer_pool_extra_config=None, tokenizer_pool_size=0, tokenizer_pool_type='ray', tokenizer_revision=None, tool_call_parser=None, trust_remote_code=True, typical_acceptance_sampler_posterior_alpha=None, typical_acceptance_sampler_posterior_threshold=None, use_v2_block_manager=False, uvicorn_log_level='info', worker_use_ray=False)
INFO 09-10 16:07:55 api_server.py:160] Multiprocessing frontend to use ipc:///tmp/961fbd3d-8728-4690-b8fe-0026ccbf61dd for RPC Path.
INFO 09-10 16:07:55 api_server.py:176] Started engine process with PID 12240
WARNING 09-10 16:07:58 cuda.py:22] You are using a deprecated `pynvml` package. Please install `nvidia-ml-py` instead, and make sure to uninstall `pynvml`. When both of them are installed, `pynvml` will take precedence and cause errors. See https://pypi.org/project/pynvml for more information.
WARNING 09-10 16:08:01 api_server.py:327] Torch Profiler is enabled in the API server. This should ONLY be used for local development!
INFO 09-10 16:08:01 llm_engine.py:213] Initializing an LLM engine (v0.6.0) with config: model='/mnt/llm_dataset/willhe/ckpt/Meta-Llama-3.1-8B-Instruct-quantized.w8a8', speculative_config=None, tokenizer='/mnt/llm_dataset/willhe/ckpt/Meta-Llama-3.1-8B-Instruct-quantized.w8a8', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, override_neuron_config=None, rope_scaling=None, rope_theta=None, tokenizer_revision=None, trust_remote_code=True, dtype=torch.bfloat16, max_seq_len=8192, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=1, pipeline_parallel_size=1, disable_custom_all_reduce=False, quantization=compressed-tensors, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), observability_config=ObservabilityConfig(otlp_traces_endpoint=None, collect_model_forward_time=False, collect_model_execute_time=False), seed=0, served_model_name=/mnt/llm_dataset/willhe/ckpt/Meta-Llama-3.1-8B-Instruct-quantized.w8a8, use_v2_block_manager=False, num_scheduler_steps=1, enable_prefix_caching=False, use_async_output_proc=True)
INFO 09-10 16:08:02 worker.py:124] Profiling enabled. Traces will be saved to: /app/vllm_profiler
INFO 09-10 16:08:02 model_runner.py:915] Starting to load model /mnt/llm_dataset/willhe/ckpt/Meta-Llama-3.1-8B-Instruct-quantized.w8a8...
Loading safetensors checkpoint shards:   0% Completed | 0/2 [00:00<?, ?it/s]
Loading safetensors checkpoint shards:  50% Completed | 1/2 [00:01<00:01,  1.43s/it]
Loading safetensors checkpoint shards: 100% Completed | 2/2 [00:03<00:00,  1.66s/it]
Loading safetensors checkpoint shards: 100% Completed | 2/2 [00:03<00:00,  1.62s/it]

INFO 09-10 16:08:06 model_runner.py:926] Loading model weights took 8.4939 GB
INFO 09-10 16:08:07 gpu_executor.py:122] # GPU blocks: 31260, # CPU blocks: 2048
INFO 09-10 16:08:09 model_runner.py:1217] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
INFO 09-10 16:08:09 model_runner.py:1221] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
INFO 09-10 16:08:21 model_runner.py:1335] Graph capturing finished in 12 secs.
INFO 09-10 16:08:22 api_server.py:224] vLLM to use /tmp/tmp_i4t0w55 as PROMETHEUS_MULTIPROC_DIR
WARNING 09-10 16:08:22 serving_embedding.py:190] embedding_mode is False. Embedding API will not work.
 To avoid this limit at the expense of performance run with --disable-frontend-multiprocessing
INFO:     Started server process [12171]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
INFO 09-10 16:08:32 metrics.py:351] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.0 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 09-10 16:10:21 logger.py:36] Received request cmpl-11174501eb824056b9a481a9ca45afad-0: prompt: 'Do you know the book Traction by Gino Wickman', params: SamplingParams(n=1, best_of=1, presence_penalty=0.0, frequency_penalty=0.0, repetition_penalty=1.0, temperature=0.0, top_p=1.0, top_k=-1, min_p=0.0, seed=None, use_beam_search=False, length_penalty=1.0, early_stopping=False, stop=[], stop_token_ids=[], include_stop_str_in_output=False, ignore_eos=False, max_tokens=119, min_tokens=0, logprobs=None, prompt_logprobs=None, skip_special_tokens=True, spaces_between_special_tokens=True, truncate_prompt_tokens=None), prompt_token_ids: [5519, 499, 1440, 279, 2363, 350, 16597, 555, 480, 3394, 75206, 1543], lora_request: None, prompt_adapter_request: None.
INFO:     <IP_ADDRESS>:45336 - "POST /v1/completions HTTP/1.1" 200 OK
INFO 09-10 16:10:21 async_llm_engine.py:206] Added request cmpl-11174501eb824056b9a481a9ca45afad-0.
INFO 09-10 16:10:21 metrics.py:351] Avg prompt throughput: 1.3 tokens/s, Avg generation throughput: 0.1 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 09-10 16:10:22 async_llm_engine.py:174] Finished request cmpl-11174501eb824056b9a481a9ca45afad-0.
INFO 09-10 16:10:22 async_llm_engine.py:174] Finished request cmpl-11174501eb824056b9a481a9ca45afad-0.
INFO 09-10 16:10:22 api_server.py:333] Starting profiler...
INFO 09-10 16:10:22 server.py:134] Starting profiler...
INFO:     <IP_ADDRESS>:45346 - "POST /start_profile HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/uvicorn/protocols/http/httptools_impl.py", line 419, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/uvicorn/middleware/proxy_headers.py", line 84, in __call__
    return await self.app(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/applications.py", line 123, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/middleware/errors.py", line 186, in __call__
    raise exc
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/middleware/errors.py", line 164, in __call__
    await self.app(scope, receive, _send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/middleware/cors.py", line 83, in __call__
    await self.app(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/middleware/exceptions.py", line 62, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/routing.py", line 758, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/routing.py", line 778, in app
    await route.handle(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/routing.py", line 299, in handle
    await self.app(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/routing.py", line 79, in app
    await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/starlette/routing.py", line 74, in app
    response = await func(request)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/fastapi/routing.py", line 278, in app
    raw_response = await run_endpoint_function(
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/fastapi/routing.py", line 191, in run_endpoint_function
    return await dependant.call(**values)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/vllm/entrypoints/openai/api_server.py", line 334, in start_profile
    await async_engine_client.start_profile()
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/vllm/entrypoints/openai/rpc/client.py", line 442, in start_profile
    await self._send_one_way_rpc_request(
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/vllm/entrypoints/openai/rpc/client.py", line 258, in _send_one_way_rpc_request
    response = await do_rpc_call(socket, request)
  File "/mnt/llm_dataset/willhe/miniconda3/envs/vllm/lib/python3.8/site-packages/vllm/entrypoints/openai/rpc/client.py", line 248, in do_rpc_call
    raise TimeoutError("Server didn't reply within "
TimeoutError: Server didn't reply within 5000 ms

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

INFO:     <IP_ADDRESS>:45346 - "POST /start_profile HTTP/1.1" 500 Internal Server Error I encounter a same issue in NV GPU

you can set --disable-frontend-multiprocessing to run the profiler. I will look into fixing this

@robertgshaw2-neuralmagic Hi, added --disable-frontend-multiprocessing did not work for me. I think above infos are not full, below is my full info, the real reason is  AttributeError: 'GPUExecutorAsync' object has no attribute '_run_workers'
INFO:     <IP_ADDRESS>:46236 - "POST /stop_profile HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/uvicorn/protocols/http/httptools_impl.py", line 401, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in __call__
    return await self.app(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/applications.py", line 123, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/middleware/errors.py", line 186, in __call__
    raise exc
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/middleware/errors.py", line 164, in __call__
    await self.app(scope, receive, _send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/middleware/cors.py", line 85, in __call__
    await self.app(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/middleware/exceptions.py", line 65, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/routing.py", line 754, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/routing.py", line 774, in app
    await route.handle(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/routing.py", line 295, in handle
    await self.app(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/routing.py", line 77, in app
    await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/starlette/routing.py", line 74, in app
    response = await f(request)
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/fastapi/routing.py", line 297, in app
    raw_response = await run_endpoint_function(
  File "/opt/conda/envs/py_3.9/lib/python3.9/site-packages/fastapi/routing.py", line 210, in run_endpoint_function
    return await dependant.call(**values)
  File "/root/vllm/vllm/entrypoints/openai/api_server.py", line 341, in stop_profile
    await async_engine_client.stop_profile()
  File "/root/vllm/vllm/engine/async_llm_engine.py", line 1283, in stop_profile
    self.engine.model_executor._run_workers("stop_profile")
AttributeError: 'GPUExecutorAsync' object has no attribute '_run_workers'

I forgot to handle the multiproc case. Will make a PR. For now set --worker-use-ray to use the ray backend and it should work.

For the timeout issue try setting the env var: VLLM_RPC_GET_DATA_TIMEOUT_MS=1800000

meet the same error:
AttributeError: 'GPUExecutorAsync' object has no attribute '_run_workers'


Emoji color display is not normal

Which operating system does the issue occur on?
macos
If on linux, are you using X11 or Wayland?
Emoji color display is not normal like this pic，how to set this？

It seems like it might be taking the text foreground color as color for the emoji? Can you confirm this by printing the emoji with a different color escape (like `echo -e "\e[31m")?

@chrisduerr  hi  this is my color setting

@taigacute Looks like I messed up the Github formatting. You need to add the emoji after the color escape.

@taigacute Looks like I messed up the Github formatting. You need to add the emoji after the color escape.

thanks for your help. you can see this pic

Closing as a duplicate of https://github.com/jwilm/alacritty/issues/1864.
While originally these issues were a bit different, I think it should be possible to fix it with one common solution.

结束为＃1864的副本。
虽然最初这些问题有点不同，但我认为应该可以通过一个通用的解决方案来解决它。

yes 。I think these two questions are related. I expect it to be solved

@chrisduerr
Thank you for your work, I have been paying attention to this issue and it has not been resolved. Unable to use emoji causes me not to switch to alacritty

I'd like to point out that when your background color is set to white, this leads to emojis being not visible at all. I've found this issue searching for "emojis don't work in Alacritty".


Update gitpod

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

Coverage data is based on head (c12827d) compared to base (348d081).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #406   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          123       123
  Lines        11438     11438
=========================================
  Hits         11438     11438

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

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


Integrate support for no-access Idps with all functionality

Ensured idps without access are visible & styled appropriately

💯 i agree with those full-width input fields.  I stuck to the design for now, but i'm really hoping that when it's tested it'll be a common conclusion!

I've made a separate commit for the displayUnnconnectedIdpsWayf !936
I've added error messages & styling as per the styleboard now 😄
I know, but it is as per the styleboard / designs.  I did forget the box-shadow which i've added now.
I agree, but followed the style board.  I'll ask Edwin/Arnout about our three known styling disagreements ;-)


Unable to install the new version 2.5 on windows

I tried several and also tried installing it on a different system that uses Windows OS but didn't work
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [74 lines of output]
Compiling av\buffer.pyx because it changed.
[1/1] Cythonizing av\buffer.pyx
Compiling av\bytesource.pyx because it changed.
[1/1] Cythonizing av\bytesource.pyx
Compiling av\descriptor.pyx because it changed.
[1/1] Cythonizing av\descriptor.pyx
Compiling av\dictionary.pyx because it changed.
[1/1] Cythonizing av\dictionary.pyx
Compiling av\enum.pyx because it changed.
[1/1] Cythonizing av\enum.pyx
Compiling av\error.pyx because it changed.
[1/1] Cythonizing av\error.pyx
Compiling av\format.pyx because it changed.
[1/1] Cythonizing av\format.pyx
Compiling av\frame.pyx because it changed.
[1/1] Cythonizing av\frame.pyx
performance hint: av\logging.pyx:232:5: Exception check on 'log_callback' will always require the GIL to be acquired.
Possible solutions:
1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
2. Use an 'int' return type on the function to allow an error code to be returned.
  Error compiling Cython file:
  ------------------------------------------------------------
  ...
  cdef const char *log_context_name(void *ptr) nogil:
      cdef log_context *obj = <log_context*>ptr
      return obj.name

  cdef lib.AVClass log_class
  log_class.item_name = log_context_name
                        ^
  ------------------------------------------------------------

  av\logging.pyx:216:22: Cannot assign type 'const char *(void *) except? NULL nogil' to 'const char *(*)(void *) noexcept nogil'. Exception values are incompatible. Suggest adding 'noexcept' to type 'const char *(void *) except? NULL nogil'.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...

  # Start the magic!
  # We allow the user to fully disable the logging system as it will not play
  # nicely with subinterpreters due to FFmpeg-created threads.
  if os.environ.get('PYAV_LOGGING') != 'off':
      lib.av_log_set_callback(log_callback)
                              ^
  ------------------------------------------------------------

  av\logging.pyx:351:28: Cannot assign type 'void (void *, int, const char *, va_list) except * nogil' to 'av_log_callback'. Exception values are incompatible. Suggest adding 'noexcept' to type 'void (void *, int, const char *, va_list) except * nogil'.
  Compiling av\logging.pyx because it changed.
  [1/1] Cythonizing av\logging.pyx
  Traceback (most recent call last):
    File "C:\Users\CodeWithJoel\AppData\Local\Programs\Python\Python312\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 353, in <module>
      main()
    File "C:\Users\CodeWithJoel\AppData\Local\Programs\Python\Python312\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 335, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "C:\Users\CodeWithJoel\AppData\Local\Programs\Python\Python312\Lib\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 118, in get_requires_for_build_wheel
      return hook(config_settings)
             ^^^^^^^^^^^^^^^^^^^^^
    File "C:\Users\CodeWithJoel\AppData\Local\Temp\pip-build-env-aihy54j2\overlay\Lib\site-packages\setuptools\build_meta.py", line 325, in get_requires_for_build_wheel
      return self._get_build_requires(config_settings, requirements=['wheel'])
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "C:\Users\CodeWithJoel\AppData\Local\Temp\pip-build-env-aihy54j2\overlay\Lib\site-packages\setuptools\build_meta.py", line 295, in _get_build_requires
      self.run_setup()
    File "C:\Users\CodeWithJoel\AppData\Local\Temp\pip-build-env-aihy54j2\overlay\Lib\site-packages\setuptools\build_meta.py", line 480, in run_setup
      super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
    File "C:\Users\CodeWithJoel\AppData\Local\Temp\pip-build-env-aihy54j2\overlay\Lib\site-packages\setuptools\build_meta.py", line 311, in run_setup
      exec(code, locals())
    File "<string>", line 156, in <module>
    File "C:\Users\CodeWithJoel\AppData\Local\Temp\pip-build-env-aihy54j2\overlay\Lib\site-packages\Cython\Build\Dependencies.py", line 1154, in cythonize
      cythonize_one(*args)
    File "C:\Users\CodeWithJoel\AppData\Local\Temp\pip-build-env-aihy54j2\overlay\Lib\site-packages\Cython\Build\Dependencies.py", line 1321, in cythonize_one
      raise CompileError(None, pyx_file)
  Cython.Compiler.Errors.CompileError: av\logging.pyx
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

Hi, thanks for the detailed information. Can you check if you are able to install the previous version?

Yh am able to install the old version but no sound, can I contribute??

Sorry I mistakenly close the issue but can I contribute??

I am running Linux, I would like someone to confirm if the same is happening  @havetc. You are more the welcome to contribute. https://github.com/PaulleDemon/tkVideoPlayer/issues/2.

@oseijoel6111
pip install tkVideoPlayer==2.5 works fine on windows with python 3.10.
It seems that you are trying to build av package instead of downloading it, and that build fails.
Are you on python 3.6 ? It seems that av package version 9.1.1 only has pre-built binaries from version 3.7 to 3.10, I would suggest upgrading python version. Otherwise, you would need to check with the av package team for help with this build error.
@PaulleDemon It's not very nice of you to ask me for help after having ignored some of my messages for months / rejected pull-request confirmed to solve some issues as discussions in #15 showed. Please don't do it anymore.

Hi @havetc I am sorry you felt that way. I was working in a startup and was quite packed during those months. The pull request wasn't rejected the pull request is already merged in with 2.5. If you are talking about #34  Weren't the #28 and #34 doing the same thing?
I am sorry again if I have caused any trouble.

@oseijoel6111 I'll mark this as closed for now. If you have any further problems feel free to ask


geojson rendering wrong

maybe related to #706 some features seem to have a geometry issue.  See this example:

You can see in the tiles behind the correct building footprint.  Seems like its losing nodes but still closing the polygon.

@russbiggs probably it's due to the fact the Mapbox data is not updated. Could you check on OSM which geometry is the most updated?

https://www.openstreetmap.org/way/676681869#map=19/35.08453/-106.62879

This happens in multiple places with similar geometry issues

https://www.openstreetmap.org/way/672520790

@russbiggs I was considering that we are having some problems with the vector tiles generation, but I checked the Albuquerque campaign and noticed problems in the osm file (like isolated nodes that should be part of a building and incomplete buildings geometry). The osm file has 24 MB, but the conversion to geojson generated only one file of 50kb with some nodes missing. So we need to check on the logs what is causing those errors.

Thanks @willemarcel no need to rush on this.  currently want to just identify bugs before we begin new development.  I'll take a look at hte code a bit and let you know if any follow up is needed


Include the browser name when printing unit-test results

This uses a similar format to the reference-test logging, and will help determine in exactly which browser the failure occurred (since the tests run concurrently).

/botio unittest

Interestingly, the failing unit-tests seem to (as I suspected) be limited to Google Chrome on Linux.

I have made #12125 to hopefully improve the situation a bit. I can reproduce the intermittent unit tests failures for Chrome on Linux, but with that patch it seems to be less tests failing and less frequent. We'll see...

I have made #12125 to hopefully improve the situation a bit.

Thanks, fingers crossed that it helps :-)

Anyway, I do believe that this patch is useful regardless since it makes the logs easier to read.

Thanks!


xen: Always map EfiRuntimeServicesCode and EfiRuntimeServicesData

Always map the regions of the subj types despite of the
descriptor attribute field
Signed-off-by: Sergey Temerkhanov<EMAIL_ADDRESS>

I see that there's a pretty good discussion on Xen ML around this -- kudos @temerkhanov -- lets wait for that discussion to conclude and then simply pull whatever patch ends up in Xen itself.
Makes sense @temerkhanov ? Can we close this PR for now (and reopen as a patch backport when it lands in Xen)?

Closing until the patch has been accepted in Xen


mpy API regression?

After successfully building the module due to your fixes in #1, I ran into another issue that took some digging to figure out.
In the latest version of embit, there are a few calls to secp256k1.ec_privkey_add and secp256k1.ec_pubkey_add that can't be resolved anymore. It appears that these functions disappeared at some point in the past few months:
https://github.com/diybitcoinhardware/secp256k1-embedded/blob/690b81679e5046c8046127bd11130f12ffe095d3/mpy/libsecp256k1.c#L532
https://github.com/diybitcoinhardware/secp256k1-embedded/blob/690b81679e5046c8046127bd11130f12ffe095d3/mpy/libsecp256k1.c#L593
I added those functions back and was able to get everything working. Here's a PR to add those back:
https://github.com/diybitcoinhardware/secp256k1-embedded/pull/3

Thank you! I was mostly working and testing zkp branch over the last few months, looks like I broke a few things in the main branch...


Facet sorting

Currently the facets are sorted by "name". Isn't a default sorting by "label" better? The label is displayed to the user and therefore the sorting should be by "label" as well.

A option to define the sorting after the key sort will be added

see http://mpneuried.github.io/iggy/#options


Boosting Query

Knowing that boosting query isn't implemented yet, there is somehow to do this using Plastic and some kind of raw query, without resort on curl or some rest client?
Something like eloquent's DB::raw().

Used (ElasticSearch DSL)[https://github.com/ongr-io/ElasticsearchDSL] and append() method.


Cell config option, only prompt when not defined in ENV

@aluedeke is interested in having a setting where the environment variable behavior is only honored if not already set in the users ENV.

Duplicate of https://github.com/stateful/vscode-runme/issues/643. We will turn this around fairly quickly.


Fix README.md in eslint-plugin-redos

Changes

Fix README.md in eslint-plugin-redos

Codecov Report

Merging #187 (263d7f2) into main (82a5c09) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #187   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           50        50
  Lines         2297      2297
  Branches       110       110
=========================================
  Hits          2297      2297

Continue to review full report at Codecov.

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


The option always appear

the option always appear and always focus to select2 element, even if i click outside of the element.

I think what @fajarlahhh's trying to say is that there's some weird behavior around the focus/opening of the dropdown, I noticed it aswell, at first i thought it was because the new jQuery update (3.4.0), but i'm starting to think its because of the Google Chrome 74 update.
To recreate:
Go to https://select2.org/i18n using Google Chrome 74 on Windows 10.
Click on any of the the demo select2 boxes, the boxes will open and stay open, it's almost impossible to close them.
Please let me know if you need more info or screenshots!

What I think @fajarlahhh is trying to say is that there's some weird behaviour around opening and closing the select2 boxxes since the 4.0.6 update. I noticed is myself aswell and after downgrading back to 4.0.5 it resolved the problem. Tested it in both Google Chrome and Firefox
To recreate

Go to https://select2.org/i18n
Click on any of the select2 boxxes.
Try to close the box (Selecting an option, clicking outside the dropdown)

The dropdown won't close, it's almost impossible to close it.
If you need any further information, please let me know!

Same problem to me, reverting back to 4.0.6-rc1 the behaviour is back to normal

Same problem. Solved temporarily by reverting to 4.0.5

I solved the problem updating to v4.0.7.rc0

Fixed for me with 4.0.7-rc.0, looks like the 4.0.7 is tagged but not available on npm.
https://www.npmjs.com/package/select2

I was on version 4.0.6 and had the issue where the dropdown would not close after selecting an option.
Updating to version 4.0.7 fixed the issue.
For reference, the code in 4.0.6 that was causing the issue was in the function
Select2.prototype._registerEvents.
Specifically, the event handler for "focus".  The code kept dropping into the else block, keeping the dropdown continuously open. Relevant code:
Select2.prototype._registerEvents = function () {
    var self = this;

    this.on('focus', function () {
      self.$container.addClass('select2-container--focus');

      if (!self.$container.hasClass('select2-container--disabled') &&
          !self.isOpen()) {
        if (self.options.get('multiple')) {
          window.setTimeout(function () {
            self.open();
          },
          self.options.get('ajax') ? 300 : 100);
        }
        else {
          self.open();
        }
      }
    });
...
...
...
}

This is fixed in 4.0.7, which was released a bit ago and is now available on all of the repositories (forgot NPM until now).


aws.Service: place ECS tasks in public subnet if cluster VPC has no NATs

Issue: https://github.com/sst/ion/issues/901
What does this do?

Normalizes args.vpc used in aws.Service to have the interface of SST's Vpc component so that more properties are available
If vpc.nodes.natGateways is empty - deploy ECS tasks into public subnet

How was this tested?
Published sst package locally with yalc
Then deployed below example and made sure the public subnets were used
    const vpc = new sst.aws.Vpc("TestClusterVpc", {
      nat: false,
    });
    const cluster = new sst.aws.Cluster("TestECSCluster", { vpc });
    cluster.addService("TestClusterService", {
      image: ".",
      public: {
        ports: [
          { listen: "80/http" },
        ]
      },
    })

Thanks @Dizzzmas!
We just released a new version of Cluster that deploys to the public subnet by default.

@fwang, do existing clusters need to do anything to avoid being deployed to a public subnet since it's the new default?

The component will not auto update. On ur next deploy, it should error with instructions to change sst.aws.Cluster to sst.aws.Cluster.v1 to stay on the previous cluster setup.


Removed set-output warnings in CI

My CI pipelines was showing warnings related to the deprecated use of set-output and set-state, so I wanted to send you a PR to remove those warnings.
It turns out those warnings were generated by @actions/core 1.9.1, and dependabot already upgraded to @actions/core 1.10.0, but you haven't released a new actions-setup-mysql version since.
Anyway, I found some occurrences of the deprecated usage in this repo workflow files (that are unrelated to my initial problem, but still worth fixing ;) )

Thanks!


how to read the performance chart

Do higher numbers mean better performance?
https://github.com/mweststrate/immer#performance
Thanks.

@epikhighs Note that in https://github.com/immerjs/immer#performance the text says:

This test takes 50,000 todo items

That's 50K, whereas in the image it says 500K:

As the code shows, 50K is the right figure (image's wrong):
const MAX = 50000

Please refrain from commenting on closed issues, as typically no one will notice the comment. Please just open a new one


[c++] Improved bounds-detection for Arrow array data

Follow-on from https://github.com/single-cell-data/TileDB-SOMA/pull/968#discussion_r1114656039

Codecov Report
Base: 80.24% // Head: 90.91% // Increases project coverage by +10.66% :tada:

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

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #986       +/-   ##
===========================================
+ Coverage   80.24%   90.91%   +10.66%
===========================================
  Files          72       30       -42
  Lines        3863     2147     -1716
===========================================
- Hits         3100     1952     -1148
+ Misses        763      195      -568

Flag
Coverage Δ

python
90.91% <ø> (-0.05%)
:arrow_down:

r
?

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

Impacted Files
Coverage Δ

apis/python/src/tiledbsoma/_tdb_handles.py
94.08% <0.00%> (-0.54%)
:arrow_down:

R/utils.R

src/include/tiledbsoma/common.h

inst/tiledb/include/tiledb/context.h

src/rutilities.h

src/rinterface.cpp

R/SOMAExperiment.R

inst/tiledb/include/tiledb/stats.h

inst/tiledb/include/tiledb/attribute.h

src/include/tiledbsoma/column_buffer.h

... and 33 more

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

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


Make enabling YourKit easy.

Allow developers and production to enable the YourKit profiler by changing the command to run. By default we don’t start with the profiling agent enabled so that we don’t accidentally create performance issues.

No jira as it's not really testable and isn't something that is related to Sakai.


Title: Loading Animation

Initiative (Required)
GSSoC (Girl Script Summer of Code) 🌸
Is your feature request related to a problem? Please describe.
YES
Describe the solution you'd like.
There should be Loading Animation for better user experience...
Add any other context or screenshots about the feature request here.
No response

@Kushal997-das Can i do this ??


feat(vertexai): add name constructor for function calling schema

Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (melos run analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

@cynthiajoan - We've just merged a PR that will automatically update the version_version.dart when we publish new vertexai versions. So there's a merge conflict I'm afraid 😓. Also analyse and format CI needs fixing. Other than that, LGTM.

resolved the version


Update blaze to use the Spark DataFrame API

will need to merge the odo PR first https://github.com/ContinuumIO/odo/pull/117

needs this PR first:
https://github.com/ContinuumIO/odo/pull/139

@mrocklin any comments?


Missing documentation to set up source maps for debugging

Repost since a ticket can't be moved from repo to repo. See: https://github.com/angular/angular/issues/18389

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[x ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
See https://stackoverflow.com/questions/45314808/angulars-zone-js-hates-raphaeljs
People suggest that I should look into compiled code but that isn't possible due the incorrect / absent source maps.
At angular.io I can't find any info how to set those up.
Expected behavior
Please cover in the docs how to setup & maintain source maps

Minimal reproduction of the problem with instructions
https://encrypted.google.com/search?hl=nl&q=how+to+set+up+source+maps+site%3Aangular.io&oq=how+to+set+up+source+maps+site%3Aangular.io
https://duckduckgo.com/?q=how+to+set+up+source+maps+site%3Aangular.io&ia=web
What is the motivation / use case for changing the behavior?
Well, imine at StackOverflow for example.
Environment

Angular version: 4.3.1

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
- [X] Pale Moon: 27.4.0

For Tooling issues:
- Node version: v8.2.1
- Platform:  Linux

Source maps should be working for dev and test as of release 1.3.0.

Heya, you can control whether sourcemaps are generated via the --sourcemap flag. It is documented in the page for the build command: https://github.com/angular/angular-cli/wiki/build. By default they are on in turned on in dev builds, and off in prod builds (but you can turn them on there as well).


Which version of python does this repo use is it multiple or is it one???

I believe different projects written at different times may have different requirements. I'd suggest to go with the most recent Python3.11
That should make you able to run almost all the projects (bare speculation).

above 3.x

Python version doesn't matter as long as the required dependencies are included in requirements.txt and README.md file


feat: allow restore backup to different instance

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕

@googlebot


feat(changelog): make changelog.header a template

Made changelog.header into a template like changelog.body and changelog.footer. Added test test-header-template.
Description
Implement #697.
Motivation and Context
Create parity between changelog.header, changelog.body and changelog.footer.
How Has This Been Tested?

Added new test fixture "test-header-template".

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Documentation (no code change)
[ ] Refactor (refactoring production code)
[ ] Other

Checklist:

[X] My code follows the code style of this project.
[X] I have updated the documentation accordingly.
[X] I have formatted the code with rustfmt.
[ ] I checked the lints with clippy.
[X] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Hi @orhun,
functionally this is a very small change. I was able to copy the logic from the body and footer template processing 1-to-1. However, I do fear that we will have to flag this as a breaking change regardless. All of the tests and examples contain explicit \n in the header. These are now obsolete. Without removing them, we would end up with an extra empty line between the header and the first release.

I am  not quite sure what to do about the allegedly wrong formatting in changelog.rs. When I run cargo fmt locally, it formats the code the way it is in this PR. I don't know why the pipeline demands it to be formatted differently. See https://github.com/orhun/git-cliff/actions/runs/9518131251/job/26238303168?pr=698
Similarly I am having trouble figuring out why the test suite fails: https://github.com/orhun/git-cliff/actions/runs/9518131251/job/26238304948?pr=698
Actual and expected look identical to me.

And this is another problem: https://github.com/orhun/git-cliff/actions/runs/9518517603/job/26239610418?pr=698#step:3:842
I have no idea why the template behaves differently in test-header-template compared to test-footer-template. They are identical, but in test-header-template there is indentation, in test-footer-template there is not. I am done for today, maybe someone else could take a look into this.

Codecov Report
Attention: Patch coverage is 69.23077% with 4 lines in your changes missing coverage. Please review.

Project coverage is 37.19%. Comparing base (eac2195) to head (4033895).

Files
Patch %
Lines

git-cliff-core/src/changelog.rs
69.24%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #698      +/-   ##
==========================================
+ Coverage   36.89%   37.19%   +0.30%
==========================================
  Files          18       18
  Lines        1350     1358       +8
==========================================
+ Hits          498      505       +7
- Misses        852      853       +1

Flag
Coverage Δ

unit-tests
37.19% <69.24%> (+0.30%)
:arrow_up:

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

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

Can you resolve the conflicts? 😊

I've fixed the tests and added the minimalist documentation update. How do we deal with the formatting? I cannot get my local rustfmt to format the code the way the pipeline wants it to be.

I've fixed the tests and added the minimalist documentation update. How do we deal with the formatting? I cannot get my local rustfmt to format the code the way the pipeline wants it to be.

Thanks! The formatting is already fixed in main, so if you merge those changes it will be fine I think.
I can also handle it before merging the PR, no biggie.

I've fixed the tests and added the minimalist documentation update. How do we deal with the formatting? I cannot get my local rustfmt to format the code the way the pipeline wants it to be.

Thanks! The formatting is already fixed in main, so if you merge those changes it will be fine I think.
I can also handle it before merging the PR, no biggie.

I've tried improving the documentation by specifying the context of each template. Is this okay?

LGTM, thank you!
One thing that crossed my mind is that --prepend won't work as expected now when there are template variables in the header. It used to work like:
1- Read the contents from existing changelog file. 2- Replace the header in the file with the new changelog entries.
Now that the header is not a raw string & is not rendered, we won't be able to perform the replace properly.
Are you interested in fixing this as well? I think we only need to render header before replacing it in the file. I would really appreciate if you can test this case and create an issue!

I was not aware of this feature. I created a bug issue to deal with that: #712


Wrong version of libraries in nuget package

I'm encountering with #31 again. So, it is figured out that 0.3.1 libraries have installed with 0.3.3 version nuget-package (Tested both in VS2013 and VS2015).

Could you pls check nuget package?

Workaround: downgrading to 0.3.2 nuget-package

Great find!
I will remove that version from nuget once 0.3.4 is out.

0.3.4 was added and 0.3.3 removed.


Message duplication causes orchestrator messages dead-letter

Orchestrator has logic that clones messages and re-enqueues them so that we can try a message more than the maximum attempts set on the subscription (20). In short, orchestrator does this:

Gets a message.
Process the message.
If the validation set is not done, re-enqueue
Complete the message.

If the "complete the message" step fails, that means there are now two messages for the one validation set. When the validation set finally completes, one message "wins" by copying the package from to the public container. The other message "loses" because it can't copy the package from the validation set location to the public container because the first message deleted the validation set copy.
This causes dead-lettering.
This issue is a continuation of https://github.com/NuGet/NuGetGallery/issues/6515.
In my on-call week I had 34+ dead-letter messages.

traces
| where cloud_RoleName == "NuGet.Services.Validation.Orchestrator"
| extend CallGuid = tostring(customDimensions.CallGuid)
| summarize max(timestamp), min(timestamp) by CallGuid
| extend Duration = (max_timestamp  - min_timestamp)/1s
| join (
  exceptions
  | where cloud_RoleName == "NuGet.Services.Validation.Orchestrator"
  | where outerMessage contains "The lock supplied is invalid. Either the lock expired, or the message has already been removed from the queue."
  | extend CallGuid = tostring(customDimensions.CallGuid)
  | project CallGuid
) on CallGuid
| join (
  traces
  | where cloud_RoleName == "NuGet.Services.Validation.Orchestrator"
  | extend CallGuid = tostring(customDimensions.CallGuid)
  | extend ValidationSetId = tostring(customDimensions.ValidationSetId)
  | where ValidationSetId <> ""
  | summarize any(ValidationSetId) by CallGuid
  | extend ValidationSetId = any_ValidationSetId
  | project ValidationSetId, CallGuid
) on CallGuid
| join (
  traces
  | where cloud_RoleName == "NuGet.Services.Validation.Orchestrator"
  | where message contains "Before calling FetchAttributesAsync(), the source blob 'validation-sets/"
  | extend ValidationSetId = tostring(customDimensions.ValidationSetId)
  | summarize count() by ValidationSetId
  | extend CopyFailures = count_
) on ValidationSetId
| project ValidationSetId, CallGuid, Duration, CopyFailures

There is a concern that the solution could make a validation set "stuck". Say a package takes 30 minutes to download, no matter what. If all 20 deliveries of the messages hit the 30 minute download, all deliveries will not send a follow-up message, and the validation set will be "stuck". In other words, the solution would make a validation set "stuck" if all deliveries of a message exceed the lock duration.
I crunched some numbers on PROD. In the last week:

911 validation sets had 1 message take longer than 1 minute to process
21 validation sets had 2 messages take longer than 1 minute to process
0 validation sets had 3 or more messages take longer than 1 minute to process

From the data, there is no concern for validation sets getting "stuck" after the change. Here is the query I ran:
traces
| where cloud_RoleName == "NuGet.Services.Validation.Orchestrator"
| extend CallGuid = tostring(customDimensions.CallGuid)
| extend ValidationSetId = tostring(customDimensions.ValidationSetId)
| where CallGuid <> ""
| summarize max(timestamp), min(timestamp), max(ValidationSetId) by CallGuid
| extend DurationSeconds = (max_timestamp  - min_timestamp)/1s
| where DurationSeconds >= 60
| extend ValidationSetId = max_ValidationSetId
| project ValidationSetId, DurationSeconds, CallGuid
| summarize count() by ValidationSetId
| order by count_ desc

Only 2 validation sets in the past week

Orchestrator does not seem to set ServicePointManager.DefaultConnectionLimit

[ ] Improve message duration + lock expiration telemetry: https://github.com/NuGet/ServerCommon/pull/230, https://github.com/NuGet/NuGet.Jobs/pull/678
[ ] Increase the connection limit in the Orchestrator: https://github.com/NuGet/NuGet.Jobs/pull/677
[ ] Improve the package backup telemetry

@agr should we keep this open until we’ve verified there’s no more dead lettering? I would wait a few days and maybe run functional tests on PROD.


bootstrap Layout for widget orchard core

How to add layout options like 20 %  in widget container i am new in orchard core can any one help me to resolve this issue.

You can see in this image with marked in which i want 20 % as option .

Wrong repository, can you file it in OrchardCore?
But duplicate of https://github.com/OrchardCMS/OrchardCore/issues/6453


Are writes ordered?

I see that we are using napi_create_async_work. However, I can't read anywhere whether or not work items are guaranteed to be executed in order or not. If not then we might have a problem with write ordering, i.e. preceding writes overwriting following writes.
Do we need to create our own per db ordered work queue?

Writes are not ordered (at least by design, and I doubt that napi_create_async_work is ordered, seeing as its purpose is parallel work). For the majority of users that's perfectly fine. Introducing a work queue would be a major change, and quite complicated, so I want to see many upvotes before considering it. Until then it can be handled in userland, where you have a choice of doing things in parallel or sequentially.

I think we might need to add a clear warning for this. I for one assumed that they would be ordered.

That would be good. PR welcome.


postgres database attach missing

When creating a database, if the postgres attach step is not instantaneous, it now apparently fails
This means that the application will have an H2 database that will disappear with a container restart -- losing the data.

For some reason, having the application listen on all interfaces seems to fix this.


Update some contributions documentations

Even though #14756 is not closed yet — but we're getting closed 🐧 — I think we should mention somewhere in the contributing docs that the modified file should pass the golint door :stuck_out_tongue_closed_eyes:.
This currently adds a golint entry to coding-style.md but I was wondering something : we do not talk about make validate on the contributing docs although it does most of the thing we're asking for a PR (validate-dco, validate-gofmt, validate-lint, validate-toml, validate-vet).
To explain this further, one of the workflow I use when working on docker is the following (if it's a code one, not a doc one :yum:) :

create my branch, doing my changes
make test : well make test-unit or make test-integration-cli depending on where it's needed but in the end, make test.
make validate so I'm sure everything is all right (gofmt, golint, etc..)
and then I can push and PR

I'm not sure where to put it though — maybe in docs/project/work-issue.md (updating it to use make commands) or maybe in docs/project/test-and-docs.md (but feels a little out of context there). 🐸
/cc @thaJeztah @moxiegirl wdyt ?
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

Hm docs/project/test-and-docs.md (Below "Run tests on your local host") sounds good to me.
@moxiegirl agree?

@vdemeester a nice addition to the coding-style-guide.md.  golinit is also mentioned here: https://github.com/docker/docker/blob/master/CONTRIBUTING.md
@thaJeztah docs/project/test-and-docs.md is really about creating new and running existing tests as part of development. It might not be explaining that well, which is another topic. :-D
@vdemeester Your workflow is addressing good practice before a PR. I agree with your assessment the right place is here docs/project/work-issue.md.  We really need two articles one for "workflow for docs PR" and "workflow for code PR." However, if you see a way to update the existing article, I think that is great task and I'd appreciate the help.
For this change LGTM.

@calavera Cherry pick please.

@moxiegirl ok, I'll look for a way to update work-issue.md and work on /workflow for PR (code & docs)then :wink:. I'll also take a look attest-and-docs.md`` to update it with the current way it's done (for integration-cli and unit tests) and also with the ideas from #7010 :wink:.

do we really need this in the release docs? It looks like it's just project related, not specific to the release.

@calavera as a courtesy to the contributor, I would include it.  The alternative is to wait X months/weeks for the next release.  Your call of course.

oh wait, so if it's not on the release it won't show up in docs.docker.com until the next release? I'll merge it if that's the case.

@calavera yup, that's the point :-)

cool, cheery picked into #15091

@calavera Between release, I do updates but only for significant fixes.  This would not be considered at that level.


ERR: Error stat()ing when dealing with a rebase with conflicts

 λ Sites/test ERR: Error stat()ing: files/test.jsx
ERR: Error opening directory  files/test.jsx: No such file or directory

 λ Sites/test                                                                                8s  ⇡ 2675b08b ◆ :: 2d :: ⬡

When I do git pull --rebase origin master, and incur conflicts, this will be printed in the console after each command is ran. ls, cd and what not.
Is this related to geometry?

It does seems like a custom error from somewhere else. I'll take a further look later today.
Thanks for reporting.

Cheers, I am going to comb through my setup later to see if I can identify anything that would conflict. I run a pretty light setup so I thought I'd start here at least.

Oh. I think I know what this is. It's when you have conflicts in a file and in that same commit some other file was removed. It tries to open all changed files in that commit to count the conflicts.
I can tackle this later today.

This happens during a conflict on a non top-level directory due to git diff --name-only --diff-filter=U in prompt_geometry_git_conflicts.


parsing map_data/state_regions

Someone I pointed your way for a convenient vic3 parser on discord came back that they couldn't find port/farm/etc province data, so I made a quick function to grab that data.
Other than simply taking the keys as they were initially parsed, it takes all capped/discoverable resources as independent entries with an amount and a depleted_type, and all entries it could not find are simply empty string.

I'm sorry, but I didn't see your pull request earlier. My email-notifications were broken.
Resources are already in the resources attribute of the states(parsed via _get_state_resources).
What Chevron9 wrote would be the best way to parse the rest of the data. I skipped these, because I didn't think they were useful, because they don't have any gameplay impact(except impassable).
You can also reach me on discord as grotaclas#2315. I'm on the official vic3 and paradox discords and on the victoria 3 mod co-op discord.


Consistent handling of trailing slash in auth domain

Currently, the app private key returned from browser.blockstack.org varies if BlockstackConfig was built with an auth domain that has a trailing slash or not.
This is confusing and should be either documented or handled consistently with the web.

fixed by #177


Add Types!

Mypy complains and I have to silence it like this (which is not ideal).
from multiformats_cid import from_bytes  # type: ignore

If the project is already typed, then it should be as easy as adding an empty file called py.typed to the base module.
and adding this to setup configuration:
[options.package_data]
cid = py.typed

It appears I posted the issue in the wrong place:
https://github.com/multiformats/cid/issues/56

Hi @bh2smith. I recently forked ipld/py-cid and fixed the issues with the python requirements, wasn't aware of this problem, i'll post a fix asap, thank you.

Following your recommendation, i've updated the setup.cfg file, tested it with mypy, and indeed the errors go away. Published v0.4.2 to pypi. Thanks !

This is great news, however it is not quite right:
Successfully installed py-multiformats-cid-0.4.2

$ mypy pysrc --strict

fetch/ipfs.py:7: error: Skipping analyzing "multiformats_cid": module is installed, but missing library stubs or py.typed marker
fetch/ipfs.py:7: note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports

You actually need to create an empty file called py.typed
based on your previous commit https://github.com/pinnaculum/py-multiformats-cid/commit/547ad4f4c60847aa032d4d388391e5f295d8c785, It looks like the only thing left to do is add the file.
$ touch multiformats_cid/py.typed

@bh2smith Thank you so much for this, the typing really improves the module a lot. Reviewing your PR now, will merge it and list you in the contributors. I'll also add a CI workflow to run the unit tests and will publish to pypi after that.

@bh2smith Thank you so much for this, the typing really improves the module a lot. Reviewing your PR now, will merge it and list you in the contributors. I'll also add a CI workflow to run the unit tests and will publish to pypi after that.

Another thing that could be cool to do is auto publish on tagged releases. I could link you to an example of how I do it in a few projects.

@bh2smith Thank you so much for this, the typing really improves the module a lot. Reviewing your PR now, will merge it and list you in the contributors. I'll also add a CI workflow to run the unit tests and will publish to pypi after that.

Another thing that could be cool to do is auto publish on tagged releases. I could link you to an example of how I do it in a few projects.

Merged your PR. Yeah the auto-publish with twine is no problem, just reused a workflow i had, will be ready soon.

Question: is the from future import annotations import strictly necessary ? This breaks support for python 3.6.

Question: is the from future import annotations import strictly necessary ? This breaks support for python 3.6, but that's probably an acceptable choice.

Yes actually this implementation as is will only work for >= 3.8
It can be adjusted to also work with 3.7, but I can't go as far back as 3.6
See here
https://github.com/pinnaculum/py-multiformats-cid/pull/2#issuecomment-1320875232

Ok, will merge #3 then cause 3.7 can't be considered a dinosaur yet. Published v0.4.3 to pypi.


[VL] Register Spark tokenizer

What changes were proposed in this pull request?
To fix affected unit tests in https://github.com/oap-project/velox, register Spark tokenizer instead of changing Velox one.
Depends on: https://github.com/oap-project/velox/pull/444.
How was this patch tested?
under test

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_3810_time.csv
log/native_master_11_23_2023_df3eb372c_time.csv
difference
percentage

q1
34.69
34.09
-0.599
98.27%

q2
24.88
24.43
-0.453
98.18%

q3
37.69
37.11
-0.577
98.47%

q4
37.42
35.49
-1.932
94.84%

q5
70.32
70.74
0.425
100.60%

q6
7.11
6.77
-0.337
95.25%

q7
83.59
85.18
1.593
101.91%

q8
86.77
84.73
-2.038
97.65%

q9
125.47
118.73
-6.734
94.63%

q10
45.41
43.59
-1.816
96.00%

q11
19.27
19.61
0.344
101.79%

q12
25.41
23.77
-1.641
93.54%

q13
46.19
45.78
-0.412
99.11%

q14
16.59
17.52
0.929
105.60%

q15
28.46
28.14
-0.327
98.85%

q16
15.78
15.14
-0.636
95.97%

q17
102.98
100.38
-2.593
97.48%

q18
147.63
147.08
-0.559
99.62%

q19
12.94
12.95
0.018
100.14%

q20
27.95
28.07
0.120
100.43%

q21
218.99
218.99
0.008
100.00%

q22
12.87
12.93
0.063
100.49%

total
1228.38
1211.23
-17.152
98.60%


Cannot add a registry with basic auth from Azure Registry service

Hi,
I cannot seem to manage a registry which is hosted on Azure Containers Registry services.
It is a docker registry running on port 443 and I authenticate it using the MANAGER_REPOSITORIES variable.
	- MANAGER_REGISTRIES='https://username:password@myregistry.azurecr.io:443'

I get the error Failed to parse registry from the passed url., but I guess it is related
to the fact that Azure is controlling the password field and that when they generate a
password they use special characters such as \=%$/ etc.
Would you have an idea how to authenticate using that kind of characters in the basic auth password schema?
Is there a way to escape special characters?
Regards
Dominick

Hey Dominick,
This seems like it would only be an issue with commas or post pound signs, I'll take a look at this tonight and figure out a solution/workaround

Thanks, let me know if you need me to test a branch if you come up with a solution.
Dominick

Hey Dominick,
Go ahead and give this a try in the develop branch:

If running from the git checked out dir, add your registry in the config.yml file then export MANAGER_REGISTRIES_CONFIG=`pwd`/config.yml  then run normal via go run
If running via docker compose, set the image to develop image: snagles/docker-registry-manager:develop  and then uncomment the MANAGER_REGISTRIES_CONFIG=/opt/config.yml  line

it works fine. Thanks

Glad to hear it, I'll clean it up a bit, merge it to master, and then close this out.


Config-based machine disabling

Add a section to the config file that allows the user to enable or disable certain machines.

Server-sided, syncs with clients
Can be maintained in a root TE class, like TileEntityBasicBlock - will destroy the existing block if it is disabled in config
Recipes will be removed and blocks will be hidden from creative mode
Hopefully can integrate with NEI

This is now done.


Use latest version of docker-compose for testing

Thanks, @albertyw 🎉
Sorry, it's taken so long to look at these! We are going to hopefully have some time to review all your PR's in the upcoming week.


Print "Downloading <item_name>" fails on Unicode character

See PrintFails.
Traceback (most recent call last):
  File ".\mycoursesdownloader.py", line 262, in <module>
    print("   Downloading " + dropbox_item_name)
  File "C:\Python33\lib\encodings\cp437.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u2013' in position 40: character maps to <undefined>

Perhaps use str.encode? Reference.

Just pushed a fix. I had a function to strip unicode, but it was not being run on the print statements. Now it is.

:+1: Thanks, dude!


I want to know how long training takes when using 4 12G NVIDIA 3090 GPUs as paper mention.

Hello, what a great job！When I use 3 NVIDIA 3090 GPUs for training, it takes more than 4 hours to train one epoch. Is this normal? So I wonder how long does training take when using 4 12G NVIDIA 3090 GPUs as paper mention.

Thank you for your enthusiasm for our work!
The training duration you mentioned is much longer than expected. In our training cases, it typically takes a little less than 1 day to train on SemanticKITTI, and ~1.2 d to train on SSCBench-KITTI-360. For more details, you can check the provided logs in the README.

Perhaps you could examine the GPU utilization rates and the time costs for each module to identify whether the potential bottlenecks lie in disk I/O or any specific module.
BTW, I recall there were some compatibility issues in the latest Lightning update regarding Distributed Data Parallel (DDP). Training on a single GPU without DDP can help diagnose whether the issue is related to DDP.

Thank you very much for your answer, I found that I was using a dataset that included every frame of data, which was 5 times larger than the original dataset. It does take just over 1 day to train using the original dataset.


LDAP server env variable should accept multiple servers

Describe the feature you'd like
I would like the LDAP_SERVER variable in .env file to accept multiple servers, as in environments with HA LDAP servers it should be supported in app too.
Describe the benefits this would bring to existing BookStack users
This would bring HA support, so if one of the LDAP servers are unreacheable, it could use the 2nd one and not fail.
Can the goal of this request already be achieved via other means?
Not to my knowledge.
Have you searched for an existing open/closed issue?

[X] I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?
0 to 6 months
Additional context
LDAP_SERVER=ipa1.redacted.fi,ipa2.redacted.fi
This happens with two LDAP servers set in .env file:

Thanks for raising @samip5,
I think this may already be covered by #543? Although that's specific to AD, it's still LDAP so would be the same fundamental feature request I think.

Ah, yeah seems to be. Let me close this and go put my screenshot of the current state there. :)

+1 for this one

+1 for this one


Instance override issue when launching a worker group launch template per az

Launch templates with mixed policies fail when re-using instance type .
I'm submitting a

[ ] bug report
[ ] feature request
[x] support request
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
I'm trying to create two worker_groups with launch templates one per availability zone. The groups are created and I can see them in the console, however this TF module is reporting an issue when overriding:

aws_autoscaling_group.workers_launch_template.1: Error creating AutoScaling Group: ValidationError: Cannot add same instance type override more than once. Remove these duplicates from the request and try again: [t3.large]
status code: 400, request id: xxxx

module.eks.module.eks.aws_autoscaling_group.workers_launch_template[0]: 1 error(s) occurred:

aws_autoscaling_group.workers_launch_template.0: Error creating AutoScaling Group: ValidationError: Cannot add same instance type override more than once. Remove these duplicates from the request and try again: [t3.large]
status code: 400, request id: yyy

If this is a bug, how to reproduce? Please include a code sample if relevant.
I'm using the following configuration to test spot fleet creation:
worker_group_launch_template_count = "2"
worker_groups_launch_template = [
{
spot_instance_pools = 3
asg_desired_capacity = 2
on_demand_base_capacity = 0
on_demand_percentage_above_base_capacity = 0
autoscaling_enabled = 1
key_name = "${var.key_name}"
instance_type = "t3.large"
name = "t3large-1a"
kubelet_extra_args = "--node-labels=spot=true --node-labels=role=t3large-1,env=k8s-env,stack=k8s-env,az=a,node-role.kubernetes.io/t3large-1=true,node-role.kubernetes.io/t3large-1a=true"
subnets = "${data.aws_subnet.private_subnet_a.id}"
},
{
spot_instance_pools = 3
asg_desired_capacity = 2
on_demand_base_capacity = 0
on_demand_percentage_above_base_capacity = 0
autoscaling_enabled = 1
key_name = "${var.key_name}"
instance_type = "t3.large"
name = "t3large-1b"
kubelet_extra_args = "--node-labels=spot=true --node-labels=role=t3large-1,env=k8s-env,stack=k8s-env,az=b,node-role.kubernetes.io/t3large-1=true,node-role.kubernetes.io/t3large-1b=true"      subnets = "${data.aws_subnet.private_subnet_b.id}"
}
]
What's the expected behavior?
Have two templates with same instance size, one for az=a and one for az=b
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details

Affected module version: 3.0.0
OS:
Terraform version: v0.11.13

Any other relevant info

The problem is here:
https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/local.tf#L55
https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/workers_launch_template.tf#L33
Currently the code applies 2 instance overrides to the ASG, the second of which defaults to t3.large.
So for you, you would need to choose a second instance type as instance_type and you could end up with a mix of both instance types in the ASG. There's no other way unfortunately. You can't set either to "" as terraform will apply on every run: https://github.com/terraform-providers/terraform-provider-aws/issues/8475

I think the changes we should make in this module are:

Remove the overrides and just use instance type from LT.
Provide a second worker_group option with 5 instance type overrides for people who are using spot instances.

But would be nice to hear other people's opinions 🙂

I got it running as I wanted, I only had to remove instance_type override from my config and that defaults to t3.large.
However, I kind of see this as a bug. That second override in the code should not happen if instance_type override matches local.

However, I kind of see this as a bug. That second override in the code should not happen if instance_type override matches local.

I don't think this is possible in Terraform currently because it requires conditionally setting an override block on the ASG.

Should all be resolved in latest release 🙂


feat: add C implementation for stats/base/dists/bernoulli/pmf

Resolves #3418
Description

What is the purpose of this pull request?

This pull request:

adds C implementation for stats/base/dists/bernoulli/pmf

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #3418

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines

@stdlib-js/reviewers

/stdlib update-copyright-years


Test out HTTP 2 support from libcurl

libcurl can do some stuff for HTTP/2 and we should enable it. This is a reminder :)

I tested it and it didn't have much of an impact on the anaconda.org repos. I think they'd need to activate HTTP/2

Just wondering if it might be useful for quetz if the server there is HTTP/2?
I've been thinking of enabling HTTP/2 for our internal repo server but never got around to it. Now I'm planning to move to quetz! 😃


MacVim defaults clean up and modernization

Just a general issue for improving the defaults for what I consider to be what constitutes a modern GUI text editor. Changing defaults is always contentious, and therefore should require a bit of thoughts behind them. None of the proposed defaults below change any features and they would just require either a vimrc change or changing them in the user settings. Just listing them below to keep track of and to gather feedbacks:

Smooth resizing defaults to on (#1276)
set guioption+=k
set macligatures
MMShareFindPboard should be NO.
Overlay scroll bar (once implemented)
set guifont=-monospace-

Update: I have made a comment for each of the new option in case people want to vote on them using emoji reactions. (Per suggested by a comment)

I'm here because the release notes asked for feedback. Maybe it makes sense to have one comment per bullet point, so that people can thumbs-up and thums-down each item?

No real opinion on smooth resizing (I have it on; having it on is probably a nicer default)
No strong opinion on k
No opinion on macligatures either. I don't use a font with coding ligatures, so it won't affect me. People who do use fonts with ligatures would probably prefer if those just worked, so it makes sense to me from a distance.
Disagree on MMShareFindPboard being NO. A shared find pasteboard across apps is a macOS thing, and integrating MacVim with that seems like a good thing to do by default
Depends on how good the overlay scroll bar impl is, but if it's good then that sounds good (as long as it honors the OS-wide pref for this)
In favor of using -monospace- by default!

Maybe it makes sense to have one comment per bullet point, so that people can thumbs-up and thums-down each item?

That's not a bad idea. I'll do that. I wish there's a better way to do this in GitHub.

No opinion on macligatures either. I don't use a font with coding ligatures, so it won't affect me. People who do use fonts with ligatures would probably prefer if those just worked, so it makes sense to me from a distance.

Yes that's the main reason for turning it on. The main reason it's not on right now is that the renderer is less efficient when ligatures is on, so I'll be investigating this only after hardware-accelerated renderer is implemented and see if the improved renderer can make sure to have good default and worst case performance before switching defaults over. E.g. some terminals like iTerm2 don't even support hardware accelerated ligatures.

Disagree on MMShareFindPboard being NO. A shared find pasteboard across apps is a macOS thing, and integrating MacVim with that seems like a good thing to do by default

I think my annoyance with this is that a lot of search terms we do is that most search commands I do in Vim are oddball regex that don't translate to other programs, but maybe I never really bought in to this part of the Mac philosophy. But it's good to hear a dissenting view here. I should at least expose it as a graphical user-visible setting. (FWIW Cmd-E/Cmd-G in MacVim are hard-coded to use the system shared find pasteboard no matter what, and it ignores MMShareFindPboard)

New default:

Smooth resizing defaults to on (#1276)

New default:

set guioption+=k

New default:

set macligatures

New default:

MMShareFindPboard should be NO.

New default:

Overlay scroll bar (once implemented)

New default:

set guifont=-monospace-

New default:

MMShareFindPboard should be NO.

I downvoted.
I don't feel too strongly about it either way.
Agreed that the regex searches we often use aren't useful to other apps - but they could be in the future.
Unless it being on by default is a pain point for people, we should just stick to the Mac paradigm. I've been a MacVim user for ~15 years and I never noticed that behavior, so it's prolly not bothering most people.
I think your suggestion of leaving it on (YES) but exposing it as a GUI setting sounds great.

set guifont=-monospace-
Yes. Please.

set guioption+=k

This would make the window not change size when you add a new tab, scroll bar, and toolbar. Without this setting, adding/removing those will try to resize the GUI window to preserve same number of lines, which could be jarring for the user and unlike how most other text editors work. Setting the option makes it work more like in full-screen, where it will change the number of lines to preserve the GUI window size so the window stays stable.

MMShareFindPboard

It makes it so that all the search you do (e.g. using /) will be shared to macOS's find pasteboard. Then means you can search for something in Vim, then do Cmd-G in another app (e.g. Safari) and it will just work. The primary reason I don't like this is that a lot of times Vim searches are complicated regex patterns that may not make sense in other text editors. But from other people's reactions I'm easing on that.

Also, I downvoted ligatures because I assume that would mean that things like => would be rendered automatically as a ligature, and I think that would be jarring to me and others editing code as I've never experienced that behavior in the editors that I've used over the years (granted, most of those have been terminal-based, so it's more due to lack of ligatures in terminals, but I think I would find it annoying enough to search for a way to disable it).

=> will only be turned into a ligature if your font supports it, which I would guess your font does not. I actually don't know if there's any font ligature at all in the default monospace fonts provided by Apple. Usually people have to install custom fonts like Fira Code in order to get ligatures.
But it's a fair point that a renderer isn't obligated to support ligatures, and the default should probably be more minimal, as people who care about ligatures can just turn it on.


gzdoom: 3.1.0 -> 3.2.5

Semi-automatic update. These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 3.2.5 with grep in /nix/store/m0ms0fpwwi306zq5as89r1kb40bhba8n-gzdoom-3.2.5
found 3.2.5 in filename of file in /nix/store/m0ms0fpwwi306zq5as89r1kb40bhba8n-gzdoom-3.2.5

cc @Lassulus

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘gzdoom-3.2.5’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/games/gzdoom/default.nix:44 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Partial log (click to expand)
/build/source/build/gzdoom.pk3 contains 671 files (updated 671)
[100%] Built target gzdoom_pk3
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/pp4k92g17akg4gzkrmlx0qfsswax7046-gzdoom-3.2.5
shrinking /nix/store/pp4k92g17akg4gzkrmlx0qfsswax7046-gzdoom-3.2.5/lib/gzdoom/gzdoom
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/pp4k92g17akg4gzkrmlx0qfsswax7046-gzdoom-3.2.5/lib  /nix/store/pp4k92g17akg4gzkrmlx0qfsswax7046-gzdoom-3.2.5/bin
patching script interpreter paths in /nix/store/pp4k92g17akg4gzkrmlx0qfsswax7046-gzdoom-3.2.5
checking for references to /build in /nix/store/pp4k92g17akg4gzkrmlx0qfsswax7046-gzdoom-3.2.5...

Success on x86_64-linux (full log)
Partial log (click to expand)
/tmp/nix-build-gzdoom-3.2.5.drv-0/source/build/zd_extra.pk3 contains 135 files (updated 135)
[100%] Built target zd_extra_pk3
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/m0ms0fpwwi306zq5as89r1kb40bhba8n-gzdoom-3.2.5
shrinking /nix/store/m0ms0fpwwi306zq5as89r1kb40bhba8n-gzdoom-3.2.5/lib/gzdoom/gzdoom
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/m0ms0fpwwi306zq5as89r1kb40bhba8n-gzdoom-3.2.5/lib  /nix/store/m0ms0fpwwi306zq5as89r1kb40bhba8n-gzdoom-3.2.5/bin
patching script interpreter paths in /nix/store/m0ms0fpwwi306zq5as89r1kb40bhba8n-gzdoom-3.2.5
checking for references to /tmp/nix-build-gzdoom-3.2.5.drv-0 in /nix/store/m0ms0fpwwi306zq5as89r1kb40bhba8n-gzdoom-3.2.5...


Scope error in migrate-repo during CreateMigrationSource call

Description
I'm getting a scope permission error during a call the GetMigrationSource, and either the error message is misleading or there's a problem I can't see.
[4:40 PM] [DEBUG] RESPONSE (OK): {"data":{"createMigrationSource":null},"errors":[{"type":"FORBIDDEN","path":["createMigrationSource"],"locations":[{"line":1,"column":109}],"message":"rbanks54 does not have the correct permissions to execute `CreateMigrationSource` query. It requires the following scopes: ['read:org', 'repo'], but the token has only been granted the: ['read:org', 'repo'] scopes. Please modify your token's scopes at: https://github.com/settings/tokens."}]}

The token needs ['read:org', 'repo'], and has ['read:org', 'repo'], yet an error is thrown.
Reproduction Steps

> gh --version
gh version 2.17.0 (2022-10-04)
> gh ado2gh --version
[4:46 PM] [INFO] You are running the latest version of the ado2gh CLI [v0.29]
0.29

Set the ADO_PAT, and GH_PAT environment variables
execute gh ado2gh migrate-repo --ado-org "<AzDO>" --ado-team-project "<PROJ>" --ado-repo "<AzDO-Repo>" --github-org "<GH>" --github-repo "<GH-Repo>" --wait --verbose

Note: I can work around this by giving the token all org permissions, as well as the workflow permission (needed later in the process).

@rbanks54 Thanks for reaching out! The error message coming from the API is a bit confusing - we're working on that now. Do you have SSO enabled on the destination organization? Are you an owner of that organization, or did someone grant you the migrator role?

The fact that adding all scopes fixed the problem suggests to me that it is in fact a scope problem. @rbanks54 are you able to file a support ticket? that way somebody on our on-call team will dig into what's going on.

@dylan-smith You might be right actually - I wasn't sure that "all org permissions" meant scopes, but on re-reading, that makes sense (tell us if we're wrong @rbanks54!).

Yes, all org permissions meant all the org scopes. 🙂

@timrogers yes, I've got SSO enabled, with tokens authorised, and I've got full permissions to both AzDO and GH.

Thanks @rbanks54 🤝 If you could file a support ticket, that would be great. Sure we can take a look and figure out what's going on here.

Closing this in favor of https://github.com/github/migration-friction/issues/762 for tracking.

⏫  FYI to any readers, this is now being handled as a support ticket since it doesn't appear to be an issue with the CLI specifically


Roadmap?

Hi there!
Can you share a roadmap of the releases? When do you plan to come out of alpha?
Will media3 eventually supersede exoplayer?

We can't share a concrete roadmap yet I'm afraid.
Eventually ExoPlayer will be published under androidx.media3 and the old package/repository com.google.android.exoplayer2 will go away. The actual code is identical but will be published with a different package/module structure. The two repositories will co-exist in parallel for a while to provide some time for developers to migrate. We can't share a timeline for this because it hasn't be decided yet.

Thank you! That helps for making a choice...


Spread operator is missing in grammar.md

Syntax for creating an array:
var arrA = [ 2, 3 ]
output arrB array = [ 1, ...arrA, 4 ]

The array rule in grammar:
array -> "[" ( NL+ arrayItem* )? "]"
arrayItem -> expression NL+

I think the rule should be something like this:
arrayItem -> ( expression | "..." array ) NL+)

The same is true for the object rule.

Good catch, thanks!


Investigate sms not received issues

twillio api did not return an error, but some users messages didn't get delivered until long after they were send.

After investigating, the problem appear to be related to (a) Russian carrier(s) not delivering the messages to the recipients. Critical incident has been opened and filed with twillio support

twillio issues resolved, reply from twillio:


List notable implementation details of the various engines.

It would be interesting for readers of the benchmark results to better understand how the various engines differ. While many readers stop at Rust vs. Java vs. C++, there are lots of other notable implementation differences such as WAND vs. MAXSCORE or whether or not doc ID reordering is used.
I thought it was also interesting to highlight similarities, such as the use of mmap and PFOR-delta.

Here is what it looks like:

I made a change to make these changes folded by default, to avoid adding too much noise to the page. Here's what it looks like when folded:

And unfolded:

tantivy is FOR, not PFOR. (or maybe I misunderstand what PFOR means)

Woops, thanks for noticing.

@fulmicoton Does it look ready to merge?


upgrade helm-docs to v1.14.2

@skyzh could you just add some description of what your intention is with this change? And ideally link to a relevant issue? I don't have a ton of context otherwise 🙂

This is for making it easier to work with the repo. The version I put in the PR is the one that can be directly installed from homebrew :) Given now we have merge conflicts of this PR, I can open another one if necessary.


[FEATURE REQ] Cosmos SDK | Update RequestTimeline to include labels for both event and event duration

Adding meaningful names to duration fields would be useful to Cosmos SDK developers and end users in two ways:

Communicating the meaning of duration and
Labeling charts and graphs with event time on the x axis and duration on the y axis.

Example:
The sent event follows message encoding and occurs once it is confirmed that the message is on the wire. The duration of the sent event is the time that it takes for a round-trip to the server to complete and the next event occurs: received. The time between these two events--sent and received-- is the transitTime.
Something like this JSON is what we should produce--perhaps word-smithed and simplified for brevity:
{
  "event": {
    "name": "sent",
    "time": "<time-stamp>"
  },
  "interval": {
    "name": "transitTime",
    "duration": <microseconds>
  }
}

I've discussed this with Naveen and Mo. We agreed that this work should be done on another PR. I've logged this issue to track the work which I will assign to myself for now.

A thought - this is use for debugging user latency issue , in that case duration name transit is more relevant that the actual event name sent . Also it will be hard to come up with two different names (x axis and y axis) for all events in rntbd and http and can create more confusion . Lets do it as we learn ?

This is done.


Operator policies and virtual host connection limit support

What are the plans of providing rabbitmq 3.7 specific features like:
(1) Setting virtualhost limits.
(2) operator policy overrides.

You are welcome to contribute them.