text:
"Update" to 1.17

This mod already works on 1.17 (except for the version lock), but this just makes the mod officially for 1.17, so any future development work is for 1.17, and so that you can use JDK 16 features.

Oops, I made a boo-boo...

Ok, I fixed the issue

source: gharchive/pull-request

repo: vktec/chonk

license: MIT

license_type: permissive

license_source: github-api


text:
ImmutableType should also implement the Type interface

Because UserType does not extend the Hibernate Type contract, we cannot provide a custom Type for a scalar result in a native SQL query as in the following example:
List<Tuple> tuples = entityManager
.createNativeQuery(
	"SELECT " +
	"  id, " +
	"  account_id, " +
	"  created_on - FIRST_VALUE(created_on) OVER ( " +
	"    PARTITION BY account_id " +
	"    ORDER BY created_on " +
	"    RANGE BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING " +
	"  ) AS since_first_transaction, " +
	"  LAST_VALUE(created_on) OVER ( " +
	"    PARTITION BY account_id " +
	"    ORDER BY created_on " +
	"    RANGE BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING " +
	"  ) - created_on AS until_last_transaction " +
	"FROM account_transaction " +
	"ORDER BY id", Tuple.class)
.unwrap(org.hibernate.query.NativeQuery.class)
.addScalar("since_first_transaction", PostgreSQLIntervalType.INSTANCE)
.getResultList();

The easiest way to fix this is to make the ImmutableType implement the Type contract as well.
This way, we can deal with the No Dialect mapping for JDBC type at the SQL query level, no matter if the associated type implements the Hibernate org.hibernate.type.Type or org.hibernate.usertype.UserType.

Fixed.

Hi, probably not appropriate place for this but it is directly related.
I'm using hypersistence-utils-hibernate-62 with hibernate 6.2. When I try to add custom type as a scalar result:
Query query = em.createNativeQuery(query.unwrap(NativeQuery.class)
		.addScalar("operation_time", PostgreSQLPeriodType.INSTANCE);

Type is not accepted and can not be cast:
The method addScalar(String, BasicTypeReference) in the type NativeQuery is not applicable for the arguments (String, PostgreSQLPeriodType)
or
java.lang.ClassCastException: class io.hypersistence.utils.hibernate.type.interval.PostgreSQLPeriodType cannot be cast to class org.hibernate.metamodel.model.domain.BasicDomainType (io.hypersistence.utils.hibernate.type.interval.PostgreSQLPeriodType and org.hibernate.metamodel.model.domain.BasicDomainType are in unnamed module of loader com.ibm.ws.classloading.internal.AppClassLoader @656f8f18)
Am I doing something wrong?

@mfur I created #609 for this

source: gharchive/issue

authors: mfur vladmihalcea

repo: vladmihalcea/hypersistence-utils


text:
Kotlin with Quarkus  - Unable to determine SQL type name for column

Hi, I have problem with enums using Kotlin with Quarkus
I made enum like in this article: https://vladmihalcea.com/the-best-way-to-map-an-enum-type-with-jpa-and-hibernate/
and I am getting org.hibernate.MappingException: Unable to determine SQL type name for column 'number' of table 'example_table' error. Application seems to work, during tests I also don't see any errors in console, this only happens when running from main

is it expected behaviour?
I made little reproducer of this: https://github.com/DawidStuzynski/enum-imperative/tree/save-enum-warning

Just after submitting the issue I realized that  @Column(columnDefinition = "number") was missing, with it there is no errors
@Column(columnDefinition = "number")

@DawidStuzynski If you're using the PostgreSQLEnumType, then the column should not be a number, but a PostgreSQL ENUM type.
Now, for your mapping:
@Enumerated(EnumType.STRING)
@Type(PostgreSQLEnumType::class)
val number: Number

I don't see why you are mapping it as a Number in the JPA entity mapping. It should be a Java Enum. And, on the DB side, it should be like this:
@Enumerated(EnumType.STRING)
@Column(columnDefinition = "post_status_info")
@Type(PostgreSQLEnumType.class)
private PostStatus status;

where post_status_info is:
CREATE TYPE post_status_info AS ENUM ('PENDING', 'APPROVED', 'SPAM')

Check out this example for more details.
In your workaround, you basically switched to using the standard Enum type from HIbernate that uses the ordinal.

I my example Number enum is postgres type, it is actually misleading. Choosing Number as the enum name was not my best idea
My code is looks like:
enum class Number {
    ONE, TWO, THREE
}

CREATE TYPE number AS ENUM (
    'ONE',
    'TWO',
    'THREE'
    );

I had project where I used Hyper Persistence utils and all worked fine, during refactoring I removed columnDefinition by accident and all integration tests passed so I din't noticed that something is wrong, after some time I run it from main and noticed some weird logs, so after while I made reproducer in one of my test projects and send an issue. After submitting the issue I looked last time at your article that I was based on, and I realized that columnDefinition is missing (previous test didn't showed me that something is wrong), so I closed issue. Sorry for the confusion

@DawidStuzynski The number keyword is reserved, so you might want to change that.

authors: DawidStuzynski vladmihalcea


text:
Add: targets and ignore inference for sparse compression

This PR adds support to automatically infer targets and ignore lists for sparse compression
The lists thus generated will be used to to ignore things like layernorms, and embeddings
The logic for adding to targets:

layer must have sparsity > threshold (set to 20% for now)
layer must follow the sparsity structure defined

Otherwise it's added to the ignore list
Note: We also perform a reduction of the targets, and ignore list to make them cleaner and easily readable inside config.json
The compression_config inside config.json will now look like:
"compression_config": {
    "sparsity_config": {
      "format": "sparse-bitmask",
      "global_sparsity": 0.12233772669884009,
      "ignore": [
        "Embedding",
        "lm_head",
        "LlamaRotaryEmbedding",
        "SiLU",
        "LlamaRMSNorm"
      ],
      "registry_requires_subclass": false,
      "sparsity_structure": "2:4",
      "targets": [
        "Linear"
      ]
    }
  },

After review comments we were able to further simplify compression_config, now we only include modules in ignore list if they are targetted, now the compression config looks like:
  "compression_config": {
    "sparsity_config": {
      "format": "dense",
      "global_sparsity": 0.12233772669884009,
      "ignore": [
        "lm_head"
      ],
      "registry_requires_subclass": false,
      "sparsity_structure": "2:4",
      "targets": [
        "Linear"
      ]
    }
  }

Note: relies on https://github.com/neuralmagic/compressed-tensors/pull/159

Looks good! I'd prefer to call "layers" modules, since layers is already used to describe transformer blocks, but I think readers still understand.

Let's be consistent and use module/submodule over layer wherever possible

@rahul-tuli The Sparsification tests are failing with a different error than the shared memory issue we've been seeing. Can you look into it?

@rahul-tuli The Sparsification tests are failing with a different error than the shared memory issue we've been seeing. Can you look into it?

Fixed!

authors: dsikka rahul-tuli

repo: vllm-project/llm-compressor


text:
[Bug]: Mixtral CUDA fails with latest code when using bfloat16

Your current environment
warnings.warn(
WARNING 04-03 18:34:42 ray_utils.py:70] Unable to import Ray with ModuleNotFoundError("No module named 'ray'"). For multi-node distributed inference, please install Ray with `pip install ray`.
PyTorch version: 2.1.2+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Red Hat Enterprise Linux 9.3 (Plow) (x86_64)
GCC version: (GCC) 11.4.1 20230605 (Red Hat 11.4.1-2)
Clang version: Could not collect
CMake version: version 3.29.0
Libc version: glibc-2.34

Python version: 3.11.8 | packaged by conda-forge | (main, Feb 16 2024, 20:53:32) [GCC 12.3.0] (64-bit runtime)
Python platform: Linux-4.18.0-372.43.1.el8_6.x86_64-x86_64-with-glibc2.34
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA A100-SXM4-80GB
GPU 1: NVIDIA A100-SXM4-80GB

Nvidia driver version: 525.60.13
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Address sizes:                   46 bits physical, 57 bits virtual
Byte Order:                      Little Endian
CPU(s):                          80
On-line CPU(s) list:             0-79
Vendor ID:                       GenuineIntel
Model name:                      Intel Xeon Processor (Icelake)
CPU family:                      6
Model:                           134
Thread(s) per core:              2
Core(s) per socket:              20
Socket(s):                       2
Stepping:                        0
BogoMIPS:                        5600.01
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves wbnoinvd arat avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq la57 rdpid fsrm md_clear arch_capabilities
Virtualization:                  VT-x
Hypervisor vendor:               KVM
Virtualization type:             full
L1d cache:                       2.5 MiB (80 instances)
L1i cache:                       2.5 MiB (80 instances)
L2 cache:                        160 MiB (40 instances)
L3 cache:                        32 MiB (2 instances)
NUMA node(s):                    2
NUMA node0 CPU(s):               0-39
NUMA node1 CPU(s):               40-79
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 Host state unknown
Vulnerability Retbleed:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.1.2+cu121
[pip3] triton==2.1.0
[conda] Could not collectROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.4.0
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    mlx5_0  CPU Affinity    NUMA Affinity
GPU0     X      NV12    PIX     0-39    0
GPU1    NV12     X      NODE    0-39    0
mlx5_0  PIX     NODE     X

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

I'm not sure why it says the CUDA version can't be collected. It's using CUDA 12.2:
| NVIDIA-SMI 525.60.13    Driver Version: 525.60.13    CUDA Version: 12.2     |

