Change how analytics variables are passed

What
Change how variables for the ga property and cross domain tracking configuration are passed to the analyticsInit function.
Why
A previous change passed these variables to the analyticsInit function so that different applications could use different configurations. Turned out that this approach didn't work with the cookie banner, because it also calls the same function as part of its internal code, and can't access those variables.
Passing these variables from an application into multiple places is too complicated, so the solution is to define the variables as attached to the GOVUK object, so they can be referenced from anywhere in the code.
This requires some tweaks to the tests to make them pass correctly. There are still some issues with the tests that will be addressed prior to the big static move, ecommerce spec is creating errors Cannot read property 'gaClientId' of undefined that are only visible in the console if tests are run headless with GA tracking shown, doesn't actually cause a test failure but needs addressing.
Visual Changes
None.

Thanks @alex-ju. I've created this card in our roadmap https://trello.com/c/epZ12grR/110-migrate-analytics-code-into-the-gem to include your note, and also because I realised we aren't tracking this piece of work properly yet. Feel free to add anything else I might have missed.


Why is the GPU KV cache usage very low?

Your current environment
PyTorch version: 2.3.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.4 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.26.3
Libc version: glibc-2.31

Python version: 3.9.12 (main, Apr  5 2022, 06:56:58)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.10.0-<IP_ADDRESS>.oe2203sp3.x86_64-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: 12.2.91
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA L20
GPU 1: NVIDIA L20

Nvidia driver version: 535.154.05
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.2.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.2.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.2.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.2.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.2.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.2.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.2.0
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
架构：                              x86_64
CPU 运行模式：                      32-bit, 64-bit
字节序：                            Little Endian
Address sizes:                      46 bits physical, 57 bits virtual
CPU:                                104
在线 CPU 列表：                     0-103
每个核的线程数：                    2
每个座的核数：                      26
座：                                2
NUMA 节点：                         2
厂商 ID：                           GenuineIntel
CPU 系列：                          6
型号：                              106
型号名称：                          Intel(R) Xeon(R) Gold 5320 CPU @ 2.20GHz
步进：                              6
CPU MHz：                           2800.273
CPU 最大 MHz：                      3400.0000
CPU 最小 MHz：                      800.0000
BogoMIPS：                          4400.00
虚拟化：                            VT-x
L1d 缓存：                          2.4 MiB
L1i 缓存：                          1.6 MiB
L2 缓存：                           65 MiB
L3 缓存：                           78 MiB
NUMA 节点0 CPU：                    0-25,52-77
NUMA 节点1 CPU：                    26-51,78-103
Vulnerability Gather data sampling: Vulnerable: No microcode
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: 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:           Vulnerable: eIBRS with unprivileged eBPF
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected
标记：                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 invpcid_single intel_ppin ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect wbnoinvd dtherm ida arat pln pts avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid fsrm md_clear pconfig flush_l1d arch_capabilities

Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.22.3
[pip3] nvidia-nccl-cu11==2.14.3
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] torch==2.3.0
[pip3] torchaudio==0.12.1
[pip3] torchinfo==1.7.2
[pip3] torchvision==0.13.1
[pip3] transformers==4.41.2
[pip3] transformers-stream-generator==0.0.4
[pip3] triton==2.3.0
[conda] blas                      1.0                         mkl
[conda] cudatoolkit               11.3.1               h2bc3f7f_2
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640
[conda] mkl-service               2.4.0            py39h7f8727e_0
[conda] mkl_fft                   1.3.1            py39hd3c417c_0
[conda] mkl_random                1.2.2            py39h51133e4_0
[conda] numpy                     1.22.3           py39he7a7128_0
[conda] numpy-base                1.22.3           py39hf524024_0
[conda] nvidia-nccl-cu11          2.14.3                   pypi_0    pypi
[conda] nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torch                     2.3.0                    pypi_0    pypi
[conda] torchaudio                0.12.1               py39_cu113    pytorch
[conda] torchinfo                 1.7.2                    pypi_0    pypi
[conda] torchvision               0.13.1               py39_cu113    pytorch
[conda] transformers              4.41.2                   pypi_0    pypi
[conda] transformers-stream-generator 0.0.4                    pypi_0    pypi
[conda] triton                    2.3.0                    pypi_0    pypi
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.4.3
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      SYS     0-25,52-77      0               N/A
GPU1    SYS      X      26-51,78-103    1               N/A

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

How would you like to use vllm
1.Model size: 14B
2.Performance: Average prompt throughput: 120.1 tokens/s, average generation throughput: 41.9 tokens/s, running: 1 request, swapped: 0 requests, pending: 0 requests, GPU KV cache usage: 1.0%, CPU KV cache usage: 0.0%.
The generation throughput speed is too slow. I think the reason might be the low GPU KV cache usage. How can I increase the GPU KV cache usage and improve the generation throughput speed?

If you're only running 1 request, your KV Cache is unlikely to be filled up. If you want to improve generation speed you can consider using FP8 or speculation


Not installing on Windows 11 Installed in parallels on M1 mac

I am getting a bunch of errors and its actually not installing but SSMS is installed, and I thought it. has installed but could not login.  So I uninstalled and reinstalled and keep getting the error
Directory: C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL
Mode                 LastWriteTime         Length Name

d-----        10/28/2023   5:01 PM                Log
d-----        10/28/2023   5:01 PM                DATA
Exception calling "SetAccessRule" with "1" argument(s): "Some or all identity references could not be translated."
At C:\Users\christimm\Downloads\MSSQLEXPRESS-M1-Install-main\src\install2022Express.ps1:98 char:1

$acl.SetAccessRule($accessRule)

  + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
  + FullyQualifiedErrorId : IdentityNotMappedException

Exception calling "SetAccessRule" with "1" argument(s): "Some or all identity references could not be translated."
At C:\Users\christimm\Downloads\MSSQLEXPRESS-M1-Install-main\src\install2022Express.ps1:103 char:1

$acl.SetAccessRule($accessRule)

  + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
  + FullyQualifiedErrorId : IdentityNotMappedException

Copy-Item : Cannot find path 'C:\Program Files\Microsoft SQL
Server\MSSQL16.SQLEXPRESS\MSSQL\Binn\Templates\master.mdf' because it does not exist.
At C:\Users\christimm\Downloads\MSSQLEXPRESS-M1-Install-main\src\install2022Express.ps1:120 char:1

Copy-Item -Path "$installedPath\Binn\Templates\master.mdf" -Destinati ...

  + CategoryInfo          : ObjectNotFound: (C:\Program File...ates\master.mdf:String) [Copy-Item], ItemNotFoundExce
 ption
  + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

Copy-Item : Cannot find path 'C:\Program Files\Microsoft SQL
Server\MSSQL16.SQLEXPRESS\MSSQL\Binn\Templates\mastlog.ldf' because it does not exist.
At C:\Users\christimm\Downloads\MSSQLEXPRESS-M1-Install-main\src\install2022Express.ps1:121 char:1

Copy-Item -Path "$installedPath\Binn\Templates\mastlog.ldf" -Destinat ...

  + CategoryInfo          : ObjectNotFound: (C:\Program File...tes\mastlog.ldf:String) [Copy-Item], ItemNotFoundExce
 ption

Are you using the batch file from an elevated command prompt to install SQL using these scripts or running the PowerShell scripts using PowerShell or PowerShell ISE? I had no issues with the scripts but ran the batch files from an elevated command prompt and got all editions to install using the scripts (2019 Express, 2019 Developer, 2022 Express and 2022 Developer). Which version have you tried installing?

Should be fixed using the new installers or scripts.


Update Project.toml

Pull Request Test Coverage Report for Build 507502747

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+2.2%) to 45.334%

Files with Coverage Reduction
New Missed Lines
%

src/Algorithms/BOX/reach_homog.jl
1
37.5%

src/Algorithms/TMJets/reach.jl
2
93.99%

Totals

Change from base Build 507281888:
2.2%

Covered Lines:
2055

Relevant Lines:
4533

💛  - Coveralls

Pull Request Test Coverage Report for Build 507502747

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+2.2%) to 45.334%

Files with Coverage Reduction
New Missed Lines
%

src/Algorithms/BOX/reach_homog.jl
1
37.5%

src/Algorithms/TMJets/reach.jl
2
93.99%

Totals

Change from base Build 507281888:
2.2%

Covered Lines:
2055

Relevant Lines:
4533

💛  - Coveralls


[FS] Logging for FederationWalletSyncManager inside AsyncProvider

I don't expect it to keep running, let see what that is producing
Anyway I don't think you need the wrapper, you can surround OnProcessBlockAsync code with that try/catch


Release update problem

@EmileRolley it looks like the yarn run check:releases calls a non existent file.
It looks to me that it would suffice to just change the output of the fetch-release function to output the french source releases to the locales dir.
Am I missing something ?

It's weird the check-releases.js file dispeared :thinking:
But, yeah it only misses to directly save the fetched releases in the source/locale/releases/releases-fr.json file.


Use ponyc 0.25.0

In the interest of reaping the benefits of ponyc 0.25 as soon as possible, this PR:

Adapts wallaroo code to conform to new ponyc APIs (minor changes)
Uses a wallaroo-ci docker image with the ponyc 0.25 compiler
Puts in place 0.25 support in wallaroo-up.sh
Uses the 0.25 compiler in the vagrant release box

@pzel looks like the tests are passing but I'm not sure if we want the default Wallaroo version in the wallaroo-up script to be this branch. thoughts on how to properly go about this @dipinhora ?

@JONBRWN the wallaroo-up changes are not tied to a branch. They're a mini hack to get wallaroo-up to use ponyc version 0.25.0. The new default will get overridden during the next release/rc process (and should not impact anyone in the meantime because to my knowledge nobody runs wallaroo-up directly from master). Also, the version added to the map doesn't tie itself to a branch. It is a string added to a url to try and download files from bintray but that functionality gets overridden during the testing to use the local source tree instead.

@dipinhora ok thanks. just wanted to confirm that the changes wouldn't cause it to attempt to use this branch once merged to master, looks good to me then


[Question] Doesn't work with Reanimated?

