[Bug]: NameError: name 'vllm_ops' is not defined

Your current environment
vllm version: 0.4.0.post1
🐛 Describe the bug
CUDA_VISIBLE_DEVICES="4"  python -u -m vllm.entrypoints.openai.api_server     --model mistralai/Mistral-7B-Instruct-v0.2     --dtype auto --api-key yanan     --tensor-parallel-size 1 --port 1703 --host <IP_ADDRESS>     --worker-use-ray --gpu-memory-utilization 1
error:

INFO 04-20 20:39:58 api_server.py:149] vLLM API server version 0.4.1
INFO 04-20 20:39:58 api_server.py:150] args: Namespace(host='<IP_ADDRESS>', port=1703, uvicorn_log_level='info', allow_credentials=False, allowed_origins=[''], allowed_methods=[''], allowed_headers=[''], api_key='yanan', served_model_name=None, lora_modules=None, chat_template=None, response_role='assistant', ssl_keyfile=None, ssl_certfile=None, ssl_ca_certs=None, ssl_cert_reqs=0, root_path=None, middleware=[], model='mistralai/Mistral-7B-Instruct-v0.2', tokenizer=None, revision=None, code_revision=None, tokenizer_revision=None, tokenizer_mode='auto', trust_remote_code=False, download_dir=None, load_format='auto', dtype='auto', kv_cache_dtype='auto', quantization_param_path=None, max_model_len=None, guided_decoding_backend='outlines', worker_use_ray=True, pipeline_parallel_size=1, tensor_parallel_size=1, max_parallel_loading_workers=None, ray_workers_use_nsight=False, block_size=16, enable_prefix_caching=False, use_v2_block_manager=False, num_lookahead_slots=0, seed=0, swap_space=4, gpu_memory_utilization=1.0, num_gpu_blocks_override=None, max_num_batched_tokens=None, max_num_seqs=256, max_logprobs=5, disable_log_stats=False, quantization=None, enforce_eager=False, max_context_len_to_capture=8192, disable_custom_all_reduce=False, tokenizer_pool_size=0, tokenizer_pool_type='ray', tokenizer_pool_extra_config=None, enable_lora=False, max_loras=1, max_lora_rank=16, lora_extra_vocab_size=256, lora_dtype='auto', max_cpu_loras=None, device='auto', image_input_type=None, image_token_id=None, image_input_shape=None, image_feature_size=None, scheduler_delay_factor=0.0, enable_chunked_prefill=False, speculative_model=None, num_speculative_tokens=None, model_loader_extra_config=None, engine_use_ray=False, disable_log_requests=False, max_log_len=None)
2024-04-20 20:40:01,364 INFO worker.py:1749 -- Started a local Ray instance.
INFO 04-20 20:40:02 llm_engine.py:98] Initializing an LLM engine (v0.4.1) with config: model='mistralai/Mistral-7B-Instruct-v0.2', speculative_config=None, tokenizer='mistralai/Mistral-7B-Instruct-v0.2', tokenizer_mode=auto, revision=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.bfloat16, max_seq_len=32768, download_dir=None, load_format=auto, tensor_parallel_size=1, disable_custom_all_reduce=False, quantization=None, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), seed=0)
INFO 04-20 20:40:05 utils.py:580] Found nccl from library /home/chenyanan/.config/vllm/nccl/cu12/libnccl.so.2.18.1
INFO 04-20 20:40:06 selector.py:77] Cannot use FlashAttention backend because the flash_attn package is not found. Please install it for better performance.
INFO 04-20 20:40:06 selector.py:33] Using XFormers backend.
INFO 04-20 20:40:08 weight_utils.py:193] Using model weights format ['.safetensors']
INFO 04-20 20:40:10 model_runner.py:173] Loading model weights took 13.4966 GB
ERROR 04-20 20:40:11 worker_base.py:153] Error executing method determine_num_available_blocks. This might cause deadlock in distributed execution.
ERROR 04-20 20:40:11 worker_base.py:153] Traceback (most recent call last):
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/worker/worker_base.py", line 145, in execute_method
ERROR 04-20 20:40:11 worker_base.py:153]     return executor(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
ERROR 04-20 20:40:11 worker_base.py:153]     return func(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/worker/worker.py", line 138, in determine_num_available_blocks
ERROR 04-20 20:40:11 worker_base.py:153]     self.model_runner.profile_run()
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
ERROR 04-20 20:40:11 worker_base.py:153]     return func(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/worker/model_runner.py", line 927, in profile_run
ERROR 04-20 20:40:11 worker_base.py:153]     self.execute_model(seqs, kv_caches)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
ERROR 04-20 20:40:11 worker_base.py:153]     return func(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/worker/model_runner.py", line 848, in execute_model
ERROR 04-20 20:40:11 worker_base.py:153]     hidden_states = model_executable(**execute_model_kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
ERROR 04-20 20:40:11 worker_base.py:153]     return self._call_impl(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
ERROR 04-20 20:40:11 worker_base.py:153]     return forward_call(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/model_executor/models/llama.py", line 360, in forward
ERROR 04-20 20:40:11 worker_base.py:153]     hidden_states = self.model(input_ids, positions, kv_caches,
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
ERROR 04-20 20:40:11 worker_base.py:153]     return self._call_impl(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
ERROR 04-20 20:40:11 worker_base.py:153]     return forward_call(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/model_executor/models/llama.py", line 286, in forward
ERROR 04-20 20:40:11 worker_base.py:153]     hidden_states, residual = layer(
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
ERROR 04-20 20:40:11 worker_base.py:153]     return self._call_impl(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
ERROR 04-20 20:40:11 worker_base.py:153]     return forward_call(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/model_executor/models/llama.py", line 224, in forward
ERROR 04-20 20:40:11 worker_base.py:153]     hidden_states = self.input_layernorm(hidden_states)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
ERROR 04-20 20:40:11 worker_base.py:153]     return self._call_impl(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
ERROR 04-20 20:40:11 worker_base.py:153]     return forward_call(*args, **kwargs)
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/model_executor/layers/layernorm.py", line 60, in forward
ERROR 04-20 20:40:11 worker_base.py:153]     ops.rms_norm(
ERROR 04-20 20:40:11 worker_base.py:153]   File "/home/chenyanan/vllm/vllm/_custom_ops.py", line 106, in rms_norm
ERROR 04-20 20:40:11 worker_base.py:153]     vllm_ops.rms_norm(out, input, weight, epsilon)
ERROR 04-20 20:40:11 worker_base.py:153] NameError: name 'vllm_ops' is not defined
Traceback (most recent call last):
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/home/chenyanan/vllm/vllm/entrypoints/openai/api_server.py", line 157, in
engine = AsyncLLMEngine.from_engine_args(
File "/home/chenyanan/vllm/vllm/engine/async_llm_engine.py", line 356, in from_engine_args
engine = cls(
File "/home/chenyanan/vllm/vllm/engine/async_llm_engine.py", line 319, in init
self.engine = self._init_engine(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/engine/async_llm_engine.py", line 432, in _init_engine
return engine_class(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/engine/llm_engine.py", line 153, in init
self._initialize_kv_caches()
File "/home/chenyanan/vllm/vllm/engine/llm_engine.py", line 228, in _initialize_kv_caches
self.model_executor.determine_num_available_blocks())
File "/home/chenyanan/vllm/vllm/executor/ray_gpu_executor.py", line 199, in determine_num_available_blocks
num_blocks = self._run_workers("determine_num_available_blocks", )
File "/home/chenyanan/vllm/vllm/executor/ray_gpu_executor.py", line 323, in _run_workers
driver_worker_output = self.driver_worker.execute_method(
File "/home/chenyanan/vllm/vllm/worker/worker_base.py", line 154, in execute_method
raise e
File "/home/chenyanan/vllm/vllm/worker/worker_base.py", line 145, in execute_method
return executor(*args, **kwargs)
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/worker/worker.py", line 138, in determine_num_available_blocks
self.model_runner.profile_run()
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/worker/model_runner.py", line 927, in profile_run
self.execute_model(seqs, kv_caches)
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/worker/model_runner.py", line 848, in execute_model
hidden_states = model_executable(**execute_model_kwargs)
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/model_executor/models/llama.py", line 360, in forward
hidden_states = self.model(input_ids, positions, kv_caches,
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/model_executor/models/llama.py", line 286, in forward
hidden_states, residual = layer(
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/model_executor/models/llama.py", line 224, in forward
hidden_states = self.input_layernorm(hidden_states)
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/chenyanan/anaconda3/envs/vllm/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/home/chenyanan/vllm/vllm/model_executor/layers/layernorm.py", line 60, in forward
ops.rms_norm(
File "/home/chenyanan/vllm/vllm/_custom_ops.py", line 106, in rms_norm
vllm_ops.rms_norm(out, input, weight, epsilon)
NameError: name 'vllm_ops' is not defined

I just received this error as well. Seems to only happen on non-quantized mistral-7B models.

using langchain can works, as an alternative.
https://python.langchain.com/docs/integrations/llms/vllm/
from langchain_community.llms import VLLM

llm_vllm = VLLM(model='mistralai/Mistral-7B-Instruct-v0.2',
           trust_remote_code=True,  # mandatory for hf models
           max_new_tokens=2048,
           temperature=1,
           # tensor_parallel_size=... # for distributed inference
)

I'm seeing the same issue.
Catching the import error gives:
No module named 'vllm._C'
Also seeing warnings during install:
...
CMake Warning at /home/tensorwave/install_vllm/venv/lib/python3.10/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:22 (message):
  static library kineto_LIBRARY-NOTFOUND not found.
Call Stack (most recent call first):
  /home/tensorwave/install_vllm/venv/lib/python3.10/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:127 (append_torchlib_if_found)
  CMakeLists.txt:67 (find_package)

CMake Warning at CMakeLists.txt:124 (message):
  Pytorch version 2.1.1 expected for ROCMm 6.x build, saw 2.4.0 instead.

-- HIP supported arches: gfx906;gfx908;gfx90a;gfx940;gfx941;gfx942;gfx1030;gfx1100
-- HIP target arches: gfx942;gfx942;gfx942;gfx942;gfx942;gfx942;gfx942;gfx942
CMake Warning at CMakeLists.txt:266 (message):
  Unable to create _punica_C target because none of the requested
  architectures (gfx942;gfx942;gfx942;gfx942;gfx942;gfx942;gfx942;gfx942) are
  supported, i.e.  >= 8.0
...

Works when TP is not set.
Currently trying to get working with MI300x on ROCm 6.1.

Found fix; for me it was an issue for running benchmark test from the package directory. During installation, the _C module is compiled into the site-packages directory of the pip installation. When running from the source directory, the script is getting the code from source and not the installed package containing the compiled module.
Command:

FROM vllm dir
python3 benchmarks/benchmark_throughput.py --input-len=50 --output-len=100 --enforce-eager --tensor-parallel-size=6

Error:
   ... File "~/workspace/vllm/vllm/_custom_ops.py", line 176, in reshape_and_cache      vllm_cache_ops.reshape_and_cache(key, value, key_cache, value_cache,  NameError: name 'vllm_cache_ops' is not defined  (Caught error: No module named 'vllm._C')
The script is picking up on the local module at ~/workspace/vllm/vllm instead of the installed module. Running the command from a different directory, such as the benchmarks directory, fixes this.
@yananchen1989 I notice your stack trace is also coming from source, /home/chenyanan/vllm/vllm/_custom_ops.py, try running from a separate directory after installing source. Let me know if this fixes the issue.
That being said, the try / except imports are causing unhelpful stack traces; I will look into doing an audit of compiled modules and adding useful warnings when not detected.

tests/ folder also suffer from this vllm_ops not defined issue.
And I create this PR for pytest, https://github.com/vllm-project/vllm/pull/4231, which force pytest to search module from installed place.

I get this error after doing a clean install with pip install -e . of commit 26f2fb51133c85ad8a57a87c8037f750dda757f4. There were no errors during the installation... but this runtime error might be because I used too new dependencies (Python 3.10.12, Pytorch 2.3, Cuda 12.4)?

it looks like Pytorch 2.3.0 causes the problem

I have this error:
INFO 05-22 14:25:08 utils.py:660] Found nccl from library /lib64/libnccl.so.2
INFO 05-22 14:25:09 selector.py:81] Cannot use FlashAttention-2 backend because the flash_attn package is not found. Please install it for better performance.
INFO 05-22 14:25:09 selector.py:32] Using XFormers backend.
INFO 05-22 14:25:34 model_runner.py:175] Loading model weights took 13.5516 GB
[rank0]: Traceback (most recent call last):
[rank0]:   File "<frozen runpy>", line 198, in _run_module_as_main
[rank0]:   File "<frozen runpy>", line 88, in _run_code
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/entrypoints/openai/api_server.py", line 168, in <module>
[rank0]:     engine = AsyncLLMEngine.from_engine_args(
[rank0]:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/engine/async_llm_engine.py", line 366, in from_engine_args
[rank0]:     engine = cls(
[rank0]:              ^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/engine/async_llm_engine.py", line 324, in __init__
[rank0]:     self.engine = self._init_engine(*args, **kwargs)
[rank0]:                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/engine/async_llm_engine.py", line 442, in _init_engine
[rank0]:     return engine_class(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/engine/llm_engine.py", line 172, in __init__
[rank0]:     self._initialize_kv_caches()
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/engine/llm_engine.py", line 249, in _initialize_kv_caches
[rank0]:     self.model_executor.determine_num_available_blocks())
[rank0]:     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/executor/gpu_executor.py", line 106, in determine_num_available_blocks
[rank0]:     return self.driver_worker.determine_num_available_blocks()
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/worker/worker.py", line 139, in determine_num_available_blocks
[rank0]:     self.model_runner.profile_run()
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/worker/model_runner.py", line 888, in profile_run
[rank0]:     self.execute_model(seqs, kv_caches)
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/worker/model_runner.py", line 808, in execute_model
[rank0]:     hidden_states = model_executable(**execute_model_kwargs)
[rank0]:                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/model_executor/models/qwen2.py", line 316, in forward
[rank0]:     hidden_states = self.model(input_ids, positions, kv_caches,
[rank0]:                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/model_executor/models/qwen2.py", line 253, in forward
[rank0]:     hidden_states, residual = layer(
[rank0]:                               ^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/model_executor/models/qwen2.py", line 202, in forward
[rank0]:     hidden_states = self.input_layernorm(hidden_states)
[rank0]:                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/model_executor/layers/layernorm.py", line 60, in forward
[rank0]:     ops.rms_norm(
[rank0]:   File "/usr/local/lib64/python3.11/site-packages/vllm/_custom_ops.py", line 106, in rms_norm
[rank0]:     vllm_ops.rms_norm(out, input, weight, epsilon)
[rank0]:     ^^^^^^^^
[rank0]: NameError: name 'vllm_ops' is not defined

Found fix; for me it was an issue for running benchmark test from the source directory. During installation, the _C module is compiled into the site-packages directory of the pip installation. When running from the source directory, the script is getting the code from source and not the installed package containing the compiled module.
Command:

FROM vllm dir
python3 benchmarks/benchmark_throughput.py --input-len=50 --output-len=100 --enforce-eager --tensor-parallel-size=6

Error:  ... File "~/workspace/vllm/vllm/_custom_ops.py", line 176, in reshape_and_cache vllm_cache_ops.reshape_and_cache(key, value, key_cache, value_cache, NameError: name 'vllm_cache_ops' is not defined (Caught error: No module named 'vllm._C')
The script is picking up on the local module at ~/workspace/vllm/vllm instead of the installed module. Running the command from a different directory, such as the benchmarks directory, fixes this.
@yananchen1989 I notice your stack trace is also coming from source, /home/chenyanan/vllm/vllm/_custom_ops.py, try running from a separate directory after installing / compiling source. Let me know if this fixes the issue.
That being said, the try / except imports are causing unhelpful stack traces; I will look into doing an audit of compiled modules and adding useful warnings when not detected.

I also met this error. And it was fixed after changing working directory out of the vllm source code.
If your error stack trace has shown with your specific path, then try to 'cd' out.
Probably many of us have a same habit to directly run tests or getting-start at the source code dir :)

Fixed by #5009

Please follow these instructions from the docs.


Pull branch from Codeship environment

Right now Codeship builds just go onto the HEAD branch, which isn't super useful. This should pull the branch of Codeship builds so that they're appropriately marked in Coveralls. Reference

Thank you!
A regression test would be awesome too ;)


Refactor client interfaces

Scope of changes
This reduces some common code when making parallel GDS requests by using the unified directory service and members service client.
sc-6359
Type of change

[ ] bug fix
[ ] new feature
[ ] documentation
[x] refactoring

Acceptance criteria
Unit tests should still pass, and are the method/struct names understandable?
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report

Merging #586 (0b00e98) into main (b377917) will decrease coverage by 5.80%.
The diff coverage is n/a.

:exclamation: Current head 0b00e98 differs from pull request most recent head a954786. Consider uploading reports for the commit a954786 to get more accurate results

@@            Coverage Diff             @@
##             main     #586      +/-   ##
==========================================
- Coverage   45.92%   40.11%   -5.81%
==========================================
  Files         510      420      -90
  Lines       14675     4721    -9954
  Branches     1171     1171
==========================================
- Hits         6740     1894    -4846
+ Misses       6913     2643    -4270
+ Partials     1022      184     -838

Impacted Files
Coverage Δ

...com/trisacrypto/directory/pkg/trtl/replica/sync.go

...risacrypto/directory/pkg/gds/store/index/search.go

...m/trisacrypto/directory/pkg/gds/store/trtl/mock.go

...com/trisacrypto/directory/pkg/bff/api/v1/errors.go

...com/trisacrypto/directory/pkg/gds/config/config.go

...ithub.com/trisacrypto/directory/pkg/trtl/server.go

...risacrypto/directory/pkg/gds/client/credentials.go

...com/trisacrypto/directory/pkg/gds/tokens/tokens.go

...crypto/directory/pkg/gds/store/leveldb/iterator.go

...ithub.com/trisacrypto/directory/pkg/gds/service.go

... and 80 more

Continue to review full report at Codecov.

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


Feature request: Writing to JSON schema

DendroPy is awesome.
I would love to see DendroPy's Tree data structures access modern tree visualization tools like D3. A simple method for writing the Tree data structure to a JSON schema would do the trick.  I'm imagining JSON that follows the format described in this post.
I'd be happy to work on a PR if y'all agree it would be useful.

This is a wonderful idea! Fantastically wonderful. I've been looking for a lightweight, portable, visualization solution, and this would be it.
Would be great to have you work on it! Otherwise, I can try an implementation myself (I love the idea so much!).
If you want to work on it, let me know, and we can discuss organization and API.
For the former, I think it should go into the dendropy.dataio hierarchy, maybe in its own module, dendropy.dataio.d3writer?
Perhaps the API should follow, for e.g. that for the NewickWriter, in terms of what gets rendered (node labels, edge lengths etc.). Also, support for other rendering features (colors, node shapes, edge thicknesses, tree styles, what gets collapsed etc. etc.) should be planned in the API even if we do not get around to implementing it all?

Fantastic! I'd be happy to help!
 Whatever works best for you! Otherwise, I'd be happy take a crack at it myself (hopefully sometime today or tomorrow).
Yeah, I agree it makes sense to have this API live in its own module in dendropy.dataio. There is likely a format specified/standardized by Vega for this kind of data structure and all the rendering features you mentioned. This might be a good place to start planning the organization. Vega was started with D3 in mind. I'll look through their docs for ideas.

Great!
I think given my familiarity with the codebase, one approach would be
for me to set up all the "scaffolding" --- i.e., the hooks into the data
schema API, the basic class to handle the writing etc., and leave the
main "write" method as a stub to be fleshed out. Then, if you want and
have the time, you can work at translating the tree structure into the
required JSON. I can work on this over this weekend or next week. In the
mean time, if you are agreeable, maybe get familiar with the Vega/D3
API, features, etc. (if you are not already)?
On 3/31/16 12:33 PM, Zachary Sailer wrote:

Fantastic! I'd be happy to help!
 Whatever works best for you!
Otherwise, I'd be happy take a crack at it myself (hopefully sometime
today or tomorrow).
Yeah, I agree it makes sense to have this API live in its own module in
|dendropy.dataio|. There is likely a format specified/standardized by
Vega https://github.com/vega/vega for this kind of data structure and
all the rendering features you mentioned. This might be a good place to
start planning the organization. Vega was started with D3 in mind. I'll
look through their docs for ideas.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/jeetsukumaran/DendroPy/issues/46#issuecomment-204011499

--

Jeet Sukumaran
<EMAIL_ADDRESS>Blog/Personal Pages:
http://jeetworks.org/
GitHub Repositories:
http://github.com/jeetsukumaran
Photographs (as stream):
http://www.flickr.com/photos/jeetsukumaran/
Photographs (by galleries):
http://www.flickr.com/photos/jeetsukumaran/sets/

Sounds good! Ping me when you have the basic hooks in place. I'll work on the JSON format and post some ideas here.

Will do!
On 3/31/16 1:18 PM, Zachary Sailer wrote:

Sounds good! Ping me when you have the basic hooks in place. I'll work
on the JSON format and post some ideas here.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/jeetsukumaran/DendroPy/issues/46#issuecomment-204031556

--

Jeet Sukumaran
<EMAIL_ADDRESS>Blog/Personal Pages:
http://jeetworks.org/
GitHub Repositories:
http://github.com/jeetsukumaran
Photographs (as stream):
http://www.flickr.com/photos/jeetsukumaran/
Photographs (by galleries):
http://www.flickr.com/photos/jeetsukumaran/sets/

Ok,
I've put the scaffolding in place:
https://github.com/jeetsukumaran/DendroPy/blob/d3writer/dendropy/dataio/d3writer.py#L148-L160

The _write_tree_list() is for any overhead/meta stuff required for a
group of trees, while _write_tree() works on a single tree. You can
see the corresponding methods in the NewickWriter class for examples on
how this is handled.
Test framework in place at:
https://github.com/jeetsukumaran/DendroPy/blob/d3writer/dendropy/test/test_dataio_d3_writer.py

Test design is going to take some thinking. Typically, the approach has
been to round-trip read-write-read, and then confirm that the objects of
second reading semantically correspond to the objects of the first
reading. Lots of infrastructure to support this.
With a write-only paradigm here, we might have to do a brute-force /
dumb approach, i.e., check if the generated strings match exactly what
is expected. This works, but is fragile -- i.e., non-semantic changes in
the rendering pipeline will break the test (e.g., placement of spaces,
newlines, etc.). But that's not a deal-breaker, I suppose, being only
majorly annoying in the main development phase and usually
easily-fixable. I am open to other suggestions if you have any.
I might find time to work on the actual D3 composition implementation
next week or later. If you want to give it a go in the mean time, that
would be great!
-- jeet
On 3/31/16 1:18 PM, Zachary Sailer wrote:

Sounds good! Ping me when you have the basic hooks in place. I'll work
on the JSON format and post some ideas here.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/jeetsukumaran/DendroPy/issues/46#issuecomment-204031556

--

Jeet Sukumaran
<EMAIL_ADDRESS>Blog/Personal Pages:
http://jeetworks.org/
GitHub Repositories:
http://github.com/jeetsukumaran
Photographs (as stream):
http://www.flickr.com/photos/jeetsukumaran/
Photographs (by galleries):
http://www.flickr.com/photos/jeetsukumaran/sets/

Awesome, thanks for getting that in place! I've forked the d3writer branch and should get some time to work on it today/tomorrow.

Hi @jeetsukumaran
Sorry for the long delay on this. The summer proved to be a busy time for me. But I was able work on this idea yesterday. I've even got a prototype branch here.
This is far from finished. Note, I haven't added most of the keyword arguments, nor have I written tests. I was mostly familiarizing myself with DendroPy's data I/O API.
I did make a simple, static example of my working branch visible in this gist.
Currently, I construct a nested dictionary for a tree. This basically converts the Tree object into a hierarchical, metadata dictionary. Then, I use python's standard json library to encode the metadata as a JSON string. This library handles all None-to-null, True-to-true, and False-to-false conversions.
It appears that there is not yet a clear, standardized JSON/Vega grammar defined for hierarchical, tree-like data. There is conversation going on between the "Open Tree of Life" group. In summary, Vega is starting to make a point to flatten JSON formats for readability, which doesn't work well for hierarchical data. My opinion is that we stick to the examples from D3. Every node has a "name" and "children" key-value pair. The "children" value is an array of child nodes. Child nodes have a "parent" argument pointing back to the parent name. I think, at the very least, this basic structure is acceptable to the general user-base:
{
    "name" : "A",
    "children" : [
        {
             "name" : "B",
             "children" : [],
        },
        {
             "name" : "C",
             "children" : [],
        },
    ]
}

Other items can be specific to DendroPy, but don't affect the generality of the output. For example, annotations, if not suppressed, are included as an "annotations" key mapped to a set of key-value pairs for each annotation. Lengths of branches, if not suppressed, are included as "length" in each child node's data.
Finally, as a small aside: I'm thinking we should rename the writer to JSONWriter instead of D3Writer. I think this data type of output is more general than just D3. It has other advantages like portability to other languages. I also find JSON format more human readable compared to other tree formats. It doesn't matter to me too much. If you'd rather keep the focus on D3, I'm fine with that as well.

Great stuff!
Really like what is happening here.
I agree with you that readability is nice, but really, really, really, really, really, should not take priority over usability. And there is strong reason to keep hierarchical data hierarchical. At the same time, we are (presumably?) not out to create a new data format, but rather render the data model in a format that can be consumed by an existing visualization technology, and it makes sense to use the format/conventions/standards/expectations of the visualization technology that we are targeting to condition output. TL;DR: I agree, stick to D3!
As far as the naming goes, given that I imagine at some point we would like to take advantage of some D3-specific expression capability,  my suggestion would be to have a JsonWriter class that handles all generic JSON stuff, and a D3JsonWriter that specializes it. Client code would then specify schema="json-d3" or schema="d3" (for example; we can decide the name later) to render the tree as D3-specific JSON and schema="json" for more generic JSON (if we want to support that). The D3JsonWriter would, of course, over-ride the _write etc. methods as needed, and also call on the base class _write as needed. I think the addition of the class hierarchy complexity is offset by the gains in modularity, abstraction, and DNRY-ness?
But that is just my suggestion. If you feel that simply renaming it "JSONWriter" makes more sense (with, maybe, the optional specification of a keyword dialect="D3" to activate D3-specific rendering), then that would be the way to go!

Yes, I definitely agree that we aren't trying to create a new data format (haha). I'm just surprised that there isn't a defined "tree" grammar for JSON format already out there (at least not that I could find immediately). It seems like there are so many great visualization tools that are prime for such a grammar. By including such a writer in DendroPy, we might be inadvertently contributing to creation of such a grammar.
I agree with keeping the hierarchy in the output, and D3 seems to honor that as well.
I really like the idea of subclassing a JsonWriter class. I'll add that to my next implementation. I think D3 is one use-case (and likely most popular use-case) of a JSON format. It would great to connect DendroPy to fresh visualization tools like D3. A lot of these tools are written as Javascript libraries, so JSON is the natural porting mechanism. A subclassed writer would likely include extra visualization attributes (i.e. window size, colors, etc). The more general JSON format, however, would be useful for porting DendroPy tree data to other APIs or languages. I'm saying this for selfish reasons ;)
Thanks for talking through this stuff! I'll keep working on it and keep you updated!

Also, in the interest of making a general JSON format that is portable, would a JsonReader class make sense as well? Or do you think this is outside the scope of DendroPy?

A reader would indeed be nice. I imagine the use case would be more limited, especially if the JSON is narrowly defined (DendroPy/D3-specific)? Though, having a reader will be useful for tests (round-tripping). Just as relevant, with projects like this, it is not always necessary to stick exclusively to what is important/needed/useful; I always tend to work in things that I like/want, even if it is very idiosyncractic and done more for interest rather than utility. So if the idea of writing a reader appeals to you, go for it!
WRT to JSON tree grammar/data format, the OTOL folks are using a JSON-based derivation of NeXML. I've been meaning to write a DendroPy parser for it, but it's been on the back-burner. Not saying that it should be used here, but mentioning it for reference or source of ideas.

Hey! @jeetsukumaran
I wanted to mention a new project I've been working on here. PhyloVega is a Python package that uses Vega's (JSON) specifications to draw interactive trees.
While writing this package, I (finally) figured out the Vega grammar for drawing trees. I think it's pretty powerful. With Vega's declarative grammar, I can style my tree any way I want. In this example below, I read in a tree using PhyloPandas and style the tree using a declarative grammar API. Underneath the hood, the TreeChart object is just building a JSON spec for Vega.
from phylopandas import read_newick
from phylovega.api import TreeChart

# Read tree using PhyloPandas
df = read_newick('tree.newick')

# Construct Vega Specification
chart = TreeChart(
    df,
    height_scale=200,

    # Node attributes
    node_size=200,
    node_color="#ccc",

    # Leaf attributes
    leaf_labels="id",

    # Edge attributes
    edge_width=2,
    edge_color="#000",
)

# Display in Jupyter
chart.display()

This may be an interesting light-weight visualization solution for DendroPy. If I can find some time, I'll write up documentation for this grammar. Then, it would be pretty easy to write a JSON I/O tool for DendroPy. What do you think?

Hi Zach,
That sounds great. I think it makes most sense, though, for the
visualization to be handled by your library, and I can work on making
sure the object model and API allows for seamless interaction. That way,
there is no duplication of effort and all it takes from a DendroPy
user's perspective is "import phylovega; phylovega.()"?
-- jeet
On 07/16/2018 06:02 PM, Zachary Sailer wrote:

Hey! @jeetsukumaran https://github.com/jeetsukumaran
I wanted to mention a new project I've been working on here. PhyloVega
https://github.com/Zsailer/phylovega is a Python package that uses
Vega's (JSON) specifications to draw interactive trees.
While writing this package, I (finally) figured out the Vega grammar for
drawing trees. I think it's pretty powerful. With Vega's declarative
grammar, I can style my tree any way I want. In this example below, I
read in a tree using PhyloPandas and style the tree using a declarative
grammar API. Underneath the hood, the TreeChart object is just building
a JSON spec for Vega.
from  phylopandasimport  read_newick
from  phylovega.apiimport  TreeChart
Read tree using PhyloPandas
df=  read_newick('tree.newick')
Construct Vega Specification
chart=  TreeChart(
df,
height_scale=200,
 # Node attributes
 node_size=200,
 node_color="#ccc",

 # Leaf attributes
 leaf_labels="id",

 # Edge attributes
 edge_width=2,
 edge_color="#000",

)
Display in Jupyter
chart.display()
static-example
https://user-images.githubusercontent.com/2791223/42785818-a77490dc-8908-11e8-9480-27b3ed85d41e.png
This may be an interesting light-weight visualization solution for
DendroPy. If I can find some time, I'll write up documentation for this
grammar. Then, it would be pretty easy to write a JSON I/O tool for
DendroPy. What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jeetsukumaran/DendroPy/issues/46#issuecomment-405395657,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABmRw-YpwX4iDOWlJUlSxLAS6tGHp8bks5uHQ1sgaJpZM4H84VZ.

--

Jeet Sukumaran
<EMAIL_ADDRESS>Blog/Personal Pages:
http://jeetblogs.org/
Departmental Page:
https://lsa.umich.edu/eeb/people/research-scientists/jeetsu.html
GitHub Repositories:
http://github.com/jeetsukumaran
Photographs (as stream):
http://www.flickr.com/photos/jeetsukumaran/
Photographs (by galleries):
http://www.flickr.com/photos/jeetsukumaran/sets/


Concept of probability and binomial  theorem

Description
To find the minimum number of times a fair coin must be tossed so that the probability of getting at least one head is more than 99%.
Important Checklist
[. ] I have read the contribution guidelines before making this issue.
[. ] I have verified this issue program is not already implemented
[ .] I have not pushed this code anywhere else (even my repo)
Languages and Assignees:

[ ] Python: @
[ ] Java: @

Please put the label HACKTOBERFEST and kindly let me work on this.

@aastha01chauhan Fill the issue template properly

Hi, I have done the same. Please assign me the task.

@aastha01chauhan which language?

Python and java.
Please put the label hacktoberfest

You can only work in one language for each issue choose one

Then it is Java.
Please don't forget to put the label for hacktoberfest.

@aastha01chauhan Are you working on this?

Yes. I am. I will complete it by today or latest by tomorrow evening.

I have done it.


Assertion error in client.prinipal

On master  0.8.0rc0 downloaded from github on 2/8/2021
Traceback (most recent call last):
File "", line 1, in
File "/home/pi/MessageBoard/dev/caldav/davclient.py", line 319, in principal
return Principal(self)
File "/home/pi/MessageBoard/dev/caldav/objects.py", line 398, in init
cup = self.get_properties([dav.CurrentUserPrincipal()])
File "/home/pi/MessageBoard/dev/caldav/objects.py", line 221, in get_properties
properties = self.handle_xml_response(response, props)
File "/home/pi/MessageBoard/dev/caldav/objects.py", line 192, in handle_xml_response
results = response.expand_simple_props(props=props, multi_value_props=multi_value_props)
File "/home/pi/MessageBoard/dev/caldav/davclient.py", line 241, in expand_simple_props
self.find_objects_and_props()
File "/home/pi/MessageBoard/dev/caldav/davclient.py", line 177, in find_objects_and_props
error.assert(not href in self.objects)
File "/home/pi/MessageBoard/dev/caldav/lib/error.py", line 23, in assert
assert(condition)
AssertionError
Note.  Commented out the assertion on line 177 and everything seemed to work fine.
Log files attached.
example1.log

The reply from the server contains two hrefs (one directly in the response block, the other nested inside the propstat/prop blocks), that's probably what's triggering the assert.  I've seen similar things from iCloud.  I have no clue if this is a breach of the standard or not, but I'll make some unit test and make sure that this XML does not cause any asserts to be triggered.
PS: in the current master branch, it's possible to set an environment variable PYTHON_CALDAV_DEBUG_MODE.  If it's set to DEBUG_PDB, one will be thrown into the debugger when asserts are raised.  If set to PRODUCTION, the asserts will log errors rather than break everything.

Oh, when doing more research on it, I can see that the URL is actually repeated three times in the returned XML.  The response block is actually duplicated.  Anyway ... as long as there exists caldav servers giving such a response, we should not throw an AssertionError.  I've remade the code into accepting duplicates.


Incompatible with Paradise Lost

https://pastebin.com/WYhTxw2y
Game crashes with both BCLib and Paradise Lost. It starts with one or the other removed.

Duplicate of #128 and #130


Ansible Resource Model missing "SSH Passphrase for private key"

In the "Ansible Resource Model Source" there is no way to set the option for the "SSH Passphrase for private key". This option is present in the "Ansible Ad Hoc Node Executor" Project configuration settings as well as in the "Ansible Playbook" and "Ansible Inline Playbook" Job Workflow configuration settings. Having it missing from the "Ansible Resource Model Source" makes it impossible to use the option in the Workflow and Ad Hoc settings, because if a password is set on the ssh key, it cannot be provided to the Resource Model Source, so no nodes are visible.

See also https://github.com/Batix/rundeck-ansible-plugin/issues/298
I think it would make sense to solve these 2 issues together, so the same data, securely saved in the Key Storage, can be used to enable ssh connections in all the Ansible Plugin components.
(Right now we'd have to set up a new ssh keypair without a password, and then save it outside the Key Storage... I'll just wait for an update before we migrate to rundeck instead.)

Strange that this is still not fixed. It is very important if you want to switch to rundeck.

Security should be #1. This may not be the product for production environment.

this already exits in the lastest releases


Add more contrat to highlighting to improve readibility

I try to use Nord theme in VScode but I'm confused by lower constrast in conparaison of other theme like Night Owl (My previous theme).
In this example with Typescript, I find it's difficult to easily difference what are Builtin class/variable, what are local constant or variable, ...

In comparison of Night Owl here different type use different color to be able to distinguish things more easily.

I appreciate the Nord theme, but this lower contrast ask me more effort to understand the code.
I haven't really idea how to deal with it. I tried different variation from Nord palette, but for now I haven't found an "perfect" configuration.
Some one haved a suggestion ?

Hi @sebtiz13 :wave:
Basically you answered your question on your own in the first sentence:

[…] in conparaison of other theme […]

That is the reason why different themes exist: every theme has its own flavor, and that is good.
Nord especially tries to reduce the “color noise“ by not trying to ue a different color for every syntax token. The more pastel and contrast reduced colors try to calm down eyes and help to minimize the diffusion your brain has to do for all these confusing colors instead of focusing for the important part: the code flow and the creation of its logic.
I don‘t want to talk bad about other themes, but many of them look like what a ecstasy trip must look like with way too many colors and often times no logic which color is used for which specific syntax token.
Taking your example screenshot from the other theme the first thing I notice is that function calls and constants are colored the same, two completely different syntax types, which is the first disruption that your brain has to passively tell apart every time. Also a class is the same color as a string, again two types that have nothing in common at all. I guess all of this is part of the themes design and flavor, but Nord want to improve on this topic and therefore carefully tries to separate syntax tokens in a constant way, even across multiple ports. Even through you might think that the “color noise“ does not affect you at all, your brain is passively disturbed by it and in the end you'll notice that you often loose focus or get tired quickly when coding and trying to develop the code logic.
Regarding your problem of distinguishing some syntax elements: This sounds more like a problem of the capabilities of the application, in this case VS Code, rather than a theme problem. Detecting a class and local variable is always something the IDE must evaluate dynamically through active language syntax engines or parsers in the background by using the specific compiler or language executer since it always depends on the content where the variable is used. Simple regular expression, or better token based in case of VS Code, highlighting doesn‘t take context into account which limits the way how detailed elements can be distinguished a lot.
In the end all I can say is that you can always customize a theme like Nord to match your preferences by overriding styles and syntax token highlighting rules for your local setup. This is the perfect solution to serve for everyone when you don‘t agree with some styles of your favorite theme.

Hi @svengreb.
Thank you for your explanation, I understand your point of view and indeed vscode limits the possibility to distinguish tokens in some cases, that's why it's complicated to have a "perfect" theme.
Indeed I made a local configuration to overload the tokens which disturbed me the most, I only wanted to emphasize this lack of distinction / contrast of the tokens to try to help improve the theme


Support go-to-implementation

Discussed in https://github.com/microsoft/pylance-release/discussions/2642

Originally posted by MalcolmMielle April 29, 2021
Hi all,
The "find implementation" feature doesn't seem to work well. I have a method f in a class A that inherits from B and reimplements f, and I'd like to list all "f" implementation, but nothing gets listed.
Is the feature included in Pylance, and if yes, am I missing something?
Thanks,

bump?

This issue has been fixed in prerelease version 2024.12.100, which we've just released. You can find the changelog here: CHANGELOG.md

Note that we're still discussing how this should behave. There's another issue here as a follow up:
https://github.com/microsoft/pylance-release/issues/6775

will it also be possible to list all implementations?


Fix RxJava versions in README

I thought to specify proper RxJava versions to enable an immediate Copy/Paste 😄

Codecov Report

Merging #35 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #35   +/-   ##
=========================================
  Coverage     93.84%   93.84%
  Complexity       14       14
=========================================
  Files             7        7
  Lines           325      325
  Branches         47       47
=========================================
  Hits            305      305
  Misses            4        4
  Partials         16       16

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 d94a9d1...6f5053c. Read the comment docs.


[sharding-jdbc-spring-boot-starter] wrong config key

Bug Report
Which project did you use? Sharding-JDBC or Sharding-Proxy?
I'm using sharding-jdbc v4.0.0-RC2:
        <dependency>
            <groupId>org.apache.shardingsphere</groupId>
            <artifactId>sharding-jdbc-spring-boot-starter</artifactId>
            <version>4.0.0-RC2</version>
        </dependency>

Actual behavior
the doc uses username for ds config

but it raises an error that username is empty:

problem is fixed when we chage the username to name

Expected behavior
the config key in sharding-jdbc-spring-boot-starter should be username or the config key in doc should be user
Reason analyze (If you can)
typo

ummmmmm, i know why i have this problem...
the config is different between datasource types, so...
for example, when I use hikari datasource, this config is ok:
        type: com.zaxxer.hikari.HikariDataSource
        driver-class-name: com.mysql.cj.jdbc.Driver
        jdbc-url: jdbc:mysql://localhost:3306/xxx
        username: root
        password: 123456


[doc] How to Pass String Literal as Script Argument is Hidden in Docs

Section on LanguageRef is very short at this point

assign to me, PR already open


Test harnes Leader 9.2.6 fail

Problem
Running on NXP K32W061 board.
Test harness Leader 9.2.6 fail at step :
Check if Data Response packet has Security
Policy TLV in Active Operational Dataset : Security
Policy sub TLV not present
See attached logs
Fail_OT_NXP_9_2_6_Leader_v54.4_2022_05_06-10_51_02.zip
After doing the bisection :
It starts failing with :
https://github.com/openthread/ot-nxp/commit/f68cedc102
This open thread submodule update correspond to one change in the open thread stack :
https://github.com/openthread/openthread/commit/a8b4fbb1893823e1c247ee1cc

Closing as duplicate of https://github.com/openthread/ot-nxp/issues/264


Add mongoid-danger

Closes #20

Thanks! Could you check the build? I think we need to lock down or remove some things under older rails's.

FYI, I've added DANGER_GITHUB_API_TOKEN to Travis.

Seems painful, but danger-changelog wants things in a certain format, ie. with the name of the person contributing. I've edited changelogs by hand many times :)

My first thought wasn't "painful", more like "silly".
But... what exactly does it want from me?
I've added names to the changes but still it doesn't like it? I can't reference PRs because there aren't PRs for most changes. What do I do?

It has a very particular format in mind that involves expanding the markdown link. The danger-changelog gem is just not smart enough to do references, so the names at the end of the change item need to include the link directly. I opened https://github.com/dblock/danger-changelog/issues/22 for adding support for that, if you feel like going down the rabbit hole :)
I fixed this PR up, it's ready to merge and is green.
The good news is that it yells at developers for you, so once you can live with this format you never have to worry about it again :)

Ah I see.. I did try that format but it didn't remove the lines from the warnings. So after trying a couple variations I gave up 😞
Thanks for the help! I will merge this now


problem in the skins of the new update of agar.io

I wanted to ask if you have solved this skin problem yet?

@Fan7asy 👍

so I can put the new skins in the minions, without everyone getting the same skin?

so I can put the new skins in the minions, without everyone getting the same skin?

I think not yet:, (

Nope.

@Megabyte918  can you please fix

lol ,I hope you can

fixxxxxxxxxxx plssssssssssss @Megabyte918

@ZfsrGhS953 you got any fix ?

@fayizan Yes, it's very simple: stop using the Megacyst (aka Miniclip)'s client.

Do what he said lol

do what agarian said


Allow specifying the C++ edition

In certain build environments cough ChromeOS cough the C++ edition may be hamstrung. For example, chrono may not be available - see https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++-features.md#chrono_banned.
To workaround this, allow an environment variable to specify the edition. For example: TRACY_CLIENT_CPP_EDITION=gnu++14 cargo build
Note that since compilers seem to be resilient to badly formed editions, the implementation itself will check for correctness.

Note that since compilers seem to be resilient to badly formed editions, the implementation itself will check for correctness.

This seems pointlessly fragile.

You can now set the standard you want to use via the TRACY_CLIENT_SYS_CXXFLAGS environment variable.


Create authContext using useContext React Hook

Description

In order to make a 'global' react state, we need to provide all project through a react context

Prerequisites

create and configure AuthContext
provide it wrapping all the app react component
make a useAuth that gets a context to export

Additional Info

make it like our previous projects such as 'react-bombado'

PS: Label on hold doesn't exist, but it's an on hold pull request


Move src/helm-frontend to project root

Fixes #2198
Moves src/helm-frontend out of src. This fixes an issue where mypy checks all code under src, including Node modules installed at src/helm-frontend/node_modules which results in mypy errors like:
src/helm-frontend/node_modules/flatted/python/test.py:3:1: E302 expected 2 blank lines, found 1

I was keeping it as helm-frontend to follow the package name, but there isn't any requirement that the folder needs to follow the package name. I'll change it to just frontend.

Okay, actually there is a reason to keep it as "helm-frontend" - the string "helm-frontend" (only appears in this context) is more unique than "frontend" (appears in docs and other places), so this makes refactors easier in the future.


login prompt style params not listed in graph docs

Feature present and documented in Azure AD docs... present but NOT documented in MS Graph docs.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c6def816-86a6-e3ed-79e1-d7c9c747c205
Version Independent ID: 22553a1d-ec26-52c3-1e88-3e5648fef2a7
Content: Interactive request prompt behavior (MSAL.js) - Microsoft identity platform
Content Source: articles/active-directory/develop/msal-js-prompt-behavior.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: marsma

@gonsalvg
Thank you for your feedback!
When it comes to the login prompt style params not being listed within the Graph Docs, can you share what MS Graph Doc you're referring to? Additionally, can you share the example/enhancement you'd like to be made so I can gain a better understanding of your issue?
Thank you for your time and patience throughout this issue.

@gonsalvg
I just wanted to check in and see if you had the chance to review my previous comment?

https://docs.microsoft.com/en-us/graph/auth-v2-user this page is the one I am referring to. Otherwise it just doesn't seem to be mentioned in the graph docs.

@gonsalvg
Thank you for following up on this! I've created a PR to update the documentation and it's currently waiting for the author to review and sign off.
Since the doc you referenced isn't part of the Microsoft identity platform documentation, I'd  recommend creating a GitHub issue within the MS Graph Doc, so the respective author can investigate and update as needed.
I will now close out this issue. Please allow some time for the author to review and the changes to reflect.
Thank you for your time and patience!


⚠ ClamAV has degraded performance

In 94ce0bd, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in cba7c12.


Cannot disable laser red line

Description of the problem:
It's not properly a bug I know, but I please could indicate how to disable the laser red line? Moreover, is it possible to customize the view (ViewfinderView?) that contains the laser with a drawable background? I integrated the library via gradle
compile 'com.journeyapps:zxing-android-embedded:3.3.0@aar'
Thanks in advance!
Which library version are you using? E.g. 3.2.0.
3.3.0
Which phone/tablet are you using, and which Android version does it run? (e.g. Samsung Galaxy S5,
Android 5.0)
Samsung Galaxy S6 and any other device

You can do this if you write a custom Activity.
You can either override ViewfinderView with custom logic (see #73), or not use it at all - just use BarcodeView directly instead of DecoratedBarcodeView. You can see the source for DecoratedBarcodeView here: https://github.com/journeyapps/zxing-android-embedded/blob/master//zxing-android-embedded/src/com/journeyapps/barcodescanner/DecoratedBarcodeView.java - it doesn't do much more than combining the BarcodeView and ViewfinderView.


Feature: Add Three number sum in C++

https://leetcode.com/problems/3sum/

@akgmage assign this issue it to me please.

is this issue still open because i want to take this up

and @akgmage please close those issue which are already solved because it's hard to find unsolved issues.

and @akgmage please close those issue which are already solved because it's hard to find unsolved issues.

Thanks


type instead of @type in neurosciencegraph/core/data/v0.3.x

There is an error in neurosciencegraph/core/data/v0.3.x (compare links below): the property should be named "@type" instead of "type" - this is relevant since this makes everything that imports this context an invalid JSON-LD and prevents us from expanding the context.
https://github.com/INCF/neuroshapes/blob/c616bf796e11ba740ac8e869d98643f72586d0c6/modules/commons/src/main/resources/contexts/neurosciencegraph/core/data/v0.3.2.json#L11
https://github.com/INCF/neuroshapes/blob/c616bf796e11ba740ac8e869d98643f72586d0c6/modules/commons/src/main/resources/contexts/neurosciencegraph/core/data/v0.3.1.json#L11
https://github.com/INCF/neuroshapes/blob/c616bf796e11ba740ac8e869d98643f72586d0c6/modules/commons/src/main/resources/contexts/neurosciencegraph/core/data/v0.3.0.json#L11

Hi @olinux,
Thank you reporting this. We usually deprecate older version of a given resource (context, schema) and encourage users to move to latest versions. But I understand the issue here. So I'll fix it.


Which models can perform which of the five core calculations? Which don't? Standardize

Duplicate of #1


SSLHandshakeException when using Gigahorse Http Client to download dependencies requiring SSL Cert

[x] I've read the CONTRIBUTING guidelines

steps
Problem exists in all SBT 1.x but works in 0.13.x.
Add resolver / lib dependency to a private artifactory server which requires a custom SSL Certificate.
Update SBT_OPTS to include your SSL settings to be used for SSL Handshake with private repo:
-Djavax.net.ssl.keyStore=/path/to/cert.p12
-Djavax.net.ssl.keyStorePassword=<password>
-Djavax.net.ssl.keyStoreType=PKCS12
-Djavax.net.ssl.trustStore=/path/to/truststore
-Djavax.net.ssl.trustStorePassword=<password>

problem
SBT fails to resolve the dependency throwing an exception (I've used underscores ___ to hide the name of the private repo, but it should be possible to reproduce with any non standard SSL cert)
[error] sbt.librarymanagement.ResolveException: unresolved dependency: ___ Artifactory: unable to get resource for ___: res=___.pom: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
[error] 	at sbt.internal.librarymanagement.IvyActions$.resolveAndRetrieve(IvyActions.scala:332)
[error] 	at sbt.internal.librarymanagement.IvyActions$.$anonfun$updateEither$1(IvyActions.scala:208)
[error] 	at sbt.internal.librarymanagement.IvySbt$Module.$anonfun$withModule$1(Ivy.scala:239)
[error] 	at sbt.internal.librarymanagement.IvySbt.$anonfun$withIvy$1(Ivy.scala:204)
[error] 	at sbt.internal.librarymanagement.IvySbt.sbt$internal$librarymanagement$IvySbt$$action$1(Ivy.scala:70)
[error] 	at sbt.internal.librarymanagement.IvySbt$$anon$3.call(Ivy.scala:77)
[error] 	at xsbt.boot.Locks$GlobalLock.withChannel$1(Locks.scala:95)
[error] 	at xsbt.boot.Locks$GlobalLock.xsbt$boot$Locks$GlobalLock$$withChannelRetries$1(Locks.scala:80)
[error] 	at xsbt.boot.Locks$GlobalLock$$anonfun$withFileLock$1.apply(Locks.scala:99)
[error] 	at xsbt.boot.Using$.withResource(Using.scala:10)
[error] 	at xsbt.boot.Using$.apply(Using.scala:9)
[error] 	at xsbt.boot.Locks$GlobalLock.ignoringDeadlockAvoided(Locks.scala:60)
[error] 	at xsbt.boot.Locks$GlobalLock.withLock(Locks.scala:50)
[error] 	at xsbt.boot.Locks$.apply0(Locks.scala:31)
[error] 	at xsbt.boot.Locks$.apply(Locks.scala:28)
[error] 	at sbt.internal.librarymanagement.IvySbt.withDefaultLogger(Ivy.scala:77)
[error] 	at sbt.internal.librarymanagement.IvySbt.withIvy(Ivy.scala:199)
[error] 	at sbt.internal.librarymanagement.IvySbt.withIvy(Ivy.scala:196)
[error] 	at sbt.internal.librarymanagement.IvySbt$Module.withModule(Ivy.scala:238)
[error] 	at sbt.internal.librarymanagement.IvyActions$.updateEither(IvyActions.scala:193)
[error] 	at sbt.librarymanagement.ivy.IvyDependencyResolution.update(IvyDependencyResolution.scala:20)
[error] 	at sbt.librarymanagement.DependencyResolution.update(DependencyResolution.scala:56)

expectation
Should be able to resolve and download the dependency.
notes
Disabling Gigahorse via SBT setting fixes the issue:
updateOptions := updateOptions.value.withGigahorse(false)

Seems like Gigahorse doesn't honour SSL settings.
sbt version: 1.2.8 (although problem exists on all 1.x)

@LukeDeighton Thanks for the report.
Potentially related https://github.com/square/okhttp/issues/1711#issuecomment-194092912.

Hi, I just want to confirm that we have faced the same issue when resolving dependencies from a repository requiring a client certificate. Disabling Gigahorse resolves it for now. 👍
Are there any major drawbacks in disabling Gigahorse? I have not found a possibility to use the default SSL context in the underlying okhttp client or at least adhere to the jvm system properties.

Closing this since sbt 1.3.x now uses Coursier.
Let me know if this is still relevant.


Setting Azure AD Application Publisher Domain through API.

Hi all,
In reference to issue 42454 any updates on this?
Setting publisher domain programmatically should be made available considering a method to set Publisher Verification (MPN ID) is.
Considering the above steps should be done on any multi-tenant app it needs to be available to set programmatically.
Thank you.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 61edea45-b5d6-05b3-33c3-2265ef8cb309
Version Independent ID: c7d5813c-5cf1-44c3-88ff-3c194d3e44ad
Content: Configure an app's publisher domain - Microsoft identity platform
Content Source: articles/active-directory/develop/howto-configure-publisher-domain.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@thomasonsignup  I confirmed with our engineering team- there are no plans to support setting publisher domain programmatically.  Sorry, I know that's not the answer you want to hear.  I'm closing this issue now, feel free to re-open if need be.  #please-close

Sorry for resurrecting an old issue, but @rwike77, do you know why this isn't planned? Is it just not being prioritised, or will it never be implemented? There are a few issues on here about this, but none of them includes that info AFAICT. It's possible to change the publisher domain in the Azure Portal by navigating to App registrations > [Some app] > Branding & properties and selecting "Update domain", so it's not completely read-only.


Error "Object argument required."

In one of the more recent versions of the Serverless Framework, it appears that something changed that causes this plugin to throw an error.
Error shows up in Serverless version 1.26.1
I'll see if I can dig in some more when I get some free time.

@Sector95 Thank you for reporting this issue. Can you execute the deploy command with SLS_DEBUG=* and share the output here?

Here's the stack trace:
Error: Object argument required.
    at applyDefaults (/usr/local/lib/node_modules/serverless/node_modules/object-hash/index.js:79:11)
    at objectHash (/usr/local/lib/node_modules/serverless/node_modules/object-hash/index.js:31:13)
    at Function.exports.sha1 (/usr/local/lib/node_modules/serverless/node_modules/object-hash/index.js:44:10)
    at AwsProvider.request (/usr/local/lib/node_modules/serverless/lib/plugins/aws/provider/awsProvider.js:202:35)
    at CreateBasePathMappingService._getRestApiInfo (/home/circleci/project/node_modules/serverless-base-path-mapping/create-base-path-mapping-service.js:55:25)
    at CreateBasePathMappingService._createBasePathMapping (/home/circleci/project/node_modules/serverless-base-path-mapping/create-base-path-mapping-service.js:42:15)
    at _getMappingInfo.then.mappingInfo (/home/circleci/project/node_modules/serverless-base-path-mapping/create-base-path-mapping-service.js:22:18)
From previous event:
    at CreateBasePathMappingService.createBasePathMapping (/home/circleci/project/node_modules/serverless-base-path-mapping/create-base-path-mapping-service.js:19:5)
    at BasePathMappingPlugin._beforeDeploy (/home/circleci/project/node_modules/serverless-base-path-mapping/index.js:17:39)
    at BbPromise.reduce (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:372:55)
From previous event:
    at PluginManager.invoke (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:372:22)
    at PluginManager.run (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:403:17)
    at variables.populateService.then (/usr/local/lib/node_modules/serverless/lib/Serverless.js:102:33)
    at runCallback (timers.js:794:20)
    at tryOnImmediate (timers.js:752:5)
    at processImmediate [as _immediateCallback] (timers.js:729:5)
From previous event:
    at Serverless.run (/usr/local/lib/node_modules/serverless/lib/Serverless.js:89:74)
    at serverless.init.then (/usr/local/lib/node_modules/serverless/bin/serverless:42:50)
    at <anonymous>

@Sector95 Thank you for the stack trace. I found the problem. The fix is released in version 0.1.1


hotfix Update vcredist2022 version info

Closes #XXXX

Relates to #XXXX

[x] I have read the Contributing Guide.

Is there a way we can automatically get the latest version number rather than manually updating it?

Sorry, I don't know how to implement it, I'm a rookie in this Scoop project.
But I feel that the Scoop script is very difficult to implement for vcredist2022's auto-update because the usual solution is not feasible.
Because "autoupdate": usually requires a static URL and $version information in the package name, but the vcredist2022 package does not have either of these features.
I just modified it manually according to the previous update method.

Just a hotfix for #8732 Please merge at your convenience ^^ @issaclin32 @tech189

I am changing version to 14.32.31326 .0 according to the file version.


Windows Pearl icons is default Electron icon

Need to ensure Windows icon is set in Electron build script.
Currently only Mac config has this defined.

Next steps

Include icons in the Build process for Windows. (Requires Windows merge to staging)

was fix in #335


Path normalization

Windows path notation style must be converted to Unix path notation style when uploading from Windows machines.
Example:
{
  "type": "sftp",
  "host": "***",
  "user": "***",
  "password": "***",
  "port": "22",
  "remote_path": "~/test"
}

Uploading a test file then creates this directory structure.
~                     (home directory)
|
+-- ~test             (directory)
+-- ~\test\mytestfile (file)

The expected behaviour would be:
~                     (home directory)
|
+-- test              (directory)
    |
    +-- mytestfile    (file)

Hi guys,
Sorry for the long period of inactivity.
We are currently working on a new version : better code, more stable, and bug fixes.
This bug will be fixed at the next release.
Thank you for using our work ! :)

Hi guys,
A new version (1.0.0) was published tonight.
Feel free to reopen if the problem is still there.
Enjoy ! :D


Localization for Markdown Activity

There is currently no attempt at localizing any of the text in the Markdown Activity.
Specifically, the following files have hardcoded text on them:
https://github.com/llaske/sugarizer/blob/master/activities/Markdown.activity/lib/Markdown.Editor.js
https://github.com/llaske/sugarizer/blob/6c8472c2aa95b978cb45eabfe16f3c0c64ff1e60/activities/Markdown.activity/js/activity.js
I would like to request that these files be changed to allow for localization, since most other activities (and sugarizer itself) already allow this.

Fixed in https://github.com/llaske/sugarizer/commit/c8163c6f907a5901723fb275519d074fa5e8a123

Fixed in https://github.com/llaske/sugarizer/releases/tag/v0.8


Fix test suite and limit resources consumed

I've looked closely at the test suite and saw some potential issues. This PR should make it more reliable to pass. Using smallfiles then prevents to fail just because of little disc space.

Thanks @omron93, I've reverted the unnecessary changes of SMALLFILES and did the proposed change with CONTAINER_IP.

Thanks @hhorak
LGTM

LGTM


Modify queue-master service to use pool of containers

Currently queue-master spawns containers via docker API, but in some cases (Mesos!!) this is not possible. Alternative is to have a pool of workers to use instead.

N/A. Removing workers soon. https://github.com/microservices-demo/queue-master.


adding time-compare intent and test file for it along with the data file

Overall logic looks good.


Sdp test

Docs Build status updates of commit 7d6aea7:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/TianqiZhang/ref102, working directory: W:\lffb-s, target branch: master, target branch commit: 302105173e1dcdb66f2ea24f62185b69cb0abd14, source commit: 7d6aea79cc26c629adfefbc494b7d972f7061aea.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit dd488dd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit e248eef:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

ref102/xml/index.xml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit fe2e1b7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

ref102/api/CatLibrary.Cat-2.Age.yml
:warning:Warning

Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

ref102/xml/index.xml
:white_check_mark:Succeeded

ref102/api/CatLibrary.Cat-2.Age.yml

Line 1: [Warning] Invalid file link:(~/api/cc3e540b-63b0-4edf-b0c0-69c38f3795d3).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 85f7f2d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

ref102/api/CatLibrary.Cat-2.Age.yml
:warning:Warning

Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

ref102/xml/index.xml
:white_check_mark:Succeeded

ref102/api/CatLibrary.Cat-2.Age.yml

Line 1: [Warning] Invalid file link:(~/api/cc3e540b-63b0-4edf-b0c0-69c38f3795d3).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@TianqiZhang

@TianqiZhang

Docs Build status updates of commit 9d0d826:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/TianqiZhang/ref102, working directory: W:\oltb-s, target branch: HEAD, target branch commit: 3eb6a6355dfbc708ebe437908751a0500d5eedca, source commit: 9d0d8266015114dbf2a31de2d0f54e020a6a487d.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 9d0d826:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/TianqiZhang/ref102, working directory: W:\5yw1-s, target branch: HEAD, target branch commit: 3aaba0e145ac7a41d128da05493010f1eb69604b, source commit: 9d0d8266015114dbf2a31de2d0f54e020a6a487d.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 9e56ced:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:x:Error

Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset ref102. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset ref102 step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

[Error] Failed to load 1 files, aborting...
Line 138: [Error] W:\5b02-s\.optemp\packages\opbuild.scripts.1.81.1\tools\opbuild\docset.prebuild.ps1 failed to execute

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Socket Programming in C#

Proposed title of article
Socket Programming in C#
Proposed article introduction
In this article, First, we'll look at how to build a C# socket and set up a listener server node that begins listening for messages sent to it through the IP and protocol specified. We'll also show how to use Sockets to develop a client application that sends messages to a listening server and reads them.
Sockets are used in computer networks to create a connection between two or more machines and to transport data from one to the other.
Key takeaways
What is socket programming?
How to create a socket
setup a listener server node
create a client application
Test and Run  the two projects
Article quality
How is your article unique? Tell us what makes your approach different from similar articles that have published on the same topic?
Is yours more in-depth? Does it cover additional topics? Do you provide handy tips or anecdotal advice?
References
N/A

Hello @Nicholas-Obare, how is your topic going to be different from this one?

Hello@Kayere,my topic will be more detailed with the good and clear examples .

I think this topic is over saturated. Feel free to suggest another area. Thanks


Add React to an Existing Project page translated to Telugu

Hello @g-savitha, @gsteja2307 and @vamsikrishnareddybevara
I have translated the entire page of Add React to an Existing Project to Telugu by following the Telugu Glossary and other guidelines provided.
Please carefully review the translated content, and merge it ASAP because I'm eager to translate other pages also but as mentioned in #1 "Please take only one page at a time".
Merging this PR will close #10
Thank you :)

Please add me as one of the maintainers, I have experience with React and have completed many projects using it.
Check them on my profile @srikanth-kandi and my certifications mentioned in LinkedIn
@g-savitha @gsteja2307
According to the guidelines about Adding a Maintainer mentioned in translations.react.dev, if any of the maintainers like @vamsikrishnareddybevara isn't active on this repository for the last 3 months or so. They need to be replaced by others.
So I hope you consider adding me as another maintainer for this repository.

Hello @g-savitha please review this pull request, as I'm also working on another page, so if PR was merged I can send another pull request of that translated page.

thanks for your effort on translating the project to Telugu. I noticed some sentences seem to be directly translated, which may not align with the contextual meaning in Telugu. Could you please review the translation for grammatical accuracy and context sensitivity? It's important that the translated content maintains the original message and flows naturally in Telugu. A thorough proofreading would be greatly appreciated. Thanks!

Hello @g-savitha, @gsteja2307 and @vamsikrishnareddybevara
I have translated the entire page of Add React to an Existing Project to Telugu by following the Telugu Glossary and other guidelines provided.
Please carefully review the translated content, and merge it ASAP because I'm eager to translate other pages also but as mentioned in #1 "Please take only one page at a time".
Merging this PR will close #10
Thank you :)

Appreciate your work on the Telugu translation of this page. I've noticed certain phrases seem directly translated, potentially losing the intended meaning in Telugu. Please recheck for grammatical and contextual accuracy. Ensuring that the translation accurately conveys the original message and reads naturally in Telugu is crucial.
Detailed proofreading would be very helpful. Thanks!
I've provided some examples in the PR review. Please ensure a comprehensive check before finalizing your changes. Additionally, be cautious with text in square brackets, typically links, to preserve context. If feasible, also update the linked titles for clarity and relevance.

Comments need not to be updated, as these will not be shown to end user.

But as mentioned in this style-guide Leave text in code blocks untranslated except for comments
So if we translate the comments of code blocks to Telugu it can help easily understand the purpose of that code block for a newbie.
@g-savitha

Can anyone review this PR
@g-savitha @gsteja2307

Please add me as one of the maintainers, I have experience with React and have completed many projects using it. Check them on my profile @srikanth-kandi and my certifications mentioned in LinkedIn
@g-savitha @gsteja2307
According to the guidelines about Adding a Maintainer mentioned in translations.react.dev, if any of the maintainers like @vamsikrishnareddybevara isn't active on this repository for the last 3 months or so. They need to be replaced by others.
So I hope you consider adding me as another maintainer for this repository.

You guys didn't consider making me a maintainer, and you are also not responding to the contributions.
Consider responding to this repository updates by sparing at least some time a day 🙏
@g-savitha @gsteja2307

Hey @g-savitha and @gsteja2307
Please review this and my existing pull requests, I requested you make me a maintainer on #1. Otherwise, add some other maintainers you know who will actively monitor the contributions on this repository.
Waiting for your response.


Deletion of increment method

Change made
Deletion of increment method in main.dart file

Hi @alabiboo this PR was deleted due to the merge conflict as a lot of changes has been made on the base branch that you need to pull to your fork copy.
Take note that we are still setting up the repository structure to make it easy for contributing.
Once setup all PR will be welcome for a review and merge.
Thank you for contributing!!!


Python test scripts validator

Create script
How to run:
1 - Start backend container in dev mode
2 - Go to backend folder
3 - run: ./test_collections/matter/scripts/validate_sdk_python_tests_scripts.sh [OPTIONAL_SDK_SHA]

Some erros detect on parsing

Categorized scripts after parsing

Log file created: /tmp/SDKPythonTestValidation-SDK_SHA.txt

@hiltonlima, can you provide a description on what is being validated and what the motivation for this feature is?

@hiltonlima, can you provide a description on what is being validated and what the motivation for this feature is?

Sure, please check the PR description.