🐛 Describe the bug
The latest main seems to fail for me when using Mixtral 8x7b with bfloat16 (it defaults to that dtype since it's in the mixtral config.json), when running in our own docker image.
With the following error:
 File "/workspace/vllm/model_executor/models/mixtral.py", line 315, in forward
    hidden_states, residual = layer(positions, hidden_states,
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/vllm/model_executor/models/mixtral.py", line 274, in forward
    hidden_states = self.block_sparse_moe(hidden_states)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/vllm/model_executor/models/mixtral.py", line 128, in forward
    final_hidden_states = fused_moe(hidden_states,
                          ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/vllm/model_executor/layers/fused_moe/fused_moe.py", line 351, in fused_moe
    gating_output.float(),  # TODO(woosuk): Optimize this.
    ^^^^^^^^^^^^^^^^^^^^^
RuntimeError: CUDA error: invalid device function

@youkaichao ah... yes there could be a difference there w.r.t. how we're building our image, I am checking that and will get back to you, thanks!

repo: vllm-project/vllm


text:
[Hardware][CPU] compressed-tensor INT8 W8A8 AZP support

This PR added the compressed-tensor INT8 W8A8 AZP support and re-enable the compressed-tensor tests in CPU CI.
This PR also move the oneDNN build procedure to the CMake script to achieve out-of-box usage.

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Hi @mgoin , please help to review this PR, thanks :)

Hi @mgoin @ProExpertProg , thanks for your helpful comments, I have fixed them all. Do you have any further comment?

Hi @mgoin , please help to merge this as I rebased it for passing CUDA tests, thanks :)

This seems to break the vLLM CPU docker image.  I upgraded to from 0.6.3 to 0.6.4 and started getting this error:
INFO 11-17 02:41:24 logger.py:37] Received request cmpl-d4613cb5f8e649c9b0e394953626555f-0: prompt: 'How are you?', params: SamplingParams(n=1, presence_penalty=0.0, frequency_penalty=0.0, repetition_penalty=1.0, temperature=1.0, top_p=1.0, top_k=-1, min_p=0.0, seed=None, stop=[], stop_token_ids=[], bad_words=[], include_stop_str_in_output=False, ignore_eos=False, max_tokens=50, min_tokens=0, logprobs=None, prompt_logprobs=None, skip_special_tokens=True, spaces_between_special_tokens=True, truncate_prompt_tokens=None, guided_decoding=None), prompt_token_ids: [2, 6179, 32, 47, 116], lora_request: None, prompt_adapter_request: None.
++ echo '--- Describe Model Pods ---'
++ kubectl describe pod -l app=model
INFO 11-17 02:41:24 async_llm_engine.py:208] Added request cmpl-d4613cb5f8e649c9b0e394953626555f-0.
ERROR 11-17 02:41:24 multiproc_worker_utils.py:116] Worker VllmWorkerProcess pid 29 died, exit code: 1
INFO 11-17 02:41:24 multiproc_worker_utils.py:120] Killing local vLLM worker processes
ERROR 11-17 02:41:24 async_llm_engine.py:65] Engine background task failed
ERROR 11-17 02:41:24 async_llm_engine.py:65] Traceback (most recent call last):
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/async_llm_engine.py", line 55, in _log_task_completion
ERROR 11-17 02:41:24 async_llm_engine.py:65]     return_value = task.result()
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/async_llm_engine.py", line 872, in run_engine_loop
ERROR 11-17 02:41:24 async_llm_engine.py:65]     result = task.result()
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/async_llm_engine.py", line 795, in engine_step
ERROR 11-17 02:41:24 async_llm_engine.py:65]     request_outputs = await self.engine.step_async(virtual_engine)
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/async_llm_engine.py", line 347, in step_async
ERROR 11-17 02:41:24 async_llm_engine.py:65]     outputs = await self.model_executor.execute_model_async(
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/cpu_executor.py", line 308, in execute_model_async
ERROR 11-17 02:41:24 async_llm_engine.py:65]     output = await make_async(self.execute_model
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
ERROR 11-17 02:41:24 async_llm_engine.py:65]     result = self.fn(*self.args, **self.kwargs)
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/cpu_executor.py", line 220, in execute_model
ERROR 11-17 02:41:24 async_llm_engine.py:65]     output = self.driver_method_invoker(self.driver_worker,
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/cpu_executor.py", line 377, in _async_driver_method_invoker
ERROR 11-17 02:41:24 async_llm_engine.py:65]     return driver.execute_method(method, *args, **kwargs).get()
ERROR 11-17 02:41:24 async_llm_engine.py:65]   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/multiproc_worker_utils.py", line 54, in get
ERROR 11-17 02:41:24 async_llm_engine.py:65]     raise self.result.exception
ERROR 11-17 02:41:24 async_llm_engine.py:65] ChildProcessError: worker died
Unable to get JIT kernel for brgemm. Params: M=5, N=5, K=64, str_a=1, str_b=1, brgemm_type=1, beta=0, a_trans=0, unroll_hint=1, lda=2304, ldb=5, ldc=5, config=0, b_vnni=02024-11-17 02:41:24,642 - __init__.py - asyncio - ERROR - Exception in callback functools.partial(<function _log_task_completion at 0x7f83813afd90>, error_callback=<bound method AsyncLLMEngine._error_callback of

The unable to get JIT kernel for brgemm may be the most relevant part?

One notable change was that previously this variable ONEDNN_ENABLE_JIT_PROFILING set to on and this PR turns it off.
Since my error message says JIT in it that's why I thought it may be related. Note I have no understanding of the code. So this may not be relevant at all.

@samos123 Looks like the W8A8 unit tests are normal on the main branch.
Can you provide your service setup command and your CPU information? I will try to reproduce it.
And you can set a env ONEDNN_VERBOSE=all to get more detail oneDNN log.

You can reproduce the issue like this:
docker run --rm -d --name vllm -p 8000:8000 -e VLLM_WORKER_MULTIPROC_METHOD=spawn -e ONEDNN_VERBOSE=all substratusai/vllm:v0.6.4.post1-cpu --model facebook/opt-125m --disable-frontend-multiprocessing

curl -v --fail-with-body --show-error http://localhost:8000/v1/completions -H 'Content-Type: application/json' -d '{
  "model": "facebook/opt-125m",
  "prompt": "San Francisco is a",
  "max_tokens": 7,
  "temperature": 0
}'

Let me know if you need any more details. I will add the env variable

@samos123 I didn't reproduce the problem on my platform.
Can you try to run examples/offline_inference.py? The multi-process of serving mode might make the oneDNN log invisible.

using offline_inference shows the same logs:
INFO 11-19 15:39:11 selector.py:221] Cannot use _Backend.FLASH_ATTN backend on CPU.
INFO 11-19 15:39:11 selector.py:156] Using Torch SDPA backend.
INFO 11-19 15:39:12 weight_utils.py:243] Using model weights format ['*.bin']
Loading pt checkpoint shards:   0% Completed | 0/1 [00:00<?, ?it/s]
/usr/local/lib/python3.10/dist-packages/vllm/model_executor/model_loader/weight_utils.py:425: FutureWarning: You are using `torch.load` with `weights_only=False` (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for `weights_only` will be flipped to `True`. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via `torch.serialization.add_safe_globals`. We recommend you start setting `weights_only=True` for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
  state = torch.load(bin_file, map_location="cpu")
Loading pt checkpoint shards: 100% Completed | 1/1 [00:00<00:00,  3.08it/s]
Loading pt checkpoint shards: 100% Completed | 1/1 [00:00<00:00,  3.08it/s]

INFO 11-19 15:39:12 cpu_executor.py:205] # CPU blocks: 7281
Processed prompts:   0%|              | 0/4 [00:00<?, ?it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]
Unable to get JIT kernel for brgemm. Params: M=6, N=6, K=64, str_a=1, str_b=1, brgemm_type=1, beta=0, a_trans=0, unroll_hint=1, lda=2304, ldb=6, ldc=6, config=0, b_vnni=0

Note this happens for me on both Github actions and on local machine. So not sure if it's platform specific. I'm leaning towards something in my docker build is different.
Do you try with using docker build and run? I did notice that vLLM has a test case that would have caught this issue so likely something wrong downstream.

Seems previously we always build and included oneDNN but after this PR this only happens if AVX512_FOUND is set. Is this expected?

@samos123 the oneDNN included in the CMake script is used for building compressed-tensor W8A8 kernels. You are using a normal opt-125m model so they are not related. In fact pytorch binary also links oneDNN statically, so you are using this oneDNN actually.
looks like your offline_inference output didn't contain oneDNN logs, please check whether ONEDNN_VERBOSE=all is set.
My tests are also inside a docker container, both serving mode and offline inference mode work normally on my platform.

I did have ONEDNN_VERBOSE=all set when using offline_inference. I suspect oneDNN isn't correctly included when the place that's building the docker image does not have AVX512_FOUND but does have AVX2_FOUND.
I have been doing various tests using Github actions here: https://github.com/substratusai/vllm-docker/pull/40
Let me try on my AMD Ryzen laptop.

I can reproduce this with vllm main branch. So I filed a bug here: https://github.com/vllm-project/vllm/issues/10478
Not sure if it's related to this PR or not, but this was the main thing that stood out when comparing v0.6.3 and v0.6.4.


text:
constr_TYPE.h:97:2: error: unknown type name 'der_type_encoder_f'

Dear all,
Compilation stops in this error. I cant find der_type_encoder_f in any file in order to include it.
Do you have any idea on how to resolve this ?
Thank you

Hi @diamantisk,
It is defined in skeletons/der_encoder.h
typedef asn_enc_rval_t (der_type_encoder_f)(
		struct asn_TYPE_descriptor_s *type_descriptor,
		void *struct_ptr,	/* Structure to be encoded */
		int tag_mode,		/* {-1,0,1}: IMPLICIT, no, EXPLICIT */
		ber_tlv_tag_t tag,
		asn_app_consume_bytes_f *consume_bytes_cb,	/* Callback */
		void *app_key		/* Arbitrary callback argument */
	);

Ok i see, but this file isnt copied to the folder where asn1c compiler generates the C equivalents of ASN1 sources. Is this normal?

but this file isnt copied to the folder where asn1c compiler generates the C equivalents of ASN1 sources. Is this normal?

Usually it is, If you see errors like
WARNING: Cannot find standard modules in ../asn1c/../skeletons/standard-modules
WARNING: Cannot read file-dependencies information from ../asn1c/../skeletons

you could try to specify the skeletons directory with -S /path/to/skeletons/
  -S <dir>              Directory with support (skeleton?) files
                        (Default is "/usr/local/share/asn1c")

authors: diamantisk velichkov


text:
Locations?

I love this, now is there a way to make it pull all the images of all the locations?
Can Ijust add this in the code where cards are change it to this https://marvelsnapzone.com/locations/
I tried adding
url = 'https://marvelsnapzone.com/locations'
def download_images(urls, dir_name='marvel-snap-locations'):
and it didn't work
also tried this and nothing
import re
import requests
import os
from bs4 import BeautifulSoup
from selenium import webdriver
from selenium.webdriver.chrome.options import Options
def scrap():
url = 'https://marvelsnapzone.com/locations'
chrome_options = Options()
chrome_options.add_argument('--headless=new')
chrome_options.add_argument('--disable-dev-shm-usage')
chrome_options.add_argument('--disable-extensions')
chrome_options.add_argument('--disable-gpu')
browser = webdriver.Chrome(options=chrome_options)
browser.get(url)
html = browser.page_source
soup = BeautifulSoup(html, 'html.parser')
# only look for link with a 'simple-card' class; those are the cards
links = soup.findAll('a', {'class': 'simple-card'})