Hi,
I am trying to use useAnimatedProps from react-native-reanimated to your StrokeText but it doesn't update when the prop's value updates once the StrokeText is initialized. It does take the initial value from the same hook so I know the hook is providing the initial prop value but StrokeText doesn't rerender on subsequent new props. I can provide a codesandbox link if needed. Any ideas?
Some context:
AnimatedStrokeText component so that reanimated is able to provide props to it.
import { StrokeText } from<EMAIL_ADDRESS>import { forwardRef } from "react";
import Animated from "react-native-reanimated";

export const AnimatedStrokeText = Animated.createAnimatedComponent(
  forwardRef(StrokeText),
);

The useAnimatedProps hook
const strokeWidthProps = useAnimatedProps(() => {
  const strokeWidth = interpolate(
    Easing.linear(timer.value),
    [
      0,
      200,
      1000,
      2000,
    ],
    [1, 1, 3, 3],
    Extrapolation.CLAMP,
  );

  return {
    strokeWidth,
  };
}

The usage:
<AnimatedStrokeText
  text="Hello World"
  fontSize={20}
  color="#00FF00"
  strokeColor="#000000"
  fontFamily="Arial Rounded MT Bold"
  animatedProps={strokeWidthProps}
/>

I have tested similar code on a simple text and it works but not with StrokeText. Let me know if you know why

Have fun 🎉
https://github.com/charmy/react-native-stroke-text/releases/tag/1.0.8
I recommend to use width prop to animate like that, when strokeWidth changed, calculates the width again so might cause flicker.
In the video on the right side, the width prop is not set, so it flickers.
https://github.com/charmy/react-native-stroke-text/assets/13810383/33af0001-b095-4a2f-a43b-2dcb82d5e356

Thanks it works great with strokeWidth & strokeColor. I think color prop still doesn't take in changes. Can you make the same change for color prop?


[Performance]: Performance degradation due to CPU bottleneck when serving embedding models to GPUs

Proposal to improve performance
When you serve your Embedding model to the GPU and load it up, you hit a throughput bottleneck due to CPU bottlenecks.
Here are the arguments we set up to serve the model.
      - --model
      - /data/models/bge-m3-embed-beta1
      - --load-format
      - "auto"
      - --dtype
      - "float16"
      - --max-num-batched-tokens
      - "131072"
      - --tokenizer-pool-size
      - "4"

We increased the number of users by 1 every 10 seconds, with each user sending a request to /v1/embeddings once every 0.5 seconds. (Number of prompt tokens: 3K)
In our tests, the throughput increased up to 12TPS, and then did not increase after that. It is not clear what the cause is, but the CPU utilization of the python process reaches 100% when the bottleneck is reached.

top - 21:52:19 up 23 days, 20:08,  0 users,  load average: 2.05, 2.53, 2.57
Tasks:   5 total,   3 running,   2 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1.6 us,  0.2 sy,  0.0 ni, 98.2 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem : 2063755.+total, 1418614.+free,  59389.1 used, 585751.8 buff/cache
MiB Swap:      0.0 total,      0.0 free,      0.0 used. 1987294.+avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
     77 root      20   0   33.7g   1.5g 194492 R **101.4**   0.1  15:27.44 **python3**

It seems that the CPU is causing the bottleneck.
Is there any way I can try to profile the above process in detail?
Report of performance regression
No response
Misc discussion on performance
No response
Your current environment (if you think it is necessary)
Collecting environment information...

[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.

You can try increasing tokenizer-pool-size to see if it can improve performance.

I guess it may be the tokenizer that causes the CPU performance bottleneck
You can try increasing tokenizer-pool-size to see if it can improve performance.

I thought it was because of the tokenizer too.  But even without tokenizer-pool-size option, the result is same.

You can try use prompt_token_ids as input to bypass the tokenizer
If bottleneck is still there, it may be bound by webserver performance.
Even if the webserver uses async, it may actually run on one python process. This may lead to bottlenecks

PTAL https://docs.vllm.ai/en/latest/contributing/profiling/profiling_index.html

I followed the instructions but nothing left in profile directory.
WARNING 12-19 19:52:24 api_server.py:394] Torch Profiler is enabled in the API server. This should ONLY be used for local development!
INFO 12-19 19:52:24 api_server.py:585] vLLM API server version 0.6.4.post1
INFO 12-19 19:52:24 api_server.py:586] args: Namespace(host=None, port=8000, uvicorn_log_level='warning', allow_credentials=False, allowed_origins=['*'], allowed_methods=['*'], allowed_headers=['*'], api_key=None, lora_modules=None, prompt_adapters=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=[], return_tokens_as_token_ids=False, disable_frontend_multiprocessing=False, enable_auto_tool_choice=False, tool_call_parser=None, tool_parser_plugin='', model='/data/models/bge-m3-embed-beta1', task='auto', tokenizer=None, skip_tokenizer_init=False, revision=None, code_revision=None, tokenizer_revision=None, tokenizer_mode='auto', chat_template_text_format='string', trust_remote_code=False, allowed_local_media_path=None, download_dir=None, load_format='auto', config_format=<ConfigFormat.AUTO: 'auto'>, dtype='float16', kv_cache_dtype='auto', quantization_param_path=None, max_model_len=None, guided_decoding_backend='outlines', distributed_executor_backend=None, worker_use_ray=False, 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, disable_sliding_window=False, use_v2_block_manager=False, num_lookahead_slots=0, seed=0, swap_space=4, cpu_offload_gb=0, gpu_memory_utilization=0.5, num_gpu_blocks_override=None, max_num_batched_tokens=131072, max_num_seqs=256, max_logprobs=20, disable_log_stats=False, quantization=None, rope_scaling=None, rope_theta=None, hf_overrides=None, enforce_eager=False, max_seq_len_to_capture=8192, disable_custom_all_reduce=False, tokenizer_pool_size=0, tokenizer_pool_type='ray', tokenizer_pool_extra_config=None, limit_mm_per_prompt=None, mm_processor_kwargs=None, enable_lora=False, enable_lora_bias=False, max_loras=1, max_lora_rank=16, lora_extra_vocab_size=256, lora_dtype='auto', long_lora_scaling_factors=None, max_cpu_loras=None, fully_sharded_loras=False, enable_prompt_adapter=False, max_prompt_adapters=1, max_prompt_adapter_token=0, device='auto', num_scheduler_steps=1, multi_step_stream_outputs=True, scheduler_delay_factor=0.0, enable_chunked_prefill=None, speculative_model=None, speculative_model_quantization=None, num_speculative_tokens=None, speculative_disable_mqa_scorer=False, speculative_draft_tensor_parallel_size=None, speculative_max_model_len=None, speculative_disable_by_batch_size=None, ngram_prompt_lookup_max=None, ngram_prompt_lookup_min=None, spec_decoding_acceptance_method='rejection_sampler', typical_acceptance_sampler_posterior_threshold=None, typical_acceptance_sampler_posterior_alpha=None, disable_logprobs_during_spec_decoding=None, model_loader_extra_config=None, ignore_patterns=[], preemption_mode=None, served_model_name=['bge-m3-embed-beta1'], qlora_adapter_name_or_path=None, otlp_traces_endpoint=None, collect_detailed_traces=None, disable_async_output_proc=False, scheduling_policy='fcfs', override_neuron_config=None, override_pooler_config=PoolerConfig(pooling_type='CLS', normalize=False, softmax=False, step_tag_id=None, returned_token_ids=None), disable_log_requests=True, max_log_len=None, disable_fastapi_docs=False, enable_prompt_tokens_details=False)
INFO 12-19 19:52:24 api_server.py:175] Multiprocessing frontend to use ipc:///tmp/7f3f58d5-853a-4166-9dfa-bde616442a05 for IPC Path.
INFO 12-19 19:52:24 api_server.py:194] Started engine process with PID 77
INFO 12-19 19:52:24 config.py:1861] Downcasting torch.float32 to torch.float16.
WARNING 12-19 19:52:27 api_server.py:394] Torch Profiler is enabled in the API server. This should ONLY be used for local development!
INFO 12-19 19:52:27 config.py:1861] Downcasting torch.float32 to torch.float16.
WARNING 12-19 19:52:28 arg_utils.py:1075] [DEPRECATED] Block manager v1 has been removed, and setting --use-v2-block-manager to True or False has no effect on vLLM behavior. Please remove --use-v2-block-manager in your engine argument. If your use case is not supported by SelfAttnBlockSpaceManager (i.e. block manager v2), please file an issue with detailed information.
WARNING 12-19 19:52:31 arg_utils.py:1075] [DEPRECATED] Block manager v1 has been removed, and setting --use-v2-block-manager to True or False has no effect on vLLM behavior. Please remove --use-v2-block-manager in your engine argument. If your use case is not supported by SelfAttnBlockSpaceManager (i.e. block manager v2), please file an issue with detailed information.
INFO 12-19 19:52:31 llm_engine.py:249] Initializing an LLM engine (v0.6.4.post1) with config: model='/data/models/bge-m3-embed-beta1', speculative_config=None, tokenizer='/data/models/bge-m3-embed-beta1', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, override_neuron_config=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.float16, 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=None, 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=bge-m3-embed-beta1, num_scheduler_steps=1, chunked_prefill_enabled=False multi_step_stream_outputs=True, enable_prefix_caching=False, use_async_output_proc=False, use_cached_outputs=True, chat_template_text_format=string, mm_processor_kwargs=None, pooler_config=PoolerConfig(pooling_type='CLS', normalize=False, softmax=False, step_tag_id=None, returned_token_ids=None))
INFO 12-19 19:52:32 selector.py:135] Using Flash Attention backend.
INFO 12-19 19:52:32 worker.py:99] Profiling enabled. Traces will be saved to: /data/profile/
INFO 12-19 19:52:32 model_runner.py:1072] Starting to load model /data/models/bge-m3-embed-beta1...
Loading safetensors checkpoint shards:   0% Completed | 0/1 [00:00<?, ?it/s]
Loading safetensors checkpoint shards: 100% Completed | 1/1 [00:21<00:00, 21.14s/it]
Loading safetensors checkpoint shards: 100% Completed | 1/1 [00:21<00:00, 21.14s/it]

INFO 12-19 19:52:54 model_runner.py:1077] Loading model weights took 1.0557 GB
INFO 12-19 19:52:54 api_server.py:249] vLLM to use /tmp/tmp741vmqv8 as PROMETHEUS_MULTIPROC_DIR
INFO 12-19 19:52:54 launcher.py:19] Available routes are:
INFO 12-19 19:52:54 launcher.py:27] Route: /openapi.json, Methods: HEAD, GET
INFO 12-19 19:52:54 launcher.py:27] Route: /docs, Methods: HEAD, GET
INFO 12-19 19:52:54 launcher.py:27] Route: /docs/oauth2-redirect, Methods: HEAD, GET
INFO 12-19 19:52:54 launcher.py:27] Route: /redoc, Methods: HEAD, GET
INFO 12-19 19:52:54 launcher.py:27] Route: /health, Methods: GET
INFO 12-19 19:52:54 launcher.py:27] Route: /tokenize, Methods: POST
INFO 12-19 19:52:54 launcher.py:27] Route: /detokenize, Methods: POST
INFO 12-19 19:52:54 launcher.py:27] Route: /v1/models, Methods: GET
INFO 12-19 19:52:54 launcher.py:27] Route: /version, Methods: GET
INFO 12-19 19:52:54 launcher.py:27] Route: /v1/chat/completions, Methods: POST
INFO 12-19 19:52:54 launcher.py:27] Route: /v1/completions, Methods: POST
INFO 12-19 19:52:54 launcher.py:27] Route: /v1/embeddings, Methods: POST
INFO 12-19 19:52:54 launcher.py:27] Route: /start_profile, Methods: POST
INFO 12-19 19:52:54 launcher.py:27] Route: /stop_profile, Methods: POST
INFO 12-19 19:52:59 metrics.py:449] Avg prompt throughput: 33042.7 tokens/s, Avg generation throughput: 8.5 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:53:04 metrics.py:449] Avg prompt throughput: 39009.4 tokens/s, Avg generation throughput: 10.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 12-19 19:53:09 metrics.py:449] Avg prompt throughput: 42956.5 tokens/s, Avg generation throughput: 11.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 12-19 19:53:14 metrics.py:449] Avg prompt throughput: 46851.9 tokens/s, Avg generation throughput: 12.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 12-19 19:53:26 metrics.py:449] Avg prompt throughput: 8348.6 tokens/s, Avg generation throughput: 2.1 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:53:28 api_server.py:400] Starting profiler...
INFO 12-19 19:53:28 api_server.py:402] Profiler started.
INFO 12-19 19:53:36 metrics.py:449] Avg prompt throughput: 415.1 tokens/s, Avg generation throughput: 0.1 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:53:41 metrics.py:449] Avg prompt throughput: 7812.1 tokens/s, Avg generation throughput: 2.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 12-19 19:53:46 metrics.py:449] Avg prompt throughput: 7808.4 tokens/s, Avg generation throughput: 2.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 12-19 19:53:51 metrics.py:449] Avg prompt throughput: 15581.8 tokens/s, Avg generation throughput: 4.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 12-19 19:53:56 metrics.py:449] Avg prompt throughput: 16675.3 tokens/s, Avg generation throughput: 4.3 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:54:01 metrics.py:449] Avg prompt throughput: 23408.1 tokens/s, Avg generation throughput: 6.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 12-19 19:54:06 metrics.py:449] Avg prompt throughput: 23839.8 tokens/s, Avg generation throughput: 6.1 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:54:11 metrics.py:449] Avg prompt throughput: 31073.9 tokens/s, Avg generation throughput: 8.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 12-19 19:54:16 metrics.py:449] Avg prompt throughput: 31698.4 tokens/s, Avg generation throughput: 8.1 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:54:21 metrics.py:449] Avg prompt throughput: 38877.6 tokens/s, Avg generation throughput: 10.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 12-19 19:54:26 metrics.py:449] Avg prompt throughput: 39324.7 tokens/s, Avg generation throughput: 10.1 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:54:31 metrics.py:449] Avg prompt throughput: 46712.7 tokens/s, Avg generation throughput: 12.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 12-19 19:54:36 metrics.py:449] Avg prompt throughput: 46849.6 tokens/s, Avg generation throughput: 12.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 12-19 19:54:41 metrics.py:449] Avg prompt throughput: 49318.0 tokens/s, Avg generation throughput: 12.6 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:54:47 metrics.py:449] Avg prompt throughput: 49322.6 tokens/s, Avg generation throughput: 12.6 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:54:52 metrics.py:449] Avg prompt throughput: 49464.6 tokens/s, Avg generation throughput: 12.7 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:54:57 metrics.py:449] Avg prompt throughput: 49534.7 tokens/s, Avg generation throughput: 12.7 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:55:02 metrics.py:449] Avg prompt throughput: 49653.3 tokens/s, Avg generation throughput: 12.7 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 12-19 19:55:07 api_server.py:407] Stopping profiler...
INFO 12-19 19:55:07 api_server.py:409] Profiler stopped.

after finishing the test, /data/profile/ dir has nothing.

Please try:

use offline api + prompt_token_ids as input  <- This should be GPU bottleneck
use offline api + text prompt                          <- Test whether the tokenizer is causing the CPU bottleneck
use webserver + prompt_token_ids as input  <- Test whether the webserver is causing the CPU bottleneck
use webserver + text prompt                          <- Test whether the tokenizer + webserver  is causing the CPU bottleneck

I followed the instructions but nothing left in profile directory.

may be related
https://github.com/vllm-project/vllm/issues/11346

use webserver + prompt_token_ids as input  <- Test whether the webserver is causing the CPU bottleneck

How can I try this? any reference in vllm github?

why?
input: Union[List[int], List[List[int]], str, List[str]]
https://github.com/vllm-project/vllm/blob/1ecc645b8f5431f1404551ad24721a63f01aea4e/vllm/entrypoints/openai/protocol.py#L865C1-L869C61
try add dummy dimension:
input: List[List[int]]

  "input": [[
    0,
    16083,
    ...(3K token ids)
    152,
    2
  ]],

What does truncate_prompt_tokens do? Can it be deleted?

why?
input: Union[List[int], List[List[int]], str, List[str]]
https://github.com/vllm-project/vllm/blob/1ecc645b8f5431f1404551ad24721a63f01aea4e/vllm/entrypoints/openai/protocol.py#L865C1-L869C61
try add dummy dimension:
input: List[List[int]]

  "input": [[
    0,
    16083,
    ...(3K token ids)
    152,
    2
  ]],

I tried it, but the result is same.

Is it caused by
"truncate_prompt_tokens": 1,

Is it caused by
"truncate_prompt_tokens": 1,

sorry for late replay.
Removing "truncate_prompt_tokens": 1  parameter fixed prompt_tokens:1 to 3907.
but the results of two scenarios below are same.

use webserver + prompt_token_ids as input <- Test whether the webserver is causing the CPU bottleneck
use webserver + text prompt <- Test whether the tokenizer + webserver is causing the CPU bottleneck

At present, it seems that the performance bottleneck is caused by the webserver, instead of tokenizer.
Please test the performance of offline inference again.

use offline api + prompt_token_ids as input <- This should be GPU bottleneck
use offline api + text prompt <- Test whether the tokenizer is causing the CPU bottleneck

Compare the performance of webserver vs offline inference to see if the performance loss is acceptable.

At present, it seems that the performance bottleneck is caused by the webserver, instead of tokenizer.
Please test the performance of offline inference again.

use offline api + prompt_token_ids as input <- This should be GPU bottleneck
use offline api + text prompt <- Test whether the tokenizer is causing the CPU bottleneck

Compare the performance of webserver vs offline inference to see if the performance loss is acceptable.

In an environment where I can test, it's a little difficult to conduct offline tests. However, interesting is that CPU usage was lowered under the same load when GPU resource was changed from mig-1g-10gb to whole h100. Maximum throughput has also increased. What did I miss?

Could it be because by out of GPU memory triggers cpu offloading?


config//build_mode/constraints is missing

This constraint is used in js rules.

Looks like config//os/constraints:iphoneos is also missing.

I'm not sure if the JS rules are usable in the open source version. Someone would need to try - and if those are the only missing features, I'm sure they could be added. The way these should have been done is by the toolchain, which tends to be the kind of cleanup we do when moving rules open source.


Rename "await" to "tsc_await"

To aid with (further) source compatibility testing, rename await to
tsc_await to get it out of the way of the use of the await keyword
in Swift's Concurrency design. Leave the await here as deprecated
entry points so we don't break any code in the process.
Cloned over from https://github.com/apple/swift-package-manager/pull/3036

@swift-ci please test

Do we know who the various clients of TSC are, and what the plan is to update them (besides SwiftPM of course)? With a lot more activity requiring clients to update (even for good reasons), perhaps it's time to properly version TSC and switch the clients to use the versions.