characters = []
for link in links:
    character = {
        # capitalize every word
        'name': link['data-name'].title(),
        'cost': link['data-cost'],
        'power': link['data-power'],
        # strip html tags and capitalize
        'ability': capitalize(BeautifulSoup(link['data-ability'], 'html.parser').text),
        # remove query string
        'url': link['data-src'].split('?')[0],
        'status': link['data-status'],
        'source': link['data-source']
    }
    characters.append(character)
    # print(character)

image_urls = []
for character in characters:
    image_urls.append(character['url'])

download_images(image_urls)

return characters

def capitalize(text):
punc_filter = re.compile('([.!?;:]\s*)')
split_with_punctuation = punc_filter.split(text)
for i, j in enumerate(split_with_punctuation):
if len(j) > 1:
split_with_punctuation[i] = j[0].upper() + j[1:]
text = ''.join(split_with_punctuation)
return text
def download_images(urls, dir_name='marvel-snap-locations'):
if not os.path.exists(dir_name):
os.mkdir(dir_name)
print("Directory '", dir_name, "' created ")
else:
print("Directory '", dir_name, "' already exists")
for url in urls:
    response = requests.get(url)
    if response.status_code:
        # take the last part of the URL as file name
        fp = open(dir_name + '/' + url.rsplit('/', 1)[-1], 'wb')
        fp.write(response.content)
        fp.close()

def create_cards(cards):
url = 'http://localhost:8080/v1/cards'
for card in cards:
if card['status'] == 'released':
body = {
'name': parse_name(card['name']),
'cost': card['cost'],
'power': card['power'],
'ability': parse_ability(card['name'], card['ability']),
'series': parse_source(card['source']),
'imageUrl': card['url']
}
requests.post(url, json=body)
print(body)
# print(card['name'] + ' created.')

ok lmao I did IT!!!!!!!
`import re
import requests
import os
from bs4 import BeautifulSoup
from selenium import webdriver
from selenium.webdriver.chrome.options import Options
def scrap():
url = 'https://marvelsnapzone.com/locations'
chrome_options = Options()
chrome_options.add_argument('--headless')
chrome_options.add_argument('--disable-dev-shm-usage')
chrome_options.add_argument('--disable-extensions')
chrome_options.add_argument('--disable-gpu')
browser = webdriver.Chrome(options=chrome_options)
browser.get(url)
html = browser.page_source
soup = BeautifulSoup(html, 'html.parser')
# only look for link with a 'simple-card' class; those are the cards
links = soup.findAll('a', {'class': 'simple-card'})

characters = []
for link in links:
    character = {
        # capitalize every word
        'name': link['data-name'].title(),
        'cost': link['data-cost'],
        'power': link['data-power'],
        # strip html tags and capitalize
        'ability': capitalize(BeautifulSoup(link['data-ability'], 'html.parser').text),
        # remove query string
        'url': link['data-src'].split('?')[0],
        'status': link['data-status'],
        'source': link['data-source']
    }
    characters.append(character)
    # print(character)

image_urls = []
for character in characters:
    image_urls.append(character['url'])

download_images(image_urls)

return characters

def capitalize(text):
punc_filter = re.compile('([.!?;:]\s*)')
split_with_punctuation = punc_filter.split(text)
for i, j in enumerate(split_with_punctuation):
if len(j) > 1:
split_with_punctuation[i] = j[0].upper() + j[1:]
text = ''.join(split_with_punctuation)
return text
def download_images(urls, dir_name='marvel-snap-locations'):
if not os.path.exists(dir_name):
os.mkdir(dir_name)
print("Directory '", dir_name, "' created ")
else:
print("Directory '", dir_name, "' already exists")
for url in urls:
    response = requests.get(url)
    if response.status_code:
        # take the last part of the URL as file name
        fp = open(dir_name + '/' + url.rsplit('/', 1)[-1], 'wb')
        fp.write(response.content)
        fp.close()

def create_cards(cards):
url = 'http://localhost:8080/v1/cards'
for card in cards:
if card['status'] == 'released':
body = {
'name': parse_name(card['name']),
'ability': parse_ability(card['name'], card['ability']),
'series': parse_source(card['source']),
'imageUrl': card['url']
}
requests.post(url, json=body)
print(body)
# print(card['name'] + ' created.')
def parse_name(name):
# character name manual fix
if name == 'Avengers Compound':
return 'Avengers-Compound'
return name
def parse_ability(name, ability):
# provide 'No ability' instead of empty string
if ability == '':
ability = 'No ability'
# The Collector ability manual fix
if name == 'Asteroid M':
ability = 'When you play a 3 or 4-Cost card, move it here.'
return ability
def parse_source(source):
if source.contains('Collection Level 1-14') or source.contains('Starter Card') or source.contains('Recruit Season'):
return 'Starter'
elif source.contains('Pool 1'):
return 'Series 1'
elif source.contains('Pool 2'):
return 'Series 2'
elif source.contains('Pool 3'):
return 'Series 3'
elif source.contains('Pool 4'):
return 'Series 4'
elif source.contains('Pool 5'):
return 'Series 5'
elif source.contains('Season Pass'):
return 'Season Pass'
else:
return ''
if name == 'main':
characters = scrap()
# create_cards(characters)
`

repo: vlmaier/marvel-snap-scrapr


text:
Problem with .env variables with backslash

Hello,
I have a Laravel app with a .env that contains :  DB_DATETIME_UTC='m/d/Y H:i:s\Z'
It displays this error :
The environment file is invalid! Failed to parse dotenv file due to an unexpected escape sequence. Failed at ['m/d/Y H:i:s\Z'].
If I remove the backslash it works fine but I need the backslash to be in that variable.

You'll need to escape the backslash with a backslash. 'm/d/Y H:i:s\\Z'

thanks, it worked very well for me

Note that in the latest version, escaping backslashes in single quoted strings is not required. Just in unquoted and double quoted strings.

Use Double Backslashes in Strings
In PHP strings, a single backslash is used as an escape character. To use a literal backslash, you need to escape it by using double backslashes (\).

Example:
$path = "C:\\path\\to\\directory";

Use Forward Slashes
PHP can handle forward slashes (/) in file paths on Windows. Using forward slashes can help avoid the issue of escaping backslashes.

Example:
$path = "C:/path/to/directory";

authors: GrahamCampbell anibalmorales parthkharecha ybert

repo: vlucas/phpdotenv

license_source: bigquery


text:
Section 5: Managing EC2 at Scale - SSM

Managing EC2 at Scale - Systems Manager
1 h

Ready, a learned a lot!

repo: vmunozvaleria/sysops-prep

license: Unlicense


text:
[Flow-Aggregator] Add template fields of stats

This PR is a follow-up fix for #1636
When bumping go-ipfix to v0.4.2, several new template fields of stats are introduced. Exporting process in flow aggregator will log errors when having sanity check since field count does not match for template and data, which causes e2e tests to fail. Adding template fields of stats will solve that problem.
Tested with @dreamtalen on this fix.

Codecov Report

:exclamation: No coverage uploaded for pull request base (feature/flow-aggregator@ad052b2). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                     @@
##             feature/flow-aggregator    #1676   +/-   ##
==========================================================
  Coverage                           ?   40.41%
==========================================================
  Files                              ?      107
  Lines                              ?    13150
  Branches                           ?        0
==========================================================
  Hits                               ?     5315
  Misses                             ?     7357
  Partials                           ?      478

Flag
Coverage Δ

unit-tests
40.41% <0.00%> (?)

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

Yongming's e2e tests PR is blocked because of this issue. As all tests are passing and it is a straightforward fix, merging this immediately.

authors: codecov-io srikartati zyiou

repo: vmware-tanzu/antrea


text:
[Docs] Provide a linkable non-version scoped page for each package

Description
This is a suggestion. It would be nice if each package had a higher level "landing page" that wasn't scoped to a particular version or an evergreen "latest" version. For example, I want to be able to write documentation that instructs users to install the latest version of Contour from TCE and link them to it. Right now I can only link to a specific version so anytime Contour is updated I need to update the link on my end.
Location
This relates to all of the package pages in general.
Additional Context
It would be nice if there was a "latest" version in this drop down or if the main package name was a link.

This sounds like a good idea. @seemiller should we update our docs automation to make the latest version of package's README the landing page?
I think this will likely be pushed out to v0.12.0 or later as we figure out higher level versioning of TCE docs, too.

authors: nrb tcdowney

repo: vmware-tanzu/community-edition


text:
Unmanaged Clusters - Kapp Controller Cluster DNS issue