That might be reasonable. For this particular case, we can leave the await entry point around for clients that aren't going to try to build with concurrency enabled, so we won't break anyone yet... but TSC has enough clients now that proper versioning would likely help us.
(At the moment, I'm trying to get far enough to build a toolchain for more testing, so TSC + SwiftPM is the target)

Right, understood, and agreed in this particular case.  There has been at least a couple of cases of revlock between TSC and SwiftPM in the past week, and so I think we should start versioning TSC so that clients can adopt changes at their pace.  I'll start some conversations about that.


OpenStreetMap.Josm: Add v1.5.18463

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Mostly based on the v1.5.18427 manifests, but with some changes because winget (at least for me) was refusing to work with the .exe installer, and only permitting the .msi one.
Microsoft Reviewers: Open in CodeFlow

Winget itself has no issues with the exe installer. It is wingetcreate that fail to parse it.


update test and apdus for cardano

📝 Description
This PR updates the apdus and the dataset test for Cardano. current one is outdated because of network update and new Cardano app.
❓ Context

Impacted projects: ledgerjs ledger-live-common
Linked resource(s): ``

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Work perfectly


Documentation on loadExternalToken

Core Library
MSAL.js v2 (@azure/msal-browser)
Wrapper Library
Not Applicable
Documentation Location
docs.microsoft.com
Description
Recently I’ve been experimenting with an existing Angular SPA, with @azure/msal-angular in combination with a teams tabs. We figured out a hack-y-way to use information from the access token that we got from Teams SSO (the Teams app is pre-authorized, and can be instructed to request an access tokens for our custom api) and creating both an account and registering the access token for our api.
Then I started looking in the code and found this code loadExternalToken(…), this seems useful instead of us doing the same, while making direct calls to private methods on the browsercache.
But I cannot find a sample or any documentation on this advanced, well hidden, method. Maybe @tnorling can enlighten us?
Our higher goal is to still keep using msal-angular, but also using the access token we get from Teams SSO. Because that will make the process for the user a bit more smooth (skipping the login pop-up, that closes automatically anyway).

@svrooij the document on loadExternalToken can be found here. However this approach shouldn't be used outside of testing scenarios -it sounds like this is what you're aiming at. Can you elaborate a bit more on your scenario? You should be able to make use of the teams sso access token to call a resource via the OBO pattern shown here.

@derisen Sure I can elaborate on our scenario. We have an API protected with Azure AD token. We already have an angular app using this api (it's hosted as Azure Static Web App, combining both the SPA and the API on a single domain). The angular app uses MSAL to get tokens for the api.
Now we want a portion of the angular app to be available in Teams. In teams you have two options to get a token, you can open a special pop-up and use MSAL there. In this case the user is shown a pop-up, and the pop-up will likely disappear without user interaction, because teams supplies us with the tenant and the login hint.
The second option is to call some teams sdk javascript method, which tells the teams client to just generate an access token for the api (specified in the app manifest). In this case the access token is requested by the teams client id, but the audience is our custom api. And there is no user interaction required.
For us not the change anything to the code calling our custom api with the access token, the token needs to be registered to MSAL. So that it's picked up by the MsalInspector.
Once we have the token on the custom api, we are able to call graph with the obo flow, but the issue is in getting the token in Msal so it's send to the custom api by the MsalInspector.
We now take the information from the access token that we get from teams and create an account for that, and register the token as both the identity token and the access token (hence the "hacky" in my description).

@svrooij I see. IMHO modifying the existing code (perhaps via a custom interceptor) to accommodate the SSO token from Teams SDK  would be less of a hurdle in future than opening the app to unpredictable behavior by using the loadExternalToken API.

Building a custom Interceptor seems like more hassle then injecting the token…. That is because then we would need to copy the entire code of the current interceptor and add a new way when the client is in teams. That is because the current interceptor has all its method defined as private, so you cannot extend it and re-use the existing code.
You pointed me to the documentation of the loadExternalToken method, so that will make my solution a bit more stable. Eventually the Teams app should be supporting MSAL (in my opinion), but until then we will be injecting the token. And getting this desire some attention.

@svrooij We strongly discourage using the loadExternalToken API for anything other than testing. If you choose to use it in production, please know that you do so at your own risk and we make no guarantees that we will support issues that arise from it. Furthermore, by injecting the tokens you are creating a 2nd source of truth in terms of cached tokens (one in the Teams context and another in MSAL context), this may create more unintended issues down the line.
The recommended approach, as Dogan mentioned, is to write a custom interceptor. The provided interceptor was designed to address the most common use cases but we are aware that it may not address all scenarios, writing a custom one is the way to go if you find the one provided doesn't meet your needs.

@tnorling understood!
A solution might be to provide enough information to the loginscreen through the query string that it logs in automatically. Is that something that would be possible?
I think that if the application is consented for that user opening the login screen with the domain set and the loginHint it might not ask the user for more info and just continue (and auto close).

Yes theoretically, if a user is already signed in and you provide a hint (login_hint optional claim is the best one to use) to MSAL it can sign you in without interaction, however, there may still be cases where interaction may be required such as when the user's session has expired or MFA is required.

Thanks for the explanation. This issue can be closed


Function hook

As we have not fully discussed the specification of examples of FunctionHooks (especially MemoryHook), we separate #933 into two PRs, FunctionHook mechanism and examples of FunctionHook (subclasses of FunctionHooks).
This PR implements the former one.
We change the implementation from #933 in two points.

Remove preprocess, postprocess, and __call__ methods of FunctionHook.
Make chainer.global_function_hook thread safe.

OK. LGTM!


Upgrade Introduction to SignalR training module to .NET 8.

https://learn.microsoft.com/en-us/training/modules/aspnet-core-signalr/1-introduction

Associated WorkItem - 167767

Fixed


Generating Training Data (and OpenFOAM 5)

I'm trying to generate the training data for the backward step case instead of using data provided. I see that you need wall distance, u,v,w velocities and coordinates for cell centres. I have two brief questions:

How did you write out your wall distances in OpenFOAM5 so that it is readable by "training_data_marker.py"? (For cellcentres I just used the inbuilt func)
Could you elaborate on how files need to be setup for the "training_data_maker.py" to create the total array data set for training?

Hello,
To write out arbitrary quantities like wall distances - you need to make a modification to a standard RANS model and recompile as a separate (more detailed) model. For example in your Spalart-Allmaras model you can add the following
if(this->runTime_.outputTime())
{
y_.write();
}

Note that the template constructor for the RANS model defines the wall distance with y_ as follows
y_(wallDist::New(this->mesh_).y())

You can make temporary variables in the same manner and write them to disk. For example, if you want to write out the magnitude of the strain-rate tensor in real-time you can use
volScalarField strain_ = sqrt(2.0)*mag(symm(fvc::grad(this->U_)));
const char* strain_name = "strain";
strain_.rename(strain_name);
strain_.write();

Finally, cell-center coordinate information can be obtained by a convenient OpenFOAM postprocessing utility
postProcess -latestTime -func writeCellCentres

Hope this helps.

@Romit-Maulik thank I found the post processing utility for cell centers but couldn't figure out the wall distance part. Thanks for your detailed explanation really appreciate it!.
For the second question, I'm assuming you then just rename these openfoam files accordingly for the python script and use it for training?.

That's correct.

Thank you!


CI CD issue -  CSS Changes Not Reflecting in Production on Frappe v15

Issue Title: CSS Changes Not Reflecting in Production on Frappe v15
1. Issue Description
CSS changes pushed to the repository are not being updated in the production environment. This issue is currently observed in the Frappe framework version 15, affecting the beta.zaviago.com site.
2. Steps to Reproduce

Push CSS changes to the repository.
Observe the CI/CD pipeline executing the deployment process.
After deployment, check the production site at beta.zaviago.com for the reflected changes.

3. Current Behavior

The CSS changes made in the repository are not visible on the production site after the deployment process.

4. Expected Behavior

All changes made to CSS files and pushed to the repository should be reflected in the production environment upon successful deployment.

5. Action Items

[ ] Review the commits related to CSS changes to confirm they are correctly pushed to the repository.
[ ] Examine the CI/CD pipeline configuration, specifically the steps handling CSS files.
[ ] Inspect the build and deployment logs for any errors or warnings that could indicate why CSS changes are not being applied.
[ ] Confirm that the latest code version is being deployed to the beta environment.
[ ] Check server-side caching mechanisms that might prevent updated CSS from being served.
[ ] If necessary, manually trigger the build and deployment to ensure the changes are picked up.
[ ] Communicate with the development team to gather more insights into the issue.
[ ] Apply a fix to the CI/CD pipeline and document the resolution process for future reference.

@MarkSuttirak can you confirm if this version have your changins?  idk about the changings so i can't confirm but from now it will fetch the version-15 changings

Need to contact umer on this one

some of the command was not running in CI CD pipeline-

1h


Typo in Polish Pipeline content

:bug: Bug Report
What is the problem?
Typo in the last paragraph of the Polish Pipelines section in the Typescript Workshop - "Conratulations"

Reproduction Steps
Browse site > Typescript Workshop > Advanced Topics > Polish Pipeline
Verbose Log
N/A
Environment
N/A
Other information
N/A

Hi @burgwyn, thanks for the catch and for putting in a PR, much appreciated! 👍


Serializer : AttributeError: 'ControlledOperation' object has no attribute 'gate'

File "/usr/local/google/home/jaeyoo/git/Cirq/cirq/google/serializable_gate_set.py", line 136, in serialize_op
gate_type = type(gate_op.gate)
AttributeError: 'ControlledOperation' object has no attribute 'gate'
When I try to serialize a circuit with "cirq.ControlledGate(cirq.Z).on(q0, q1)", It shows the above error. (yes, ControlledOperation doesn't have "gate" : https://github.com/quantumlib/Cirq/blob/master/cirq/ops/controlled_operation.py#L25).
Is it intended or am I doing wrongly?
CZ, CZPowGate is possible to be serialized because they are eigen gates. That means, do I have to use them always for serialization? What if I want to make C-ZZ operator and serialize it, how can i do it?

It should work if you create a CZPowGate instead of using ControlledGate(cirq.Z), but this may depend on which gate set you are trying to serialize to. It looks like we don't have a good way of supporting controlled operations in SerializableGateSet, so we will have to add support for that.

Yeah, this is a good example of how consuming gates is complicated by the ability to specify them in multiple ways.

Would it make sense for the serializer to check that an unknown gate is equivalent to one of the known serializable gates, as a relatively quick workaround? (May be not by default, but as an option)

Yes, what I am implementing requires conditioning any DensePauliString and any PauliSum. I've tried maffoo's suggestion by using ConvertToCzAndSingleGates to use CZPowGate only, but it shows errors:
`

import cirq
import sympy
a = sympy.Symbol('a')
b = cirq.Ry(a).on(cirq.GridQubit(0,0))
c = cirq.Circuit([b])
c
cirq.Circuit([
cirq.Moment(operations=[
cirq.Ry(sympy.Symbol('a')).on(cirq.GridQubit(0, 0)),
]),
])
print(c)
(0, 0): ───Ry(a)───
d = cirq.ConvertToCzAndSingleGates().optimize_circuit(c)
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/google/home/jaeyoo/git/tfq/Cirq/cirq/circuits/optimization_pass.py", line 127, in optimize_circuit
opt = self.optimization_at(circuit, i, op)
File "/usr/local/google/home/jaeyoo/git/tfq/Cirq/cirq/optimizers/convert_to_cz_and_single_gates.py", line 95, in optimization_at
else self._on_stuck_raise))
File "/usr/local/google/home/jaeyoo/git/tfq/Cirq/cirq/protocols/decompose.py", line 273, in decompose
error = on_stuck_raise(item)
File "/usr/local/google/home/jaeyoo/git/tfq/Cirq/cirq/optimizers/convert_to_cz_and_single_gates.py", line 82, in _on_stuck_raise
"known unitary effect on 1 or 2 qubits.".format(op))
TypeError: Don't know how to work with cirq.Ry(sympy.Symbol('a')).on(cirq.GridQubit(0, 0)). It isn't composite or an operation with a known unitary effect on 1 or 2 qubits.
`
Could you give me more advices?

Ok, I found out a way. Close this issue and open the new issue related to cirq.decompose()

@jaeyoo Could you say more about the workaround to for your example? Also interested in ways to make more gates serializable with sympy symbols.


Add ?opam_version to Dir_context.std_env

It defaults to the version of opam libraries, but in some cases (e.g. ocaml-ci) it is useful to inject a value that comes from an external opam process.

Thanks!


~6 bugs in one short video: Modules, Registers showing bogus output, cannot edit watch expressions, watch expression view rule not respected, assembly view not showing interactable registers, watch address location not correct

Debugger version 9.12 ALPHA - Oct 14 2024 [cc2848f] (most recent release on github)
I am debugging a component debug build of Chromium. I can provide you with more info if you'd like.
As the title (which may get clipped) spells out:
~6 bugs in one short video:

Modules, where it shows some __elems_ object which is... zero sized types? but which have values?
Registers showing bogus output, showing various random objects that Idk what they are.
cannot edit watch expressions, screen flashes red, doesn't give any reason why (it's just on the stack?? I can't edit the memory either because...)
watch expression view rule not respected, it shows it in hex with the enum name.
assembly view not showing interactable registers, only those AFTER $rip
watch address location not correct, as shown in my jumping to that address and it containing garbage.

Here is the video in question:
When there is a "bug," I tend to circle my mouse around it :P
https://drive.google.com/file/d/1bcjgRgQ1t_0uvXYzWZEL501NHgCGE3fV/

Without testing Chromium locally, I believe I've fixed the registers/modules view problems as of 1865c337041d296a2174f92e4ebcb96e8795d2e8.

watch expression view rule not respected, it shows it in hex with the enum name.
This should be fixed as of 53c624a27cee0416f35c4dc44f2044541500f7ea.

As for the others:

screen flashes red, doesn't give any reason why
The reason is in the bottom right-hand corner of the window, but it likely just says that committing failed. I'll try to recreate that one locally, I have a suspicion of what is causing that.

assembly view not showing interactable registers, only those AFTER $rip
I think this is likely just an assembly syntax lexing problem (it looks like the lexer got confused at some point) - to get around it temporarily, you can select the register name and hover it.

watch address location not correct, as shown in my jumping to that address and it containing garbage.
This is not a bug, as the watch pin "address location" is referring to the spot in disassembly where you've attached that pin, not the evaluated address of the expression. (You can see how that address changes if you drag/drop that pin around). When you navigate to the address of the pin, that address is the location within the disassembly that you've attached that pin to. So when you navigate there and it shows the various byte values, those are the byte values of the disassembly, not of the expression you're evaluating.

Okay, that watch window mutation bug should also be fixed as of b3d6b2913e925c74701700a10b3b855ada2da0cb. You should be able to write to that value.
You can't modify in the memory view yet, but this is just a known limitation of the memory view; that UI will be more fleshed out a bit later on.

Thanks for the super fast response!

In the interest of not creating more issues:
Here's a new video showing stepping being broken when it has to actually step over a function call:
https://drive.google.com/file/d/1EGY2o3tFKJRtaSW8eUXDgVOgz37O2Hbn
Basically, it freezes, "running" the target, but it's actually paused at the correct 'ret' instr.
Then, pausing, and stepping once more will return to the right location.

Thanks for your work on this by the way, you're doing god's work.....

If you'd rather I create new issues for these minute little things for easier bugtracking, let me know and I'll do that.
Hovering over a stack frame with extensive template use, the types of the parameters cause the name to be super long, pushing the entire signature out of screen. Can that be changed so it's left-justified and won't go wider than the width of my screen, either wrapping or pushing off to the right?

In the interest of not creating more issues:
Here's a new video showing stepping being broken when it has to actually step over a function call:
https://drive.google.com/file/d/1EGY2o3tFKJRtaSW8eUXDgVOgz37O2Hbn
Basically, it freezes, "running" the target, but it's actually paused at the correct 'ret' instr.
Then, pausing, and stepping once more will return to the right location.

Might be related to this line stepping bug ?
https://github.com/EpicGamesExt/raddebugger/issues/322

Yeah, I would prefer new issues for each separate category of bug - that helps me keep track of things a bit better.
The disassembly lexing bug has been fixed as of e9666e2eddee1665169b6c74f0e9f6660e746f86. I've also fixed the thread callstack tooltips when extremely long autogenerated symbol names are used; there is still no path for trying to make those names more helpful, but I've just stopped the tooltip from overtaking too much. I've fixed #322, so I'll look into that stepping bug now.

Actually, that does look like it would've been caused by the #322 bug, which has now been fixed. So I'll close this issue, but let me know if you run into the same bug again.


Auto task completion tracking will break block references in tasks.

What happened?

enable auto task completion tracking in setting
query all task
click a uncompletion task which rendered by dataview and have a block ref like this: - [ ] A task [priority::low] [[#^100ce1]]
get a broken block ref: - [x] A task [priority::low] [[#]] [completion:: 2023-08-09] ^100ce1

DQL
No response
JS
No response
Dataview Version
master
Obsidian Version
v1.3.7
OS
MacOS

cause by: https://github.com/blacksmithgu/obsidian-dataview/pull/1530


Material-ui/0.15

This PR will contain all the changes needed to run with material-ui 0.15
I’ll keep this PR updated till the final 0.15 version will be released

@izziaraffaele your paths are incorrect. Should be like 'material-ui/Checkbox' instead of 'material-ui/lib/Checkbox'

If someone is interested, I have https://github.com/mbrookes/formsy-material-ui/pull/85 to fix the import path that are needed from 0.15.0-beta.1.


[FLINK-12882][network] Remove ExecutionAttemptID argument from ResultPartitionFactory#create

What is the purpose of the change
The ResultPartitionID could be got directly from ResultPartitionDeploymentDescriptor, so it is no need to pass ExecutionAttemptID to construct new ResultPartitionID during creating ResultPartition in factory.
Brief change log

Remove ExecutionAttemptID argument from ResultPartitionFactory#create
Use the simple constructor of ResultPartitionID in tests
Add checkNotNull for the parameters in constructor of ResultPartitionID

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot attention @azagrebin

@flinkbot approve all

Thanks for the review @azagrebin !
@zentol could you help double check and merge if no other concerns?


type 'double' is not a subtype of type 'int'

Operation next([num length = double.infinity]) {
    assert(length != null);

    if (_modificationCount != delta._modificationCount) {
      throw ConcurrentModificationError(delta);
    }

    if (_index < delta.length) {
      final op = delta.elementAt(_index);
      final opKey = op.key;
      final opAttributes = op.attributes;
      final _currentOffset = _offset;
      final actualLength = math.min(op.length - _currentOffset, length);
      if (actualLength == op.length - _currentOffset) {
        _index++;
        _offset = 0;
      } else {
        _offset += actualLength;
      }
      final opData = op.isInsert && op.data is String
          ? (op.data as String)
              .substring(_currentOffset, _currentOffset + actualLength)
          : op.data;
      final opIsNotEmpty =
          opData is String ? opData.isNotEmpty : true; // embeds are never empty
      final opLength = opData is String ? opData.length : 1;
      final int opActualLength = opIsNotEmpty ? opLength : actualLength;
      return Operation._(opKey, opActualLength, opData, opAttributes);
    }
    return Operation.retain(length);
  }

next([num length = double.infinity])   length default is a double
but   Operation.retain need a int
And assert(length != null); is useless

Where did you get this code?

It's in quill_delta-2.0.0/lib/quill_delta.dart, line 642
I'm trying to add text with code
_controller.replaceText(0, 4, 'data', TextSelection.collapsed(offset: 0));

Where did you get this code?

It's in quill_delta-2.0.0/lib/quill_delta.dart, line 642
I'm trying to add text with code
_controller.replaceText(0, 4, 'data', TextSelection.collapsed(offset: 0));

I can copy the file out to our repo. It is just one file

What fix do you propose to make?

What fix do you propose to make?

I'm not sure yet. I just hope I can add text to the editor with code.

submitted https://github.com/singerdmx/flutter-quill/commit/d603c46c45517ef48b7194fe32907b23b14cfeed

checkout https://github.com/pulyaevskiy/quill-delta-dart/issues/18

@lookdczar  please use https://github.com/singerdmx/flutter-quill/commit/e41b2c3b2023f17cc0ffbf1eeb0aff51ef1bc0e1
It is checked in.
Just use latest code.
Let me know if I can resolve this issue

Reopen it if there is still issue.


[PROJECT] Expense Flow V2 Specs

Here's the list of Specs / Features for the Expense Flow Iteration
We will be building this into a project once we've had a chance to hear user feedback on the new expense flow.
V1 Project issue is here https://github.com/opencollective/opencollective/issues/2394

Suggestions after submitting an actual expense in the new flow:
Save multiple bank accounts
The current payment methods menu design led me to think I could add multiple accounts, because it says "add bank account" under my current one. But actually it just overwrote my previous bank info and only saved one.

Name payment methods
For example, I have saved my business and personal bank accounts, but they just show up as numbers on the dropdown. It would be great if I could give them names so I can tell them apart easily.
Add payout methods section to profile settings
I should be able to view, delete, rename, and edit my saved payment methods from this screen.

Hmm! Actually it did save both bank accounts. But it only showed up after a long while (hours). Now I can see two.

Small improvement:

"Submitted" has two Ts
Make "expense feed" a link

Design issue: If you upload multiple receipts, it's super hard to tell which is which when you're entering the details.

Make the thumbnail images bigger
Show the upload filename

The downloaded version of invoices needs to include the date submitted - currently this is missing.

If there is no line item description provided, it should automatically copy the expense title as the description. Alternatively, descriptions should be mandatory. To be valid, invoices must have completed line items.

@betree this last comment might be worth doing as a fix to V1 rather than a V2 spec. We need people to fill up description -

@piamancini @alanna Descriptions are already mandatory in the new flow. This appears because the expense was created with the legacy expense flow, thus individual items (amounts) don't have a description attached.

Ah ok @Betree - if possible, it would be good to copy the title to the description for all the older expenses that don't have anything in the description, to help with the migration. Is that easy to do? If it's too complicated we can probably get away with is, but the accountants won't be so happy.

Also what about including the date on downloaded invoices as mentioned above? I think that should be a quick fix and it's needed soon for accounting reasons. @piamancini is it worth doing that one now?

@alanna dowloaded invoices have the date already:

@piamancini the expense that triggered my request about adding the date was this one below. It's showing a date range not an invoicing date. Why would that be? Is it something the user types in? I think it should just automatically stamp the submission date of the expense, because an invoicing date is not the same as the date rage of work the invoice covers.

@alanna The range date in this case seems to be because of the different dates she entered on the expense.
I think indeed we should take the date from the submission date.
cc @Betree

#3278 Mentioning this issue since is where I'm uploading design updates of the 'Request expense' feature

Just planned the overall steps for this project.
Each step maps to an issue I'll create and properly spec.
There's not so much that can be parallelized, I see the email template as something we can delegate from the beginning (perhaps as a bounty) while I take care of refactoring the payee information as a separate step in the expense flow.
After that refactor, I can tackle submitting on behalf and if it's urgent, someone else can tackle grants with minor conflicts.
In practice, I'll probably tackle both.

We have addressed all issues stated here, as far as I know. I suggest closing this, and since we constantly have the stuff to do on expenses, we can have an ongoing project to manage individual issues.


Flyway 10 Gradle Plugin: No database found to handle jdbc:postgresql://...

Which version and edition of Flyway are you using?
Gradle plugin version 10.0.0
Upgraded from 9.22.3
I read the upgrade notes - https://documentation.red-gate.com/fd/release-notes-for-flyway-engine-179732572.html - but did not see any changes relating to PostgreSQL or clean.
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
N/A
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Gradle plugin
Gradle version 8.4
JVM 17.0.9
Which database are you using? (Type & version)
PostgreSQL
Which operating system are you using?
Tested on both Linux x64 (RHEL8) and ARM x64 (M2)
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
We have a custom flyway clean task:
tasks.register('flywayCleanTest', FlywayCleanTask) {
  url = System.getenv('TEST_JDBC_URL') ?: 'jdbc:postgresql://localhost/testdb?currentSchema=test'
  user = System.getenv('TEST_DATABASE_USERNAME') ?: 'admin'
  password = System.getenv('TEST_DATABASE_PASSWORD') ?: 'admin'
  defaultSchema = 'test'
  cleanDisabled = false
}

What did you expect to see?
The clean succeeds without error, as it did for 9.22.3
What did you see instead?
Running ./gradlew flywayCleanTest gives an error:
No database found to handle jdbc:postgresql://localhost/testdb?currentSchema=test

As of version 10, you'll need to add a dependency on flyway-database-postgresql
https://documentation.red-gate.com/fd/postgresql-184127604.html

Just for clarification, this is what was meant in the release notes as:

Java compatibility

Deprecated Java 8. Java 17 is now required for development
Modularized database support in Flyway to allow greater flexibility. This includes; DB2, Derby, HSQLDB, Informix, PostgreSQL, CockroachDB, Redshift, SAP HANA, Snowflake and Sybase ASE. See Database Support page for your database for module dependency.

Unfortunately I cannot link to that section directly. The Database Support page for PostgreSQL is here

Perhaps that should be moved to the breaking changes section and clarified?
Anyway happy to close this - I have the info I need to upgrade, thanks all

@josephearl thank you for your comment. I have actually moved that up into the breaking changes to make it more noticeable.

I still can't see any mention of this change in the breaking changes section for v10

We, too, have this issue even after applying the extra dependency. Unfortunately, the error message isn't really helpful, since it doesn't specify if there is a dependency, configuration, connection, authentication, or whatever else error; only stateing the message above.
At least I don't see a connection attempt logged in my postgres instance.
Best regards Jan

Got it solved by adding the additional dep to the buildscripts dependency declaration, too:
plugins {
    ...
    id("org.flywaydb.flyway") version "10.1.0" apply false
    ...
}
buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        ...
        classpath("org.flywaydb:flyway-database-postgresql:10.1.0")
        ...
    }
}

I guess, this is needed in our case, since we declare the plugin dependency in our main gradle file; and each subproject using flyway the uses the plugin definition from main and adds flyway-core and flyway-database--postgres itself for SpringBoot/Tests.
Just in case someone else stumbles over this; maybe this helps. :smiley:

Got it solved by adding the additional dep to the buildscripts dependency declaration, too:
plugins {
    ...
    id("org.flywaydb.flyway") version "10.1.0" apply false
    ...
}
buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        ...
        classpath("org.flywaydb:flyway-database-postgresql:10.1.0")
        ...
    }
}

I guess, this is needed in our case, since we declare the plugin dependency in our main gradle file; and each subproject using flyway the uses the plugin definition from main and adds flyway-core and flyway-database--postgres itself for SpringBoot/Tests.
Just in case someone else stumbles over this; maybe this helps. 😃

This Solved my issue, Thanks.

This is still broken for maven projects. Reverted back to 9.23.
    <dependency>       <groupId>org.flywaydb</groupId>       <artifactId>flyway-core</artifactId>       <version>10.7.2</version>     </dependency>     <!-- https://mvnrepository.com/artifact/org.flywaydb/flyway-database-postgresql -->     <dependency>       <groupId>org.flywaydb</groupId>       <artifactId>flyway-database-postgresql</artifactId>       <version>10.7.2</version>       <scope>runtime</scope>     </dependency>
still gets us the error No database found to handle jdbc:postgresql://...

I still got this build error after adding to the class path, reverting to 9.22.3 works for me.
* What went wrong:
A problem occurred configuring project ':backend'.
> Could not resolve all files for configuration ':backend:classpath'.
   > Could not find org.flywaydb:flyway-database-postgresql:flyway.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/flywaydb/flyway-database-postgresql/flyway/flyway-database-postgresql-flyway.pom
       - https://plugins.gradle.org/m2/org/flywaydb/flyway-database-postgresql/flyway/flyway-database-postgresql-flyway.pom
     Required by:
         project :backend

I think it's important to mention that you have to substitute the flyway-database-postgresql dependency in place of flyway-core, otherwise it doesn't work (at least for me).

This is vaguely alluded to in the Flyway Gradle Task documentation under the header "Adding dependencies on Flyway Database Types":

For some Flyway database types, like Cloud Spanner and SQL Server, you'll need to add a dependency to the database type in a buildscript closure to get your Gradle commands to work properly. This puts the database type on the build classpath, and not the project classpath.
Here is an example build.gradle:

Since the 10.x change, it appears this is now the case for all databases. This is very poorly documented, and we stumbled upon this today as well when trying to upgrade Spring Boot from 3.2.8 to 3.3.3, whose BOM includes an update of Flyway from 9.x to 10.10.0.

I came across this poblem today where I use flyway in a ktor project. I had to put this to the top of my build.gradle.kts file.
buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath("org.flywaydb:flyway-database-postgresql:10.19.0")
    }
}

apply(plugin = "org.flywaydb.flyway")

plugins {
    kotlin("jvm") version "2.0.20"
    // add flyway plugin
    id("org.flywaydb.flyway") version "10.19.0"
    // project specific plugins
    id("io.ktor.plugin") version "3.0.0"
    id("org.jetbrains.kotlin.plugin.serialization") version "2.0.20"
}


Set up Render with the FastAPI project

Hook up render to the Meta API (webhook) and connect it to the main branch of this repo.

Completed. We got a dev and prod server now. Need a phone number to get the prod server live.


[5.3] Changing the name of the method mapToAssoc() to mapWithKeys()

This was suggested in #14795 by @JosephSilber and @adamwathan and is a better definition of this method.
Also changed the test accordingly.

There should probably be a fallback method with the old name here as to not introduce a breaking change. Just add a deprecated docblock on top of it so people are aware it will go away at some point.

I think it's not needed since this method were introduced last week on 5.3 only so it shouldn't be a BC since 5.3 isn't even out yet.

Ah, didn't know that it was introduced only last week. Carry on! 😄

RC1 is out now. We maybe need to bit a little bit careful at this point. Nothing's set in stone though I think. :)


It would be nice to have a favicon.ico!

It's a little thing, but it would be nice. I have no artistic talents unfortunately, but I know where the file should go!

that is a really great idea! Not sure what Chris would agree on, but even the logo would be really cool!

I put something there, based on a redesign that's already in progress.  It's better than the blank-page icon, but I'll do better soon.

I've now got a decent image in each of three sizes.  The black isn't terribly colorful, but lighter shades don't turn out well at all.  I think I'll stop here.


Call tests without swagger global

I noticed in the package.json the test script is calling "swagger project test" I really don't want to install swagger globally on my build server, is there a way to call these tests without the global package?

I figured it out. You just call mocha with the path to your tests.


It would be helpful to have charset support included, even if it's added to AnyParameter.

In order to support other languages, I need to add charset to the vCard and generate the vCard string as follows:
BEGIN:VCARD
VERSION:4.0
FN;CHARSET=UTF-8:姓名
TITLE;CHARSET=UTF-8:职位
ORG;CHARSET=UTF-8:公司;;
END:VCARD

I haven't been able to find a method that supports charset, so I currently manually add CHARSET to paramRegExp in AnyParameter and rebuild.
It would be helpful to have charset support included, even if it's added to AnyParameter.

Hello @fts11259375,
Thank you for you using vcard4, and for your valuable contribution to the vcard4 community (this issue).
This library is dedicated to strictly adhering to the vCard version 4.0 specification (RFC6350). This means that we stay true to the guidelines set forth in the official specification without introducing any additional features or deviating from it.
Allow me to provide some brief historical context to this character set issue. In early versions of vcards, specifically version 2.1 and earlier, the default character set of vcards was ASCII, but this could be overridden in specific properties using the "CHARSET" property parameter (very much like what you're doing).
However, for later versions, 3.0 and 4.0, the charset for vCard is UTF-8.  There is no way to override this and it is invalid to specify a value other than "UTF-8" in a "charset" MIME parameter (see section 3.1 of the RFC).
In fact, in version 4.0 vCards, the "CHARSET" property parameter is intentionally removed from the vCard specification (see Appendix A2 of the RFC). This was also the case for vCard 3.0.
In conclusion, this feature WILL NOT be included in the vcard4 library, because the library remains true to RFC 6350 and its extensions.

Let me provide some insight into the issue you're currently facing. It seems that the root of the problem might stem from the vCard version compatibility.
It's worth noting that the most widely used vCard version is vCard 2.1. Considering the symptoms you're encountering, it's possible that the device you're using to test your code doesn't support vCard 4.0 and might be limited to vCard 2.1 compatibility.
If we take a closer look at the historical context I provided in the earlier comment, the pattern you're employing (such as adding CHARSET to properties) was common in vCard 2.1. This suggests that if your device only responds positively to this approach, it likely supports only vCard 2.1.
Given this, I'd recommend considering two options. First, you could explore using a different device for testing, one that supports vCard 4.0. Alternatively, you might want to consider utilizing a library that generates vCard 2.1 vcards. Either approach should help align your code and device compatibility.
Feel free to reach out if you have any questions or need further assistance.

Thank you for your answer. It may be that the problem I encountered is caused by the phone manufacturer not following the specifications. On iPhones, if there is no "CHARSET" label, Chinese characters will display as garbled text. This is true for both vCard 3.0 and 4.0 versions. If the "CHARSET" label is included, Chinese characters can be displayed normally.
I have also encountered another issue. When using base64-formatted URIType in PhotoProperty, if the string "data:image/png;base64," is added before it, the photo cannot be displayed when imported into the phone. However, if the string "data:image/png;base64," is removed, the photo can be displayed on the phone but cannot be used in this format within URIType.
------------------ 原始邮件 ------------------
发件人:                                                                                "kelseykm/vcard4"                                                                                @.>;
发送时间: 2023年8月8日(星期二) 晚上9:29
@.>;
<EMAIL_ADDRESS>主题: Re: [kelseykm/vcard4] It would be helpful to have charset support included, even if it's added to AnyParameter. (Issue #18)
Let me provide some insight into the issue you're currently facing. It seems that the root of the problem might stem from the vCard version compatibility.
It's worth noting that the most widely used vCard version is vCard 2.1. Considering the symptoms you're encountering, it's possible that the device you're using to test your code doesn't support vCard 4.0 and might be limited to vCard 2.1 compatibility.
If we take a closer look at the historical context I provided in the earlier comment, the pattern you're employing (such as adding CHARSET to properties) was common in vCard 2.1. This suggests that if your device only responds positively to this approach, it likely supports only vCard 2.1.
Given this, I'd recommend considering two options. First, you could explore using a different device for testing, one that supports vCard 4.0. Alternatively, you might want to consider utilizing a library that generates vCard 2.1 vcards. Either approach should help align your code and device compatibility.
Feel free to reach out if you have any questions or need further assistance.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

I believe both issues stem from the same root cause.
Many manufacturers seem to deviate from the vCard specification. I'm convinced that some don't even verify the vCard version before parsing it. I think in pursuit of the 'Robustness Principle,' they often adopt a "mongrel"  parser that handles different vCard versions, but leaning heavily towards vCard 2.1 parsing functionalities


fix(ui): homepage layout glitch

Description:
Fixes a minor layout glitch with the launchpad sidebar and modifies padding slightly to bring more inline with original designs.
Motivation and Context:
Fix #1245
How Has This Been Tested?
Manually - navigate around the launchpad and ensure sidebar looks ok.
Screenshots
Before:

After:

Types of changes:
Bug fix
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 19.181% when pulling e24c4c87add297dee7a6b49522d319501cb27ac0 on mrfelton:fix/homepage-sidebar-glitch into 362cb562642d50145382f798e14026f59b355e6f on LN-Zap:master.


Json and payload_path

I'm having issues building a webhook agent for the following Json from a Kerberos installation . I don't know how to create just one event for it because the payload_path ="." Or $.web_request creates several events.
Could anyone give me a hand?
{
"regionCoordinates": [
388,
308,
535,
599
],
"numberOfChanges": 4442,
"incoming": 1,
"outgoing": 0,
"timestamp": "1476391523",
"microseconds": "6-438745",
"token": 736,
"pathToImage": "1476391523_6-438745_frontdoor_388-308-535-599_4442_736.jpg",
"instanceName": "frontdoor",
"web_request": {
"regionCoordinates": [
388,
308,
535,
599
],
"numberOfChanges": 4442,
"incoming": 1,
"outgoing": 0,
"timestamp": "1476391523",
"microseconds": "6-438745",
"token": 736,
"pathToImage": "1476391523_6-438745_frontdoor_388-308-535-599_4442_736.jpg",
"instanceName": "frontdoor"
}
}

Hi @nachiarg,
payload_path: "." should be working, are you sure Huginn isn't receiving more then one request? If it keeps being an issue you could use a DeDuplicationAgent to filter out the duplicates.

Ive manage to correctly configure a DeDuplicationAgent but I want to clean up the original agent

For example if I want to send as a payload only the token.  I would think it should go like this

{
"secret": "kerberos",
"expected_receive_period_in_days": 1,
"response": "Event Created",
"code": "201",
"payload_path": "$..token"
}

Original JSON

{

"regionCoordinates": [
388,
308,
535,
599
],
"numberOfChanges": 4442,
"incoming": 1,
"outgoing": 0,
"timestamp": "1476391523",
"microseconds": "6-438745",
"token": 736,
"pathToImage": "1476391523_6-438745_frontdoor_388-308-535-599_4442_736.jpg",
"instanceName": "frontdoor",
"web_request": {
"regionCoordinates": [
388,
308,
535,
599
],
"numberOfChanges": 4442,
"incoming": 1,
"outgoing": 0,
"timestamp": "1476391523",
"microseconds": "6-438745",
"token": 736,
"pathToImage": "1476391523_6-438745_frontdoor_388-308-535-599_4442_736.jpg",
"instanceName": "frontdoor"
}
}

When you followed the manual installation guide the request logs should be in /home/huginn/huginn/log/production.log, sites like http://requestb.in/ let you inspect the raw data that is send.
When the JSON payload is an array the WebHookAgent will emit an Event per array entry, would that explain the amount of events you are seeing?

Solved, Kerberos was expecting a 200 , not a 201, so it was looping.
Thanks!

Great 😄


Entities sometimes completely stop updating (issue wip)

Describe the bug
Sometimes seemingly at random all entities stop updating
To Reproduce
Steps to reproduce the behavior:

Wait until entities stop updating
Entities stop updating
Can be fixed by reloading the integration but i have no idea what the cause is

Expected behavior
Entities keep updating and don't randomly stop without recovering
Screenshots

After reloading entities start updating again
Version

HA version: 2024.10.4
HA Bosch component version: 0.26.3
Python Bosch HTTP client version: wip

** Debug SCAN **
** IMPORTANT **
Go to Developer tools in Home Assistant, choose Service tab and choose bosch.debug_scan
Download file to your computer and upload it somewhere eg. https://jsonblob.com/
Additional context
Bosch model: wip

This has been happening to me. I have a CT 200.


Debugger UI does not close after stopping debug session (bug introduced in 1.86)

Does this issue occur when all extensions are disabled?:
N/A (debugging requires an extension, but this issue confidently occurs in 1.86.2 and confidently does not occur in 1.85.2 with all other variables constant

VS Code Version: 1.86 and beyond
OS Version: Windows 10

Steps to Reproduce:

Set up development environment for debugging the Raspberry Pi Pico microcontroller using a second Pico as the debug probe
Launch VSCode debugger
Set breakpoints, continue etc. all work fine
Select "Restart"

Wait for device to restart
Select "Stop"

Observe that the debugger UI is not closing, even though the debug server successfully disconnects

If you need some excruciatingly specific steps, you can slog through the precise build environment I've set up down to each application's checksum in my repository here (keeping in mind that the only thing to change to experience the bug is the version of VSCode you are using).

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.90.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.90.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

🐞 Confirmed this bug exists in the latest stable release 1.90.1.  It was introduced in 1.86, and has not yet been resolved.

Sorry for the slow response. Is it still happening in the latest?
Could you check for errors? Likely in the Window or "Extension Host" output channels.
For myself, debug changes in 1.86 https://github.com/microsoft/vscode/commits/release/1.86/src/vs/workbench/contrib/debug

Thanks for taking a look at this 🙂
Yes, I can confirm this still happens in 1.92.2.
Extension Host output after bug on 1.92.2:
2024-08-18 10:59:49.151 [info] Extension host with pid 35876 started
2024-08-18 10:59:49.151 [info] Skipping acquiring lock for XXX\AppData\Roaming\VSCodium\User\workspaceStorage\016a6f85b37bdb91f5423e0a6d312b64.
2024-08-18 10:59:49.323 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-08-18 10:59:49.328 [info] ExtensionService#_doActivateExtension llvm-vs-code-extensions.vscode-clangd, startup: false, activationEvent: 'onLanguage:c'
2024-08-18 10:59:49.449 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2024-08-18 10:59:49.451 [info] ExtensionService#_doActivateExtension adammaras.overtype, startup: true, activationEvent: '*'
2024-08-18 10:59:49.455 [info] ExtensionService#_doActivateExtension ms-vscode.cmake-tools, startup: true, activationEvent: 'workspaceContains:CMakeLists.txt'
2024-08-18 10:59:49.518 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2024-08-18 10:59:49.537 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2024-08-18 10:59:49.819 [info] Eager extensions activated
2024-08-18 10:59:49.865 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 10:59:49.867 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 10:59:49.870 [info] ExtensionService#_doActivateExtension eamodio.gitlens, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 10:59:49.893 [info] ExtensionService#_doActivateExtension mcu-debug.debug-tracker-vscode, startup: false, activationEvent: 'onStartupFinished', root cause: marus25.cortex-debug
2024-08-18 10:59:49.895 [info] ExtensionService#_doActivateExtension mcu-debug.peripheral-viewer, startup: false, activationEvent: 'onStartupFinished', root cause: marus25.cortex-debug
2024-08-18 10:59:49.902 [info] ExtensionService#_doActivateExtension medo64.render-crlf, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 10:59:49.991 [info] ExtensionService#_doActivateExtension mcu-debug.memory-view, startup: false, activationEvent: 'onStartupFinished', root cause: marus25.cortex-debug
2024-08-18 10:59:50.000 [info] ExtensionService#_doActivateExtension mcu-debug.rtos-views, startup: false, activationEvent: 'onStartupFinished', root cause: marus25.cortex-debug
2024-08-18 10:59:50.019 [info] ExtensionService#_doActivateExtension marus25.cortex-debug, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 10:59:50.920 [info] ExtensionService#_doActivateExtension vscode.debug-server-ready, startup: false, activationEvent: 'onDebugResolve'
2024-08-18 11:00:12.555 [error] Error: Invalid debug adapter
    at c.getDebugAdapter (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:2018:136)
    at c.$acceptDAExit (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:2018:35)
    at y._doInvokeHandler (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1909:19555)
    at y._invokeHandler (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1909:19237)
    at y._receiveRequest (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1909:17947)
    at y._receiveOneMessage (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1909:16686)
    at u.value (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1909:14360)
    at o._deliver (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:93:910)
    at o.fire (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:93:1229)
    at r.fire (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:123:17864)
    at G.onmessage (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1925:11327)

  Extension Host output on 1.85 (no bug):
2024-08-18 11:06:57.814 [info] Extension host with pid 10292 started
2024-08-18 11:06:57.814 [info] Skipping acquiring lock for XXX\AppData\Roaming\VSCodium\User\workspaceStorage\016a6f85b37bdb91f5423e0a6d312b64.
2024-08-18 11:06:57.829 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-08-18 11:06:57.833 [info] ExtensionService#_doActivateExtension llvm-vs-code-extensions.vscode-clangd, startup: false, activationEvent: 'onLanguage:c'
2024-08-18 11:06:57.910 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2024-08-18 11:06:57.912 [info] ExtensionService#_doActivateExtension adammaras.overtype, startup: true, activationEvent: '*'
2024-08-18 11:06:57.967 [info] ExtensionService#_doActivateExtension ms-vscode.cmake-tools, startup: true, activationEvent: 'workspaceContains:CMakeLists.txt'
2024-08-18 11:06:58.032 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2024-08-18 11:06:58.045 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2024-08-18 11:06:58.278 [error] [llvm-vs-code-extensions.vscode-clangd] provider FAILED
2024-08-18 11:06:58.278 [error] {"_isCancelled":true,"_emitter":null}
2024-08-18 11:06:58.432 [info] Eager extensions activated
2024-08-18 11:06:58.463 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 11:06:58.464 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 11:06:58.468 [info] ExtensionService#_doActivateExtension eamodio.gitlens, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 11:06:58.512 [info] ExtensionService#_doActivateExtension mcu-debug.debug-tracker-vscode, startup: false, activationEvent: 'onStartupFinished', root cause: marus25.cortex-debug
2024-08-18 11:06:58.514 [info] ExtensionService#_doActivateExtension mcu-debug.peripheral-viewer, startup: false, activationEvent: 'onStartupFinished', root cause: marus25.cortex-debug
2024-08-18 11:06:58.520 [info] ExtensionService#_doActivateExtension medo64.render-crlf, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 11:06:58.615 [info] ExtensionService#_doActivateExtension mcu-debug.memory-view, startup: false, activationEvent: 'onStartupFinished', root cause: marus25.cortex-debug
2024-08-18 11:06:58.627 [info] ExtensionService#_doActivateExtension mcu-debug.rtos-views, startup: false, activationEvent: 'onStartupFinished', root cause: marus25.cortex-debug
2024-08-18 11:06:58.648 [info] ExtensionService#_doActivateExtension marus25.cortex-debug, startup: false, activationEvent: 'onStartupFinished'
2024-08-18 11:07:28.164 [info] ExtensionService#_doActivateExtension vscode.debug-server-ready, startup: false, activationEvent: 'onDebugResolve'
2024-08-18 11:07:47.785 [error] Error: Invalid debug adapter
    at C.getDebugAdapter (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1559:136)
    at C.$acceptDAExit (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1559:35)
    at m._doInvokeHandler (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1567:24876)
    at m._invokeHandler (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1567:24558)
    at m._receiveRequest (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1567:23328)
    at m._receiveOneMessage (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1567:22229)
    at o.value (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1567:20093)
    at d._deliver (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:87:2465)
    at d.fire (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:87:2784)
    at s.fire (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:616:17227)
    at K.onmessage (vscode-file://vscode-app/c:/Program%20Files/VSCodium/resources/app/out/vs/workbench/workbench.desktop.main.js:1663:10861)

The same type of error appears to be reported upon closing the debug session for both 1.85 and 1.92, even though the bug only exists in 1.86+.
My apologies in advance if this does turn out to be an extension bug which only became symptomatic after a VSCode update.

Also, to clarify, I do not know whether the bug was visible in 1.86.0 - My A/B testing only got so far as to be confident that it is present in 1.86.2 and not present in 1.85.2.

I am still using 1.85.2 due to this bug, so I haven't updated since reporting this issue.  @roblourens, let me know if you need any further information from me.

@connor4312 any idea whether anything in Jan/Dec would have been relevant? https://github.com/microsoft/vscode/commits/release/1.86/src/vs/workbench/contrib/debug?before=903b1e9d8990623e3d7da1df3d33db3e42d80eda+35

There was activity last week - @roblourens can we reopen this issue?


NEXT disable combobox multiple prop

Linked Issue
Closes #2963
Description
Disables the Zag-based multiple prop for the Svelte Combobox, as this is an unsupported feature.
Changsets
Instructions: Changesets automate our changelog. If you modify files in /packages, run pnpm changeset in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, bugfix: or chore:.
Checklist
Please read and apply all contribution requirements.

[x] This PR targets the dev branch (NEVER master)
[x] Documentation reflects all relevant changes
[x] Branch is prefixed with: docs/, feat/, chore/, bugfix/
[x] Ensure Svelte and Typescript linting is current - run pnpm ci:check
[x] Ensure Prettier linting is current - run pnpm format
[x] All test cases are passing - run pnpm test
[x] Includes a changeset (if relevant; see above)

Hi,
Do you have an advice on how to implement a combobox with multiple values please ?

@magiceupho from the description above:

Disables the Zag-based multiple prop for the Svelte Combobox, as this is an unsupported feature.

In short, you don't. We may revisit support for this in the future, but right now it's not possible.


Redshift connections randomly set to read-only after upgrade to 7.3.4

System information:

Operating system (distribution) and version: MacOS Catalina 10.15.7
DBeaver version: 7.3.4 CE

Connection specification:

Database name and version: Amazon Redshift 1.0.23412
Driver name: https://s3.amazonaws.com/redshift-downloads/drivers/jdbc/<IP_ADDRESS>8/RedshiftJDBC42-<IP_ADDRESS>8.zip
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
Redshift connections being set to read-only without the setting being checked.

Toggling the Read-only connection box and saving does not fix the issue. There is no way to disable read-only mode.

Resolved by downgrading DBeaver to 7.3.0. Upgrading and downgrading prompt a upgrading and downgrading of the Redshift driver respectively.
As noted below, it seems this is tied to the Redshift driver and not DBeaver itself.
Steps to reproduce, if exist:

Create a connection in a version lower than 7.3.4, make sure Read Only connection is unchecked.
Confirm you can write using this connection.
Upgrade DBeaver to 7.3.4
Connect to above connection and attempt a write operation.

That's interesting.
Upgrading to 7.3.4 prompts for a download of the Redshift driver, and the option available is: https://s3.amazonaws.com/redshift-downloads/drivers/jdbc/<IP_ADDRESS>8/RedshiftJDBC42-<IP_ADDRESS>8.zip
However, when you downgrade to 7.3.0, you're also prompted to download the Redshift driver, except the version available is now: https://s3.amazonaws.com/redshift-downloads/drivers/jdbc/<IP_ADDRESS>9/RedshiftJDBC42-no-awssdk-<IP_ADDRESS>9.jar
Seems that <IP_ADDRESS>9 works, but <IP_ADDRESS>8 is broken. I can create an issue with Amazon and link them to this for reference.
Is there a way to prevent DBeaver from suggesting the broken driver, at least until Amazon publishes a fix for that version, or provides a new one? I'm sure other users either are experiencing or will experience a similar issue.

Also, do you happen to know the process for reporting driver bugs to Amazon?

Looks like driver version <IP_ADDRESS>9 seems to be the last good one. I will revert default download location to it.
Unfortunately I'm not aware about the official process of bug reporting to Amazon. But probably creating a ticket at https://github.com/aws/amazon-redshift-jdbc-driver will work.

verified

I've found a workaround that seems to fix it (temporarily). I'm using version RedshiftJDBC42-no-awssdk-<IP_ADDRESS>3.jar which seems to have the same issue. It is particularly prevalent on sessions you leave unattended for a bit, so might be related to a timeout setting.
Run the following SQL restore your session's ability to 'write' ...
set readonly = 0;
... then get on with your day (until you do it again an hour later).