Bug Report
Kapp Controller is run on host network in TCE. there is an issue with Kapp Controller config that doesnt allow an app or package to reference a cluster DNS name (eg. http://source-controller-manager-artifact-service.source-system.svc.cluster.local./imagerepository/demo01/tanzu-java-web-app-delivery/c72f8fee9ed3d9d5af40d807fc8e47617af1d8ba42357d1da84bae2a9e4a9438.tar.gz).
In Tanzu Framework PR 1672 it seems this was fixed however this doesnt work on TCE 0.12.rc2. i dont have an older TCE env right now but believe this used to work. i manually changed the dnsPolicy to the correct value of ClusterFirstWithHostNet from what is set by UC today (ClusterFirst) and everything works.
Is this indeed a regression in the Kapp Controller installation?
While i have tested this with TAP 1.1 I'm pretty sure the same issues will occur with app toolkit as it happens when the cartographer deliverable stamps out the Carvel App CR to apply the manifests of the knative service which which are supplied via a flux source controller blob URL using the in cluster DNS name

Expected Behavior
for Kapp Controller to be able to resolve cluster DNS records

Steps to Reproduce the Bug

install an unmanaged-cluster using 0.12.rc2
get the current dnsPolicy setting

kubectl get pod -n tkg-system -l app=kapp-controller -o json | jq .items[0].spec.dnsPolicy

view the resolv.conf in the pod

kubectl exec -it $(kubectl get po -n tkg-system -l app=kapp-controller -o name --no-headers) -n tkg-system -- cat /etc/resolv.conf

Create an app that uses a local source such as fluxcd source controller

Screenshots or additional information and context

Environment Details

Build version (tanzu version):
Deployment (Managed/Unmanaged cluster):
Infrastructure Provider (Docker/AWS/Azure/vSphere):
Operating System (client):

Diagnostics and log bundle

We'll take a look into this issue and determine what's up!

authors: seemiller vrabbi


text:
#74 NPT-696: Remove hardcoded paths from playground

All the getting started documents have hardcoded paths
mkdir -p $HOME/test-datamodel/orgchart && cd $HOME/test-datamodel/orgchart
As requested the paths are to be user-defined
export WORKDIR=$HOME/work/graph-test
mkdir -p $WORKDIR/test-datamodel/orgchart && cd $WORKDIR/test-datamodel/orgchart

Closes #74


text:
Show octant route history in the header

What this PR does / why we need it:

Updates page title to be more descriptive.
Show a history dropdown in the header displaying the last 10 visited pages.
Applications detail page has a generated breadcrumb and hence a title.

Which issue(s) this PR fixes

Fixes #2472

Consider the following scenario:
The user has switched namespaces multiple times then proceeded to visit cert-manager service followed by a cert-manager deployment.

Two approaches come to mind for tacking this problem:

Create a history for each namespace
Add more metadata about namespace scoped paths/objects such that one overview can be distinguished from another

Adding namespace to the history is straightforward as it is already a part of content response and since history is for octant app, showing scoped history makes sense.

Please add a changelog entry for this.

@GuessWhoSamFoo  @lenriquez This feature can be improved further by using local storage so that the history is not lost on page refresh. I'm working on adding this as this greatly improve the experience.

One final task this, needs prettier run
[warn] Code style issues found in the above file(s). Forgot to run Prettier?```

repo: vmware-tanzu/octant


text:
ensure that all of the environment variables that are covered in the documentation also exist in the helm charts with default values

For example, according to the docs
VSECM_SAFE_SVID_PREFIX: Both VSecM Sentinel, VSecM Safe, and workloads use this environment variable.
However, in safe’s helm charts this does not exist in the values.yaml
Also make sure env vars are in alphabetical order in the values yaml (to be consistent with the docs).

Done.

repo: vmware-tanzu/secrets-manager


text:
Add an e2e tests using a sha

What this PR does / why we need it
This PR adds a new plugin-with-sha plugin to the local test central repos.
It also has the E2E tests install that plugin to confirm installation using a sha reference works in the normal scenario but also in an airgap scenario.
These tests are meant to make sure we can move to using shas in the future, if we choose too.
Which issue(s) this PR fixes

Fixes # N/A
Describe testing done for PR
I ran make start-test-central-repo and checked that the following repos all had a plugin-with-sha plugin that used a sha in the DB:

localhost:9876/tanzu-cli/plugins/central:small
localhost:9876/tanzu-cli/plugins/central:large
localhost:9876/tanzu-cli/plugins/airgapped:small
localhost:9876/tanzu-cli/plugins/airgapped:large

Then, since this PR only adds E2E tests, I verified that CI passed and checked that the new tests have been properly run by looking at the logs.
Release note

E2E test of plugin installation using a sha reference have been added.

Additional information
Special notes for your reviewer

This is ready for review

repo: vmware-tanzu/tanzu-cli


text:
Add ytt getting started and leigh

Can I get a review? I also can't get it to successfully build locally.

I created an Issue for this piece, linked it to this PR, and put it in our content planning board. This Git Hub Issue includes a checklist for content submissions, as well as what we do for the review. @tiffanyfay please take a look at the list and verify those items are complete (reviews, etc). There is more info on these in our wiki. These are changes that have come about fairly recently, so apologies for dropping it all on you. Tried to make it as straight forward as possible with the list in the issue, but we are still adjusting things. Let us know if we can help at all through the process, or if we can make this process better/easier.

Also, if you need a hand getting your local builds working, happy to Zoom and see if we can get it up and running. Find me on Slack if you want :)

authors: anthonyvetter tiffanyfay

repo: vmware-tanzu/tanzu-dev-portal


text:
Reintroduce CfApiClient for select operations

As a part of adding support for V3 of the Cloud Controller API to this VSIX extension, it feels important to change those portions of the CfCliService which use cf curl to get lists of orgs/spaces/apps.
In particular, the current strategy for requesting orgs uses a hard-coded CF command which indicates that communication with the Cloud Controller should happen using V2 of the API: curl /v2/organizations -v. The response from this request includes URLs that tell our extension how to request additional information for any spaces in an org, but since this response conforms to the V2 format, these URLs contain V2 endpoints, not V3 endpoints.
For example:
REQUEST: [2021-04-21T10:15:31-04:00]
GET /v2/organizations HTTP/1.1
...

RESPONSE: [2021-04-21T10:15:31-04:00]
HTTP/1.1 200 OK
...
{
  "total_results": 4,
  "total_pages": 1,
  "prev_url": null,
  "next_url": null,
  "resources": [
    {
      "metadata": {
       ...
      },
      "entity": {
        "name": "org-1",
        ...
        "spaces_url": "/v2/organizations/afa4fdad-2d87-4f3c-8ca7-c67210a86e39/spaces",
        "domains_url": "/v2/organizations/afa4fdad-2d87-4f3c-8ca7-c67210a86e39/domains",
        ...
      }
    },
...

^ notice that the spaces_url field starts with "/v2", not "/v3". This pattern with orgs/spaces repeats for spaces/apps, enforcing that all CC API communication happens over V2.
So it's worth revisiting the code that uses this cf curl /v2/organizations -v endpoint to find a way to support (ideally encourage) CC communication using API V3. While this should be totally possible using the CC API communication system we have in place today (i.e. using the CF CLI to issue cf curl commands), the team has identified some reasons why it might make sense to consider using an alternative strategy:
This Miro board makes a case for the potential benefits of using hand-built HTTP requests to request org, spaces & apps. To be clear, the proposed strategy isn't to replace CfCliService, it would be a hybrid strategy that would use the CF CLI for certain requests (e.g. those which won't be made concurrently) and plain HTTP requests for other requests (esp. those that need to run concurrently/quickly).

Deploying an app should continue to be orchestrated by the CF CLI because it's a complex operation that the CLI can handle with ease.
The login operation should continue to be orchestrated by the CF CLI for now because it has the potential to get fairly complex (e.g. with the addition of different ways to log in like SSO) & the CF CLI is already able to handle additional login complexity.
Get orgs should happen as a plain HTTP request since it could be made concurrently with requests to get orgs for other CF instances (this is faster & simpler to parallelize without the CF CLI)
Get spaces should happen as a plain HTTP request since it could be made concurrently with requests to get spaces for other orgs (this is faster & simpler to parallelize without the CF CLI)
Get apps should happen as a plain HTTP request since it could be made concurrently with requests to get apps for other spaces (this is faster & simpler to parallelize without the CF CLI)
Starting/stopping/deleting apps all have the potential to create race conditions around the value for "currently-targeted space", so if we ever want to allow users of this extension to perform concurrent operations on apps in different spaces, it'll make more sense to have these operations happen via regular HTTP requests (able to specify apps by guid & will get responses faster than cf curl)


text:
App level alerts no longer centered horizontally (regression)

Describe the bug
This is a regression bug introduced by https://github.com/vmware/clarity/commit/1590daed127964ec1b5f4fa7df9422ec974057e8
The flex-basis: 100% causes the .alert-text to grow to its maximum width, moving the icon and text to the left, while the .alert-actions are pushed to the right.
How to reproduce
Have a look at the App-Level Alerts section in the clarity documentation (https://clarity.design/documentation/alerts).
This is the current style:

Expected behavior
Setting flex-basis: auto for the .alert-text element in the browser debug tools causes the icon, text and actions to be centered.

Versions
App

Clarity: 3.1.3

There is a workaround fix for this and the Clarity Core implementation of alerts can also be used to avoid this issue. See https://clarity.design/core-components/alert/.

authors: erabl-identos gnomeontherun

repo: vmware/clarity


text:
Add a skip link within the header

Summary

What is the change: Include a skip link within the header code
Why should it go in Clarity? Skip links must be included as the first focusable element at the top every page in order to be accessible. E2E stories are requirement and this is a must-have for consistency.
Does this change impact existing behaviors? If so how? This element becomes the first focusable element in lieu of other elements
If this change introduces a new behavior, is this behavior accessible? This behavior is improves accessibility for all products

Use case
A person who only uses a keyboard (instead of a mouse) will find it easier/faster to navigate to the main content area.
Examples
Internal link removed
Workarounds
Each product team must implement this on their own in order to implement accessibility compliance.

Skiplink on Clarity docs site:
https://github.com/vmware/clarity/issues/3153#issuecomment-471000263

The feature request here has been captured into our list and we’re going to take it into consideration as we develop Clarity Core capabilities. In an effort to clean up our backlog and focus our attention, I’m going to close this as captured in our feature requests. Please follow our development and releases to see when we release relevant components to make this possible. Future feature requests can be made in our GitHub Discussions.

authors: colinreedmiller gnomeontherun scroniser


text:
VIB signing

ESX VIB is not signed. Need to setup process to sign VIB automatically for each tagged release.
RPM and Deb files also need signing. Please see https://github.com/vmware/docker-volume-vsphere/issues/273#issuecomment-289175029

We have a solution for signing the artifacts for the upcoming beta. A more formal workflow is being worked on for GA. Once the binaries are built, I will upload the signed binaries to github releases.

Let's keep it open until we figure out a process to sign binaries.

starting vDVS 0.13 we are recommending to use managed docker volume plugin by pulling from docker store so updating the title to have signing only for VIB.

when the artifacts is ready for VIB, it will be signed by vmware EE team. Following each releases, signed VIB should be uploaded to bintray for download.

authors: kerneltime pdhamdhere shuklanirdesh82

repo: vmware/docker-volume-vsphere


text:
How to limit the number of replication job logs

Hi All, We have more than 2M replication job logs, is the any configuration property to limit the number of replication logs to keep in the filesystem?
Thanks.

Currently not, you'll have to remove the log manually from the filesystem, we'll think about how to better support large-scale usage, but it's a systematic work so will need some time to design.

Yep

@roldancer in the next version the job logs will be swept regularly, but that means after that the log will be gone, I assume that's acceptable?

authors: reasonerjt roldancer

repo: vmware/harbor


text:
Update REST API State digram to include Execution API

What is the feature request? What problem does it solve?
We have a diagram that describes the relationships between different API components - https://raw.githubusercontent.com/wiki/vmware/versatile-data-kit/vdk-data-job-lifecycle-state-diagram.png
The purpose of the diagram is to help users understand better how the API works and how it is expected to be used (describing the usual data engineering work flow)
It would be good to describe how Execution API fits. If it is too much one diagram we can split it in two.

Triaged. Closed as stale.

authors: sabadzhiev tozka

repo: vmware/versatile-data-kit


text:
control-service: graphql add execution fail/success query

why: Users requested the ability to produce reports
based on data job execution failure/success numbers.
This is a part of the graphQL epic.
what: added a query in the JobExecutionRepository which
retrieves the status of executions based on a certain filter
criteria. Considered to count the execution statuses separately
in two different queries, however decided counting them toghether
wouldn't impose a performance penalty and is more convenient
this way, since DB caching should produce better results as we only
query the DB per data job name once and return only the status
numbers.
testing: added unit test.

Is there github issue for this ticket? Can you link it?

Do you think this approach is better than the one describe in #424? Why?

Is there github issue for this ticket? Can you link it?

This issue is a part of #424, however we don't want to close it when we merge this.

Do you think this approach is better than the one described in #424? Why?

I've updated the query.


text:
Add _with_func methods for generating textual output of MIR

It is nice there are methods to output the binary MIR format via a writer function as described by MIR_write_with_func which is helpful for bindings to other languages where passing a FILE *f across the language barrier is annoying.
It would be nice if there were a similar method to write the textual output from MIR_output to a writer function.

Sorry for delay with the answer and thank you for sharing your thoughts and proposal for MIR improvement.
This is not a big work, I can implement it soon when I resume my work on MIR project (approximately in a month).
You can also implement it by yourself and send me  a pull request if you want to see it faster.

repo: vnmakarov/mir


text:
内盘ctp的连接，是否可以修改成不获取之前成交、委托的方式

环境

操作系统: 如Windows 10

Issue类型
三选一：Enhancement
预期程序行为
群主，您好
内盘ctp的连接，是否可以修改成不获取之前成交、委托的方式，这样在登录的时候比较节省性能，另外也让机器负荷变小，虽然下午收盘就又是第二个交易日不会再有之前的交易记录了，，，但是每天早上9点前开盘的登录，因为成交记录、委托的撤单太多，导致大概得5分钟才能登录好，，，如果是盘中出了问题必须重启，那就更是悲催的了。
希望vnpy能够从官方版本上进行修改。
如果vnpy确定不修改了，请您指导下该如何修改，谢谢！

应该是修改这个地方吧。
///订阅私有流。
///@param nResumeType 私有流重传方式
///        THOST_TERT_RESTART:从本交易日开始重传
///        THOST_TERT_RESUME:从上次收到的续传
///        THOST_TERT_QUICK:只传送登录后私有流的内容

应该是修改这个地方吧。
///订阅私有流。
///@param nResumeType 私有流重传方式
///        THOST_TERT_RESTART:从本交易日开始重传
///        THOST_TERT_RESUME:从上次收到的续传
///        THOST_TERT_QUICK:只传送登录后私有流的内容

可以，修改这里两个订阅函数中的订阅模式（整数）即可：
https://github.com/vnpy/vnpy/blob/f8f76e6b71ff16a5066187b253371e0b956f12ef/vnpy/gateway/ctp/ctp_gateway.py#L757-L760

authors: raycool stone3536 vnpy

repo: vnpy/vnpy

license: mit


text:
Is AV1 supported?

as the title says.
according to some docs/tutorials av1 should give better quality at the same bitrate or same quality at a lower bitrate.

from some digging in obs-studio's bugtracker

https://github.com/obsproject/obs-studio/issues/11186
https://github.com/obsproject/obs-studio/issues/11186

both say AV1 is not supported by mpeg-ts, but there is:

https://github.com/AOMediaCodec/av1-mpeg2-ts

this one claims to support AV1 https://softvelum.com/nimble/srt/

You can absolutely transport AV1 over SRT and relay with srtrelay. But support in streaming/player applications is the main issue. Most only support SRT with mpegts, and yes there is a spec for AV1 in mpegts but I think its not widely supported yet.

authors: darix iSchluff

repo: voc/srtrelay


text:
Always support sentiment

In the __init__ we have the following code:
if self.agent.get_agent_config().track_bot_sentiment:
            self.sentiment_config = (
                self.synthesizer.get_synthesizer_config().sentiment_config
            )
            if not self.sentiment_config:
                self.sentiment_config = SentimentConfig()
            self.bot_sentiment_analyser = BotSentimentAnalyser(
                emotions=self.sentiment_config.emotions
            )

This seems to me that we can get a SentimentConfig even if the synthesizer has no sentiment_config, e.g. it's enough that we have track_bot_sentiment on agent. But in the start method, we only start tracking sentiment if the synthesizer has the sentiment_config. So I propose a change that it will start tracking if self.sentiment_config exists. This allows us to track sentiment regardless if the synthesizer is configured for it or not.

Also I note that we get warnings from the line self.update_bot_sentiment() as it's not awaited, e.g like this RuntimeWarning: coroutine 'StreamingConversation.update_bot_sentiment' was never awaited   self.update_bot_sentiment(). So maybe we should add an await to it?

thanks @ripperdoc! we'll get to this soon :)

repo: vocodedev/vocode-python


text:
Option to insert tags when comma is inserted

Is there a way to insert a tag when comma is typed?

Not at the moment, but this is good idea I guess. I'll implement it in the next release.

Can the same be done for blur event?

authors: 4unkur AlexMordred libin-techversant

repo: voerro/vue-tagsinput


text:
setVisible seems recursive

hello,
I use setVisible on a hidden panel, and all its hidden children appear although they are defined as visible="false" and should appear later in the code, not when the parent shows up
    <layer id="nodesInfosLayer" backgroundColor="#0000" childLayout="absolute">
        <panel id="nodesInfosPanel" width="100" height="100" backgroundColor="#0000" childLayout="absolute" visible="false">
            <panel id="hudGlassPanel" x="35" y="-43" width="160" height="133" backgroundColor="#0000" childLayout="absolute" visible="false">
                <image id="hudGlassImage" x="0" y="0" width="160" height="133" filename="Textures/hud_glass.png" />
            </panel>
        </panel>
</layer>

is there a way to preserve children states when parent.setVisible(true) is called ?
so far, I set the parent visible and manual set invisiible the children, wich is tedious and prone to errors
also it does not make sens to have children visible while parent is not
thanks

Which Nifty version do you use?
The whole recursive setVisible thing should be fixed in 1.4.x, see this commit for details https://github.com/void256/nifty-gui/commit/c8a6030e78225cb5dc7a4cc3aba22df686339b68 and issue #43 as well.
I've not tried your example but from what I understand this should work as expected in 1.4.x. There have been some more changes lately so can you try it in the latest Nifty too, which is 1.4.1?

ok , actualy I use JMonkey 3, maybe they are nt up to date with latest nifty version

The latest nightly build of jME should actually contain Nifty 1.4.1. Can you check the Nifty version?
There is a method on the Nifty instance that returns the version String: https://github.com/void256/nifty-gui/blob/1.4/nifty-core/src/main/java/de/lessvoid/nifty/Nifty.java#L239


text:
Linux - extension build : cannot find module './util'

Problem :

This looks like there is a missing dependency

How to reproduce

Try build the extension

Expected :

Extension build

npm run build inside /extensions/void works for me. Can you try reloading node_modules?

authors: andrewpareles jcommaret

repo: voideditor/void


text:
GUI memory free problem when shutdown

In Visual Studio, debug the application, just close the start page(project manager), Visual Studio will prompt an exception in ImGui::MemFree

Does this happen every time? I will look into it.

Yes, it can be reproduced both on my desktop and laptop. Thanks.

I will fix this on Monday. Thanks for the issue.

authors: qiaone volcoma

repo: volcoma/EtherealEngine


text:
How to add multiple criteria in .Where

I was wondering how to add multiple criteria in .Where() in following example
var od = OrderDetailRow.Fields;
data.Details = connection.List(q => q
.SelectTableFields()
.Select(od.ProductName)
.Select(od.LineTotal)
.Where(od.OrderID == this.OrderID));

try using single
& for (And)
| for (Or)
you may also chain another .Where(...)

var sqlOfi = new SqlQuery()
.Select("KeyValue")
.From("[MasterData].[TableName]")
.Where($"Id={Value1} AND Id2={Value2}");

Thankyou @dfaruque  and @xareas , it solved my isuue

authors: dfaruque vinaykulkarni89 xareas

repo: volkanceylan/Serenity


text:
set up google analytics

Set up google analytics using gtag. This will likely also require some sort of GDPR notice or privacy policy.

Going to close this for now, not enough value add to overcome the risks.

repo: vondenstein/portfolio


text:
Revision files

Add revision (content) hash to asset filenames so they can be served with "never expire" header. Then update references to these filenames.
Can use gulp-rev + gulp-rev-replace like done in voorhoede-ocelot and vigetlabs/gulp-starter.
Use gulp-rev-napkin to cleanup original files.

Many static sites are hosted on Github Pages. Those have cache headers which typically expire between 10 to 60 minutes. Our revisioned files could be cached forever. So combine this with a server which supports that. For example Github Pages via CloudFare CDN?

repo: voorhoede-labs/fastatic


text:
Update pyo3 to 0.17

Update pyo3 to 0.17
Bump version to 0.7.0

Codecov Report

Merging #20 (b435f63) into main (546b26d) will decrease coverage by 0.41%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
- Coverage   35.29%   34.88%   -0.42%
==========================================
  Files           1        1
  Lines         170      172       +2
==========================================
  Hits           60       60
- Misses        110      112       +2

Impacted Files
Coverage Δ

src/lib.rs
34.88% <0.00%> (-0.42%)
:arrow_down:

Thank you, this was an all-inclusive pull request :-) I've published it.

authors: codecov-commenter diddlum vorner


text:
Add dependabot

This PR adds dependabot config

Thank you

authors: oriontvv vorner


text:
Remove old metrics logic and introduce handler for the deprecated wor…

…kflowMetrics API, which uses prometheus to provide data that satisfies the existing use-case of the now-deprecated route.

This implementation doesn't support the Sankey diagram on the UI. Closing until this has been remedied.

repo: vorteil/direktiv


text:
Declare Puppet 5 compatability

Update metadata.json to declare Puppet 5 compatability.
Add Puppet 5.0 check in travis.yml (requires modulesync_config or .sync.yml update too)
exclude rspec test that fails with new rspec-puppet 2.6.0 (#225)

unfortunatly puppet_install_helper does not support Puppet 5 and contributing guidelines more or less state that it is deprecated (https://github.com/puppetlabs/beaker-puppet_install_helper/blob/master/CONTRIBUTING.md) - but does not mention what will be the replacement.

successfully ran tests  with el6, el7, fedora 24 and fedora 25 with patched spec_helper_acceptance.rb
example for f25:
diff --git a/spec/spec_helper_acceptance.rb b/spec/spec_helper_acceptance.rb
index 358370d..c6ce6ff 100644
--- a/spec/spec_helper_acceptance.rb
+++ b/spec/spec_helper_acceptance.rb
@@ -2,7 +2,11 @@ require 'beaker-rspec/spec_helper'
 require 'beaker-rspec/helpers/serverspec'
 require 'beaker/puppet_install_helper'

-run_puppet_install_helper unless ENV['BEAKER_provision'] == 'no'
+#run_puppet_install_helper unless ENV['BEAKER_provision'] == 'no'
+hosts.each do |host|
+  on(host, 'dnf install -q -y http://yum.puppet.com/puppet5/puppet5-release-fedora-25.noarch.rpm')
+  on(host, 'dnf install -q -y puppet-agent')
+end

repo: voxpupuli/puppet-selinux


text:
Fixed import for VerifyChallengeMessage + information

I did some testing and succeeded to send back the token, this is just a small bug I've found in your code. The classname is VerifyChallengeMessage, though the filename is VerifyChallenge. This is an error in the protos repo, I've opened an issue already (https://github.com/NicklasWallgren/pogoprotos-php/issues/10). But the import should be on the classname in order to work.
I managed to send it back using this logic:
$config = new Config();
// TODO: Set Auth-Info to Config

// Create the authentication manager
$manager = Factory::create($config);

// Initialize the pokemon go application
$application = new ApplicationKernel($manager);
$pogoApi = $application->getPokemonGoApi();
$requestHandler = $pogoApi->getRequestService()->requestHandler();

$verifyChallenge = new \NicklasW\PkmGoApi\Requests\VerifyChallengeRequest($token);

$response = $requestHandler->handle($verifyChallenge);

Now someone has to put this nicely into the library :laughing:.
Note that the response HTTP code is always 200, and the ResponseEnvelope StatusCode is OK, but if the token is rejected the returns field is empty (not a false bool), so you get this error:
Fatal error: Uncaught InvalidArgumentException: fp must be a string or file resource in vendor\nicklasw\pogoprotos-php\src\protocolbuffers.inc.php:37
Stack trace:
#0 vendor\nicklasw\pogoprotos-php\src\protocolbuffers.inc.php(54): checkArgument
(false, 'fp must be a st...')
#1 vendor\nicklasw\pogoprotos-php\src\POGOProtos\Networking\Responses\VerifyChal
lengeResponse.php(24): ProtobufIO::toStream(NULL, 9223372036854775807)
#2 src\Requests\VerifyChallengeRequest.php(71): POGOProtos\Networking\Responses\
VerifyChallengeResponse->read(NULL)

We'd have to find a way to deal with this aswell.
I hope these information help you somehow.
See also https://github.com/AeonLucid/POGOProtos/issues/240

Thanks for proofing and fixing the mistake ^^ Much appreciated. About to test your example and verify. ^^

authors: DrDelay voxx

repo: voxx/PokemonGoAPI-PHP


text:
2.16.0 build issue

I have built docker image for 2.16.0 from source code giving base_image argument as 2.15.0 and distribution_url as https://repository.apache.org/content/repositories/releases/org/apache/activemq/apache-artemis/2.16.0/apache-artemis-2.16.0-bin.zip
Command:
docker build --no-cache=true --build-arg ACTIVEMQ_ARTEMIS_VERSION=2.16.0 --build-arg BASE_IMAGE=vromero/activemq-artemis:2.15.0 --build-arg ACTIVEMQ_ARTEMIS_VERSION=2.16.0 --build-arg ACTIVEMQ_DISTRIBUTION_URL=https://repository.apache.org/content/repositories/releases/org/apache/activemq/apache-artemis/2.16.0/apache-artemis-2.16.0-bin.zip -t activemq-artemis:2.16.0 -f Dockerfile .
Is this the correct procedure to build the image for 2.16.0 ??
I noticed an issue in docker-entrypoint.sh when running the image built. There is an closing "fi" missing at Line#88. Please do the fix.

I don't provide support for 2.16.0 yet. I'm working on it.

I don't provide support for 2.16.0 yet. I'm working on it.

repo: vromero/activemq-artemis-docker


text:
Compatibility with Grafana version 8?

I'm trying to use this plugin with Grafana 8, but the data source type is not being listed (after approving unsigned plugins). Would it be due to incompatibility with this new version?

yes I m getting also the same error using grafana 8 Missing signature

authors: allamiro romansoft

repo: vsergeyev/loudml-grafana-app


text:
Conche

Conche - Swift build system and dependency manager. :large_orange_diamond:

After the release of Conche, Apple surprised us and release the Swift Package Manager (SPM) and therefore this project isn't applicable. I'd suggest you instead take a look at SPM and use that over Conche.

repo: vsouza/awesome-ios


text:
Suggestions: Recipes -> Widgets

Issue for page suggestions for Widgets section of page /recipes/

@ktquez
I would like to contribute to this project.
https://vue-a11y.com/jp/recipes/widgets/card.html
Please give me an image of creating a "Card" recipe.
I found a card recipe on Vuetify docs like this.
https://vuetifyjs.com/en/components/cards/#usage

@ktquez
I would like to contribute to this project.
https://vue-a11y.com/jp/recipes/widgets/card.html
Please give me an image of creating a "Card" recipe.
I found a card recipe on Vuetify docs like this.
https://vuetifyjs.com/en/components/cards/#usage

Awesome @kazuki-komori
Thank you for wanting to contribute.
Would you like to create this recipe?
You can create an issue claiming this recipe.
In the issue, we can discuss more the process, curation...

Awesome @kazuki-komori
Thank you for wanting to contribute.
Would you like to create this recipe?
You can create an issue claiming this recipe.
In the issue, we can discuss more the process, curation...

@ktquez
Thank you for your reply.
I would like to create this recipe.
When you created the issue, please assigned me. 👍

@ktquez
Thank you for your reply.
I would like to create this recipe.
When you created the issue, please assigned me. 👍

authors: kazuki-komori ktquez


text:
trackBy on multiple properties

I need search capability to work with multiple properties. Can I use 'trackBy'  for that? Or is there some other method?

Concatenating a string in trackBy could be a solution?

Coming back to this issue, since this could be a good improvement to the component.
Maybe allow users to set similar property as trackBy, like alias to be used as aliased.

Good example is search location component.
There was a spelling change from Turkey to Türkiye
I have a const that composes of few lodash utilties and creates an array for Multiselect.
export const EUROPE_COUNTRIES = [
  'Sweden',
  'Türkiye',
]

export const COUNTRY_CHOICES = intersectionBy(
  orderBy(
    EUROPE_COUNTRIES.map((c) => {
      if (c === 'Türkiye') {
        return {
          label: c,
          value: c,
          alias: ['Turkey'],
        }
      }
      return {
        label: c,
        value: c,
      }
    }),
    [(country) => country.value.toLowerCase()],
    ['desc']
  ),
  'label'
)

<Multiselect
  v-model="location"
  :options="COUNTRY_CHOICES"
  searchable
  placeholder="Select locations"
  trackAlias="alias"
/>

Is here any update please?

As of 2.6.3 trackBy can be an array @morrowcreative

Thank you very much :) @adamberecz

repo: vueform/multiselect


text:
[Rio de Janeiro/RJ] Senior Full Stack Developer @ Lemoney

Missão do Cargo
Nosso time de Desenvolvimento é o coração da empresa. Eles são os responsáveis pelo coding, manutenção e implementação de novas features para nossos principais produtos e projetos.
Solução de ponta a ponta: Front to Back, passando por testes automatizados e tentando sempre encontrar as melhores opções tecnológicas para solucionar os problemas.
Procuramos pessoas proativas, com muita vontade de aprender e assumir novos desafios em sua carreira.
Nossa Tech Stack
Trabalhamos atualmente com Ruby on Rails, JavaScript e Vue.JS, mas em alguns projetos utilizamos Node.JS também.
Nossa Sprint é semanal e utilizamos a metodologia SCRUM.
Utilizamos o Google Clouds como serviço de armazenamento.
Pré Requisitos

Experiência como Full Stack (+4 anos);
Sólido conhecimento em JavaScript e alguma de suas frameworks (Vue é um diferencial);
Desenvolver com testes automatizados;
Ser apaixonado por aprender novas tecnologias e explorar novas soluções;

Desejáveis

Experiência anterior trabalhando com CI (Continuous Integration);
Experiência com Google Clouds;
Conhecimentos em SEO;

Sobre Nós
Somos uma startup americana de Cash Back e Cupons liderada por um time Brasileiro. Temos quatro anos de estrada e estamos em um momento chave de expansão e crescimento. Além de lidar com um mercado que é referência no mundo, estamos expandindo nossa operação para outros locais, o que torna o desafio mais gostoso ainda! :)
Aqui na Lemoney, você poderá contribuir para o crescimento e escalabilidade da empresa em ritmo startup de ser. Agilidade está em nosso core.
Local
Nosso Escritório fica em um dos pontos mais atrativos do Rio de Janiero, próximo à Praia de Ipanema, em frente ao metrô da Nossa Senhora da Paz. Temos também, um co working space em Downtown Miami.
Para essa vaga consideramos apenas posições Presenciais.
Diferenciais

Horário Flexível com política de Home Office duas vezes na semana;
Ambiente compartilhado com muita possibilidade de troca e aprendizado;
Oportunidade de lidar diretamente com o produto, participar e contribuir nas decisões chaves da empresa e da área de desenvolvimento;
Nosso time é pequeno, mas é de ouro! Todos engajados e extremamente produtivos;
Você trabalhará diretamente com o mercado americano, onde a excelência é default;
Ambiente informal e dinâmico, com amplo espaço para criatividade e inovação;

Application
Se identificou com a oportunidade? Envie seu Currículo ou Linkedin para careers@lemoney.com

Caros da @lemoneyhiring, por favor, especifiquem se a contratação é CLT ou PJ para completarmos as tags da vaga.

Ola, Erick!
Desculpe, acabei de atualizar a vaga. É contratação PJ.
Obrigada,
Odara
On Thu, Dec 5, 2019 at 14:14 Erick Eduardo Petrucelli <
notifications@github.com> wrote:

Caros da @lemoneyhiring https://github.com/lemoneyhiring, por favor,
especifiquem se a contratação é CLT ou PJ para completarmos as tags da vaga.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vuejs-br/vagas/issues/101?email_source=notifications&email_token=AKXDQ37IIEAHTLJWZKBM7MLQXEZHHA5CNFSM4JV235Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGBN52Y#issuecomment-562224875,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKXDQ35OFXC6KQQ74ETD75DQXEZHHANCNFSM4JV235ZQ
.

--
https://www.lemoney.com/
Odara Menezes
Human Resources
+55 (21) 3502-2185
odara.menezes@lemoney.com
https://www.facebook.com/lemoneyway
https://www.instagram.com/lemoney_coupons
https://www.twitter.com/lemoneyway https://www.pinterest.com/lemoneyway

authors: ErickPetru lemoneyhiring

repo: vuejs-br/vagas


text:
can you update vue1.0's template to webpack2?

Our some vue1.0 projects running with webpack1, and i want use webpack2 to replace it to get better performance.

To be perfectly honest, I suspect that we won't find time to do this anytime soon, there's a lot of other stuff to do that has a higher impact. At least I won't have the time, personally - can't speak for the rest of the guys with certainty.
We are open to PRs though, so the community might help out :)

repo: vuejs-templates/webpack


text:
When defined as a WebComponent, useSlots() and $slots return an empty object

Vue version
3.3.4
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-xycchc?file=src%2FApp.vue
Steps to reproduce
Just run and see the rendered content of useSlots() and $slots props:

What is expected?
Expected WebComponent to act similarly as vue component when accessing useSlots() or $slots.
What is actually happening?
useSlots() and $slots return an empty object when using as WebComponent.
System Info
System:
    OS: Linux 5.10 Ubuntu 20.04 LTS (Focal Fossa)
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1265U
    Memory: 16.62 GB / 24.62 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 18.12.1 - /usr/local/bin/node
    npm: 8.19.2 - /usr/local/bin/npm
  npmPackages:
    vue: ^3.3.4 => 3.3.4

Any additional comments?
No response

Vue slots content comes in the form of functions that retrun vnodes.
But when you wrapp a vue component as a custom element, this component will not receive vue slots content.
Instead, the custom element uses native <slot> elements, and those inject actual HTML elements directly from the parent DOM. Vue doesn'T even see these elements, really. And I would not see it as a good idea to have $slots suddently return HTML elements instead of vnode factory functions when used in a custom element.
However I do see an opportunity to improve the docs about this. The docs team would surely be thankful for an issue in their repo over at vuejs/docs

@LinusBorg thanks for respond.
I understand that there might be some differences and limitations when wrapping Vuejs component into a WebComponent. Although IMO every framework should strive to minimize those and make DX as fluent as possible.
By only updating docs, the problem won't be solved. Still Vuejs devs would have to struggle to come up with a workaround for such cases.

I would not see it as a good idea to have $slots suddently return HTML elements instead of vnode factory functions when used in a custom element.

When $slots suddenly returning an empty object, that seems to be much worse idea, than returning at least a list of HTML Elements, wouldn't you agree?
Can you please consider implementing some workaround baked into Vuejs for better compatibility with WebComponents, and may be transforming this bug report into a feature request? 🙏

When $slots suddenly returning an empty object, that seems to be much worse idea, than returning at least a list of HTML Elements, wouldn't you agree?

I don't really agree. for one, the types would then need to reflect this, and developers would be forced to always take into account the possibilty of a slot suddenly conatining plain HTML elements instead of a vnode factory, even though they don't develop component to be used as web components.
If anything, a new API would be a better solution, or even just setting a template ref on a <slot /> (didn't try wether that already works right now with web component slots)

I was hoping ref on a <slot /> would work, but it doesn't, I have just checked.
Indeed a union return-types increases cognitive load and doesn't seem to be a good solution. And indeed apparently a new API is required. At the end of the day it still looks like a bug, and not like a feature or well reasoned limitation.
I ended up with this dirty workaround:
export function useSlot() {
    const instance = getCurrentInstance()
    const slot = ref<VNode[] | HTMLCollection | undefined>()
    if (instance) {
        onMounted(() => {
            const root = instance.root.vnode.el
            const isWebComponent = root?.parentNode instanceof ShadowRoot
            if (!isWebComponent) {
                const slots = useSlots()
                slot.value = slots.default && slots.default()
            } else if (root) {
                const host = root.parentNode.host as HTMLElement
                slot.value = host.children
            }
        })
    }
    return slot
}

If anyone has a better idea please reply in this issue.

authors: LinusBorg mav-rik

repo: vuejs/core


text:
feat(sfc-playground): upgrade the sfc-playground dependency @vue/repl

feat(sfc-playground): upgrade the sfc-playground dependency @vue/repl

The CI requires strict lockfile when bumping deps, so I did it in 8758da47


text:
fix(teleport): unrollBuffer unrolls asynchronous item synchronously during teleport

reference: https://github.com/nuxt-modules/icon/issues/37

see #9431


text:
Maximum call size stack exceed in Nuxt 3

Reproduction
https://stackblitz.com/edit/github-ckfaob?file=nuxt.config.ts
Steps to reproduce the bug
Install @pinia/nuxt 0.2.0 together with pinia 2.0.15.
Set ssr: false in nuxt.config.
Run app.
Expected behavior
No 500 so nuxt app is loaded and pinia can be used.
Actual behavior
The app cannot start because of 500: Maximum call size stack exceed in Nuxt 3. Hopefully the repro link where I just edited nuxt.config to turn off SSR will show you more than:
at createMock (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/unenv/runtime/mock/proxy.mjs?v=e62355c5:6:10)
at Object.get (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/unenv/runtime/mock/proxy.mjs?v=e62355c5:17:43)
at toRaw (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/.vite/deps/vue.js?v=2aaec172:1043:35)
at toRaw (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/.vite/deps/vue.js?v=2aaec172:1044:16)
at toRaw (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/.vite/deps/vue.js?v=2aaec172:1044:16)
at toRaw (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/.vite/deps/vue.js?v=2aaec172:1044:16)
at toRaw (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/.vite/deps/vue.js?v=2aaec172:1044:16)
at toRaw (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/.vite/deps/vue.js?v=2aaec172:1044:16)
at toRaw (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/.vite/deps/vue.js?v=2aaec172:1044:16)
at toRaw (https://github-ckfaob--3000.local.webcontainer.io/_nuxt/node_modules/.vite/deps/vue.js?v=2aaec172:1044:16)

Additional information
While SSG in Nuxt 3 is not fully supported yet the root cause might be within pinia plugin, https://github.com/vuejs/pinia/issues/1442 does not seem to be the reason because the message was present in both modes.
I'm a bit surprised I wasn't able to find this issue here but still expect it might be a duplicate.

"@pinia/nuxt": "^0.1.9",

use 0.1.9 fine..but update to 0.2.0 , "Maximum call size stack exceed"

@pi0 Do you have any idea of what could trigger a 500 when setting ssr: false? Also, why is there a 500 on the client side? 🤔

Thank you Eduardo for quick fix and release, it does work now as expected.

authors: leosin posva xollaborator

repo: vuejs/pinia


text:
docs: Update dynamic-matching.md

Is it necessary to add an explanation here? I just started learning vue and didn't understand this usage at first.

thanks! It's not necessary to add it as this is part of vue core docs

authors: freemedom posva

repo: vuejs/router


text:
New template: Webpack - Server-side rendering

Vuejs 2.0 has 1 nice feature is server-side rendering. But setup this feature runs correctly somehow is too pain for newbie.
So I think it's nice to add a new template support server-side rendering.

something like https://github.com/zeit/next.js for Vue.js would look sweet.

You can check out this WIP template if you'd like :
vue init molamil-com/vuejs-ssr-template <project-name>
cd <project-name>
npm install
npm run dev

@egoist Have you seen https://github.com/nuxt/nuxt.js ? It's been a while since your comment, but Nuxt is exactly what you are describing, and I like what I see! I would love if if there were something official, though. I always assumed vue-cli would expand to something more like Ember and Angular 2 where you can add a route from the command line, etc. But perhaps that is out of the scope of the Vue core.

@jpt It doesn't need to be official to be good 😉 . Nuxt is a great project, well maintained and actively being worked on. It'd we a waste to create an official fork of it!

A simple server-side rendering CLI template for Vue.js: https://github.com/xpepermint/vue-cli-template

Looks like Vue v2.2 will get even more SSR goodies and community is thinking about it. Also see this: https://www.youtube.com/watch?v=InOWBvseRYU&feature=youtu.be&t=5386

Hello is there any update about cli template for ssr, i really would like to have full supported webpack template wich would be managed by official vue js team. I think many peaple get stuck in searching for ssr templates. The temlates which exist usually do not have some feachers for example css bundeling or proper minification. And so on ... . Thank you

Hello everyone!
It's almost been a year after this issue was created. We got pretty ssr guide but still no template.
In this issue @LinusBorg mentioned there's work on it, but is it?
If no - I could start build template based on hn example.
@LinusBorg I'm not sure if you're close to vue-cli and its templates, but can you please coordinate future moves in this issue?

authors: egoist fahrenq goriunov imcvampire jpt kasperhelweg posva xpepermint zigomir

repo: vuejs/vue-cli


text:
Cannot import project via "import project" button

Version
3.0.0
Node and OS info
Node 10.6.0 / NPM 6.1.0 / macOS 10.13.6
Steps to reproduce
install vue cli
run command vue ui, get Error: Cannot find module 'core-js/modules/es7.object.entries'
fix this by doing npm i core-js -g
run command vue ui again, and it works.
Find project and click "import this folder"
What is expected?
Project to be imported to vue cli
What is actually happening?
Nothing

The "import this folder" button is active(green).
If I try to import an vue plugin(eg vuejs-datepicker), it works.
The project has not been generated by a previous vue-cli. Is this the issue? If so, how does one import a "rouge" project?

The cli ui can only import Javascript projects that contains a package.json file. Do you have a minimal reproduction of a project you can't import?

I had this problem - turned out to be syntax errors in the package.json file.  Would be nice to have an error message....
BUT - after I fixed the syntax errors, the import function ran "forever".

I had this problem.  Turned out to be syntax errors in the package.json file.  Would be nice to have an error message....

Closing for inativity.

authors: Akryum BlitZz96 LinusBorg mhldtna


text:
Add ts declaration for @vue/cli-test-utils, Plugin API, Generator API

What problem does this feature solve?
I code by vscode, and these is no code intelliSense when coding vue-cli-plugin and plugin unit test.
If ts declarations are provided, it will be helpful. I'm maintaing some vue cli plugins for some times, it's just a pain point for me.
What does the proposed API look like?
for @vue/cli-test-utils,  add declaration to cli-test-utils folder, like createTestProject.d.ts, vscode can finish code completion even in .js file.
for plugin, generator api, maybe like this?
import {GeneratorAPI} from '@vue/cli'
import {PluginAPI} from '@vue/cli-service'

or

import {GeneratorAPI, PluginAPI} from '@vue/cli-types'

export =  function (api: GeneratorAPI, options: any) {

}

Hi, I am interested in this issue and I had generated GeneratorAPI declaration file and PluginAPI declaration file like this:
/**
 * Note: if a plugin-registered command needs to run in a specific default mode,
 * the plugin needs to expose it via `module.exports.defaultModes` in the form
 * of { [commandName]: mode }. This is because the command mode needs to be
 * known and applied before loading user options / applying plugins.
 */
declare interface PluginAPI {
  /**
   *
   * @param id
   * @param service
   */
  new (id: string, service: any);

  /**
   *
   * @param range
   */
  assertVersion(range: string): void;

  /**
   * Current working directory.
   * @return
   */
  getCwd(): any;

  /**
   * Resolve path for a project.
   *
   * @param {string} _path - Relative path from project root
   * @return {string} The resolved absolute path.
   */
  resolve(_path: string): string;

  /**
   * Check if the project has a given plugin.
   *
   * @param {string} id - Plugin id, can omit the (@vue/|vue-|@scope/vue)-cli-plugin- prefix
   * @return {boolean}
   */
  hasPlugin(id: string): boolean;

  /**
   * Register a command that will become available as `vue-cli-service [name]`.
   *
   * @param {string} name
   * @param {object} [opts]
   *   {
   *     description: string,
   *     usage: string,
   *     options: { [string]: string }
   *   }
   * @param {function} fn
   *   (args: { [string]: string }, rawArgs: string[]) => ?Promise
   */
  registerCommand(name: string, opts?: any, fn: any): void;

  /**
   * Register a function that will receive a chainable webpack config
   * the function is lazy and won't be called until `resolveWebpackConfig` is
   * called
   *
   * @param {function} fn
   */
  chainWebpack(fn: any): void;

  /**
   * Register
   * - a webpack configuration object that will be merged into the config
   * OR
   * - a function that will receive the raw webpack config.
   *   the function can either mutate the config directly or return an object
   *   that will be merged into the config.
   *
   * @param {object | function} fn
   */
  configureWebpack(fn: any): void;

  /**
   * Register a dev serve config function. It will receive the express `app`
   * instance of the dev server.
   *
   * @param {function} fn
   */
  configureDevServer(fn: any): void;

  /**
   * Resolve the final raw webpack config, that will be passed to webpack.
   *
   * @param {ChainableWebpackConfig} [chainableConfig]
   * @return {object} Raw webpack config.
   */
  resolveWebpackConfig(chainableConfig?: any): any;

  /**
   * Resolve an intermediate chainable webpack config instance, which can be
   * further tweaked before generating the final raw webpack config.
   * You can call this multiple times to generate different branches of the
   * base webpack config.
   * See https://github.com/mozilla-neutrino/webpack-chain
   *
   * @return {ChainableWebpackConfig}
   */
  resolveChainableWebpackConfig(): any;

  /**
   * Generate a cache identifier from a number of variables
   * @param id
   * @param partialIdentifier
   * @param configFiles
   * @return
   */
  genCacheConfig(id: any, partialIdentifier: any, configFiles: any): any;
}

But 'add declaration for @vue/cli-test-utils, like createTestProject.d.ts' makes me confused, because there is only a function in createTestProject.js.
We just need to add declaration for this function in the declaration file, right？
If so, I will work on it.

authors: fangbinwei shadowings-zy


text:
lock inquirer dependency, fixes #4177

This should revert the upstream bug identified here: https://github.com/SBoudrias/Inquirer.js/issues/811
It should fix https://github.com/vuejs/vue-cli/issues/4177

This is awesome. Please merge!

Closed since this was fixed upstream.

authors: fohletex slhck


text:
Vue is in prduction mode

this disables Vue developer tools extension work.😞😞
and because the app is not  for production it will be beautiful to let Vue in the Development mode.
thanks guys of Vue & Vue developer extension developers👍👍

you can add Vue.config.devtools = true in app.js
or use it something like
if (process.env.NODE_ENV !== 'SOME_ENV') {
    Vue.config.devtools = true
}

authors: john-ko khaled-nuur


text:
The directive is overwritten by the varriable which has the same name as the directive when use composition API

Version
3.0.5
Reproduction link
https://github.com/Ryan2128/test
Steps to reproduce
Just run it.
What is expected?
Behavior as same as option API
What is actually happening?
After compile, the directive and the varriable both are properties of $setup

It has the same reason as https://github.com/vuejs/vue-next/issues/3270

Same workaround as https://github.com/vuejs/vue-next/issues/3270#issuecomment-782591109

Same workaround as #3270 (comment)

Yes, just change one of their name.
Thanks.

repo: vuejs/vue-next


text:
feat(runtime): support delay initializing props (fix #2325)

54ed759 ignored that :value also can cause #2325 , which is due to the order when initializing an element's attributes.
I believe similar problems may exist on other platforms, so I think it might be better to add delayInitProp to runtime-core.

runtime-core
provide a render option called delayInitProp, which receives el and key, returns whether delay or the priority.
benchmark: https://jsben.ch/wP8Q4 loop vs bench
delayInitProp?(el: HostElement, key: string): number | boolean

return value

true or number greater than 0 means put this prop at the end of the delayed queue
false or 0 means no need to delay
number less than 0 means put this prop at the beginning of the delayed queue (the need for delay is weaker)

runtime-dom
delay initializing value

fix #2325

https://github.com/vuejs/vue-next/commit/54ed7592e416fc411196e9b767aebcc4f2ca20d8 ignored that :value also can cause #2325 , which is due to the order when initializing an element's attributes.
I believe similar problems may exist on other platforms, so I think it might be better to add delayInitProp to runtime-core.

Isn't this a bit overkill though? Maybe looking through the vnode attrs to check if the value needs to be set one tick after instead of using mounted like in https://github.com/vuejs/vue-next/commit/54ed7592e416fc411196e9b767aebcc4f2ca20d8 works

In fact, I'm not sure if this change is appropriate.

Maybe looking through the vnode attrs to check if the value needs to be set one tick after instead of using mounted like in 54ed759 works

I've considered a similar approach, but when it comes to async prop initializing, it's hard to guarantee that there's no sequential conflict under special conditions.
Also I'm confused about where to set attr on vnode for such special delay requirements. And after all we need to judge such special conditions in the runtime-core.
I've also considered a less general solution with no runtime cost, that is, moving :value to the end when parsing the template 😂

I meant reading from vnode.props the possible attributes like type, min, max and range, and set them on the element before setting the value. For example, doing a rough Object.assign(el, vnode.props) before el.value = value solves the issue

I've also considered a less general solution with no runtime cost, that is, moving :value to the end when parsing the template 😂

Maybe that's the best solution but I imagine it would still be a problem in JSX and manual render functions

gotcha.
but I wonder how it works for :value. The logic of patch props is in runtime-core, but set props such as min, max  before value is a unique logic of DOM.

@posva https://jsben.ch/wP8Q4
it wouldn't be have a significant impact on performance according to this benchmark. after all, this change only affects how to initialize props.

I was only talking about setting min, max and similar attributes on the vModel directive code (which is dom specific) before setting the value. All directly in created and removing the code of mounted
I don't really understand what you want to say with the jsbench 😅

well there may be some misunderstanding. plz allow me to explain
this pr is mainly to solve the problem of :value, not vModel.

https://github.com/vuejs/vue-next/commit/54ed7592e416fc411196e9b767aebcc4f2ca20d8 ignored that :value also can cause #2325 , which is due to the order when initializing an element's attributes.

so this pr provides a way to delay initializing certain props (such as value in DOM). then I found that it would be much easier to solve vModel problem if directly set value as a prop instead of like what you suggest, so I did so.
sorry to puzzle you.

@unbyte this needs to be rebased now.

@HcySunYang
I just rebase on master branch and all tests are passed 😂
Since I haven't paid attention to vue-next for a long time, I just temporarily checked the files involved in this PR, which should not damage the current operation mechanism. If there is any, please let me know and I will fix it as soon as possible

@unbyte Thanks

See ff0c8103 - while the changes proposed in this PR are technically correct, they introduce a bit too much overhead / complexity for a very finite special case. I decided to just special case value directly in runtime-core.

authors: HcySunYang posva unbyte yyx990803


text:
fix: correctly pass component definition as slot mounting option

We were not passing the entire component to slots, just the render function, so things like the lifecycle hooks were not executed.
closes #727

This looks good to me. Thank you 🙌🏼

repo: vuejs/vue-test-utils-next


text:
vue/vue-server-renderer  vue-ssr-client-manifest.json  The initial property is an empty array times the bug

What problem does this feature solve?

When the initial attribute of the vUE - SSr-client-manifest.json file is an empty array

Start the Node service and access the IP in the browser

Build.dev. js file in the vue-server-renderer plugin reported a bug in line 9074sha

TypeError: Cannot read property 'file' of undefined
at /Users/binbinwang/workspace/x-fe/vue-ssr/node_modules/vue-server-renderer/build.dev.js:9074:24
What does the proposed API look like?
vue-ssr-client-manifest.json
{
  "publicPath": "/dist/",
  "all": [
    "app.0178268b84efde12045b.js"
  ],
  "initial": [],
  "async": [
    "app.0178268b84efde12045b.js"
  ],
  "modules": {
    "239adfd4": [
      0
    ],
    "6fbc4fdc": [
      0
    ]
  }
}

I solved it
return needed.map(function (ref) {
      if(!ref) return   // Add this line
      var file = ref.file;

      return ("<script src=\""   (this$1.publicPath)   file   "\" defer></script>")
    }).join('')

fixed in https://github.com/vuejs/vue/pull/11609

authors: posva wbbhacker

repo: vuejs/vue


text:
Component in keep alive receives activated event when being deactivated

Version
3.2.29
Reproduction link
code : github.com
demo : netlify.com
Steps to reproduce

Click https://vue-3-keep-alive-lifecycle.netlify.app/
Open devtools, console tab.
Click About link.
Clear console.
Click Home link.

What is expected?
Since it's being deactivated NestedAbout component should not receive the activated lifecycle event
What is actually happening?
NestedAbout component is receiving the activated lifecycle event

We can also notice that NestedHome is mounted twice, as reported here:
https://github.com/vuejs/router/issues/626#issuecomment-1004182965

oups, vue3 related, issue generator redirect to vue2 only.
Issue moved here : https://github.com/vuejs/core/issues/5323


text:
props.sync will be invalid when do this

<parent>
  <child :prop.sync="mProp"></child>
</parent>

in parent data,i don't defined mProp
if i run "this.mProp='xxxx'" in parent before run "this.prop='xxxx'" in child,the sync will be invalid
why?
懂中文的还是用中文回我吧==

Hi!
Please make sure to ask the question on the forums or the gitter chat. We keep questions out of issues :smile:
As for the question, you need to define it on parent

authors: aweiu posva