text:
[Usage]: In the VLLM background log, only the question asking log can be viewed, but the answer log generated by the large model cannot be viewed. How to display the answer generated by the large model in the log?

Your current environment
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: Ubuntu 22.04.3 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.29.0
Libc version: glibc-2.35

Python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-3.10.0-1160.el7.x86_64-x86_64-with-glibc2.35
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-40GB
GPU 1: NVIDIA A100-SXM4-40GB
GPU 2: NVIDIA A100-SXM4-40GB
GPU 3: NVIDIA A100-SXM4-40GB
GPU 4: NVIDIA A100-SXM4-40GB
GPU 5: NVIDIA A100-SXM4-40GB
GPU 6: NVIDIA A100-SXM4-40GB
GPU 7: NVIDIA A100-SXM4-40GB

Nvidia driver version: 535.86.10
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:                   43 bits physical, 48 bits virtual
Byte Order:                      Little Endian
CPU(s):                          192
On-line CPU(s) list:             0-191
Vendor ID:                       AuthenticAMD
Model name:                      AMD EPYC 7642 48-Core Processor
CPU family:                      23
Model:                           49
Thread(s) per core:              2
Core(s) per socket:              48
Socket(s):                       2
Stepping:                        0
Frequency boost:                 enabled
CPU max MHz:                     2300.0000
CPU min MHz:                     1500.0000
BogoMIPS:                        4599.87
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip overflow_recov succor smca
Virtualization:                  AMD-V
L1d cache:                       3 MiB (96 instances)
L1i cache:                       3 MiB (96 instances)
L2 cache:                        48 MiB (96 instances)
L3 cache:                        512 MiB (32 instances)
NUMA node(s):                    2
NUMA node0 CPU(s):               0-47,96-143
NUMA node1 CPU(s):               48-95,144-191
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; Load fences, usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full retpoline, IBPB
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.18.1
[pip3] torch==2.1.2
[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    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      NV12    NV12    NV12    NV12    NV12    NV12    NV12    0-47,96-143     0               N/A
GPU1    NV12     X      NV12    NV12    NV12    NV12    NV12    NV12    0-47,96-143     0               N/A
GPU2    NV12    NV12     X      NV12    NV12    NV12    NV12    NV12    0-47,96-143     0               N/A
GPU3    NV12    NV12    NV12     X      NV12    NV12    NV12    NV12    0-47,96-143     0               N/A
GPU4    NV12    NV12    NV12    NV12     X      NV12    NV12    NV12    48-95,144-191   1               N/A
GPU5    NV12    NV12    NV12    NV12    NV12     X      NV12    NV12    48-95,144-191   1               N/A
GPU6    NV12    NV12    NV12    NV12    NV12    NV12     X      NV12    48-95,144-191   1               N/A
GPU7    NV12    NV12    NV12    NV12    NV12    NV12    NV12     X      48-95,144-191   1               N/A

Legend:

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

What's the problem I'm having?
I run QWEN1.5-72B-Chat model in VLLM. In the VLLM background log, only the question asking log can be viewed, but the answer log generated by the large model cannot be viewed. How to display the answer generated by the large model in the log?

May I ask if you have solved this problem? I'm also confused about this, I didn't find any information about it, and it's very inconvenient when debugging the error report.

repo: vllm-project/vllm


text:
[RFC]: Add support for IBM Spyre accelerator

Motivation.
IBM has recently announced its Spyre AI accelerator at Hot Chips 2024. This accelerator has been designed, in collaboration with IBM Research,  to scale-up enterprise AI workloads running on IBM's mainframe systems (IBM Z), as well as on IBM's Power platform. Since IBM is building our inference stack on top of vLLM, we would like to enable support for IBM Spyre within the vLLM framework.
Spyre has been designed to fit seamlessly into the PyTorch ecosystem via torch.compile. Specifically, IBM Research has developed a new backend for torch.compile that will compile torch FX graphs for execution on the Spyre hardware. In this sense, we envision that Spyre support in vLLM can work in a similar way to how the TPU support is working today (e.g., see here).
Today, there are two key limitations that affect this integration and need to be worked around. Specifically:

Spyre only supports execution of the modeling code from IBM's open-source Foundation Model Stack (fms). This is only a temporary limitation, the end-goal is that, via torch.compile, we can also run the native vLLM modeling code on Spyre. We hope that recent efforts to make vLLM models torch compilable will significantly accelerate this effort.
Spyre does not currently support paged attention or continuous batching. This means that, after prefilling a batch, we need to keep decoding until all of the sequences within that batch are finished. Our team is working to remove this limitation in the near future.

Proposed Change.
In this RFC, we propose the following sequence of PRs to enable IBM Spyre support in vLLM:

[ ] P1: Add support for single Spyre card via new SpyreExecutor class
[ ] P2: Changes to scheduling algorithm to disable continuous batching.
[ ] P3: Enable TP execution across multiple Spyre cards via MultiprocessingSpyreExecutor class.
[ ] P4: Enable paged attention and continuous batching for Spyre.
[ ] P5: Enable vLLM modeling code to run on Spyre.

While much of the work here (P1, P2, P3) has already been completed in an private fork, we plan to upstream the changes as a sequence of smaller PRs, to make the changes easier to review. Below we will discuss the planned changes from each PR step.
P1: Add support for single Spyre card via new SpyreExecutor class
We will introduce a set of classes, inheriting from the core vLLM classes, that will enable execution on a single Spyre device. Architecturally, this will look very similar to the equivalent classes that were introduced for running on AWS Inferentia (e.g., NeuronExecutor, NeuronWorker, NeuronModelRunner, NeuronCausalLM). In a similar way to how the NeuronModelRunner use the modeling code from the transformers_neuronx package, these new classes will execute the modeling code from IBM's fms package.
In the diagram below, we compare the proposed Spyre classes, with the corresponding classes that already exist for the AWS Inferentia support:

Since Spyre works via torch.compile, to ensure that compilation does not occur on the critical path (e.g., serving user requests), we need to ensure that all compilation gets triggered at init time. This PR will also introduce a routine for warming up the inference server when using the Spyre, triggering compilation of all required shapes (e.g., prompt length, number of output tokens, batch size). We will write code to ensure that batches get padded to one of the compiled shapes before execution. This behaviour is akin to what happens today in vLLM for CUDA graphs, and presumably something like this warmup will also be needed once vLLM starts using torch.compile more extensively. This could be one area to explore commonality with others parts of the codebase.
Testing: While testing on the real hardware can only be performed internally for now, we can test the vast majority of the integration on the CPU by either (a) running in eager mode or (b) by using torch compile with the inductor backend. Thus, in this PR we will also add a set of unit and integration tests to verify that everything behaves as expected. The tests will focus on the offline mode, since changes to the scheduling algorithm are needed to support online mode (see P2). We will also add a Dockerfile.spyre containing all necessary dependencies (e.g., FMS) in which the tests can be executed. Whether we could have these tests running as part of vLLM's CI/CD is something we would like to discuss.
P2: Changes to scheduling algorithm to disable continuous batching.
We need to introduce a few changes to the scheduling algorithm to workaround the lack of continuous batching support. Specifically:

We must not schedule another prefill until all decodes in the running batch are finished (one line change).
We need to introduce some logic to decide how to batch together request based on the prompt lengths and max output tokens, in order to best fit the shapes that have been compiled on Spyre during the warmup phase.

These changes must be conditional and not affect the behaviour of the scheduler on existing supported devices. They could either be applied within the scheduler itself (e.g., by checking is_spyre()) or we could try to "plug in" an alternate scheduler design? This is one of the design choices we would like some feedback on.
Testing: As part of this PR, we will also introduce tests to cover the integration with the MQLLMEngine and online operation.
P3:  Enable TP execution across multiple Spyre cards via MultiprocessingSpyreExecutor class.
We have found that the MultiprocessingGPUExecutor can be easily adapted into a MultiprocessingSpyreExecutor to enable TP execution across multiple Spyre devices in parallel. However, to reduce code duplication we propose refactoring the common code between MultiprocessingGPUExecutor and MultiprocessingSpyreExecutor into a common parent class MultiprocessingExecutor. By inheriting from MultiprocessingExecutor and a corresponding mixin class (e.g., GPUExecutor or SpyreExecutor) it should be possible to achieve the desired behaviour with very little device-specific code. Note that something along these lines already exists for the MultiprocessingXPUExecutor (e.g., see here), but the design proposed below would give more flexibility for device-specific specialization, and would also easily allow us to create multi-processing executors for all support devices if we want.
The architecture would look something like this:

Testing: We will add tests to verify that the MultiprocessingSpyreExecutor behaves as expected for tensor parallel execution when running using eager or usinginductor backend on CPU. Internally, we will run these tests against the real hardware.
P4: Enable paged attention and continuous batching for Spyre.
TBD
P5: Enable vLLM modeling code to run on Spyre.
TBD
Feedback Period.
2 weeks
CC List.
@njhill @simon-mo @youkaichao @zhuohan123 @comaniac @WoosukKwon @Yard1
Please cc anyone else as you see fit!
Any Other Things.
No response
Before submitting a new issue...

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

Hi @tdoublep, thanks for the thorough writeup! I had some torch.compile related questions

Specifically, IBM Research has developed a new backend for torch.compile that will compile torch FX graphs for execution on the Spyre hardware

Is this a torch dynamo backend? Or does it integrate via Inductor?

This PR will also introduce a routine for warming up the inference server when using the Spyre, triggering compilation of all required shapes (e.g., prompt length, number of output tokens, batch size). We will write code to ensure that batches get padded to one of the compiled shapes before execution. This behaviour is akin to what happens today in vLLM for CUDA graphs, and presumably something like this warmup will also be needed once vLLM starts using torch.compile more extensively.

Agreed, something like this would be useful for GPUs. We want to be able to write custom inductor passes where we only apply certain optimizations depending on the number of tokens we're working with. (cc @bnellnm who is working on an inductor pass like that)
BTW: It sounds like the Spyre might require all shapes to be static, is that true?

Thanks for reading @tlrmchlsmth

Is this a torch dynamo backend? Or does it integrate via Inductor?

Thanks for reading @tlrmchlsmth

Is this a torch dynamo backend? Or does it integrate via Inductor?

The former, it integrates at the level of FX graphs.

BTW: It sounds like the Spyre might require all shapes to be static, is that true?

Right now each compile has a static prompt length and batch size, but the number of output tokens is dynamic to an extent (we still need to define some maximum). We are able to compile multiple graphs to support different cases though, and we have some logic to pad to the nearest reasonable shape (again, sort of like how CUDA graphs works today iirc).

Update from our side: we have now open-sourced the code for Spyre support on IBM's fork of vLLM:
https://github.com/IBM/vllm

Nice, looks like all the needed changes are contained in this PR https://github.com/IBM/vllm/pull/56?

@tlrmchlsmth Yes, those are the changes compared with a commit from last month. We will continue developing on the open repo from here onwards, and will be pulling in changes from upstream frequently.

source: gharchive/issue

authors: tdoublep tlrmchlsmth

license_type: permissive

license_source: github-api


text:
[Frontend] Refactor prompt parsing

I have refactored the prompt parsing logic by moving it to the base class OpenAIServing, so that it can be shared between Chat Completions API and legacy Completions API. The _validate_prompt_and_tokenize method has also been decomposed so that prompt and prompt_ids are processed separately.
Related Contributions
This PR is part of #3978.

Seems that #4032 alone fixed the flaky tests. Perhaps we can merge this first then?

Seems that #4032 fixed the LoRA bugs, however entrypoints-test is still failing.

Update: I found that it is due to a bug in my refactored parsing, my bad. I have fixed it just now.

@njhill The tests now pass. To move on with #3978, perhaps we can merge this PR first?

Update: I found that it is due to a bug in my refactored parsing, my bad. I have fixed it just now.

I'm updating test_batch_completions to better catch this error. Previously, the error only occurred in test_echo_logprob_completion which misled me from the real cause.

@DarkLight1337 sorry for the hold-up, I will hopefully get to this tomorrow including looking at reconciling with #3512.

No worries. Do note that I have ported some of the changes (mostly related to type annotations) to #4355, so perhaps we can wait until that has been merged first.

Alright, #4355 has been merged so I have updated this branch accordingly.

Heads-up: I have copied OpenAIServing._parse_prompt_input_or_inputs to vllm.inputs.parse_and_batch_prompt in #4328. If that other PR is merged first, I'll make the change in this one accordingly.

@DarkLight1337 sorry, going to look at this next, I did a review of #4328 at least :)

I have merged #4328 into this PR in advance, so you might see additional diffs. These diffs should disappear once #4328 is merged into main.

@njhill any update?

@njhill I have updated this PR based on your #6227. PTAL.

Looks like this line also needs to be removed from the tokenization test.

Looks like this line also needs to be removed from the tokenization test.

Actually, let me add add_special_tokens to Completions API as well to make things consistent. It's a vLLM feature originally introduced by #5278.

My only concern is whether some folks might make use of the logging in the engine with different front ends.

I've moved out the logging to a separate class vllm.entrypoints.logger.RequestLogger, so it should be easy for them to manually log the requests if need be.

I have finished addressing your comments.

source: gharchive/pull-request


text:
[CI/Build] install setuptools-scm when building the wheel

publish.yml currently fails, see https://github.com/vllm-project/vllm/pull/8771#issuecomment-2376202075 for context

@youkaichao

how about just use pip install -r requirements-build.txt ?

@youkaichao good call. Moved to https://github.com/vllm-project/vllm/pull/8900

authors: dtrifiro youkaichao


text:
Check failure/Cant compile the converter-example

I followed the instructions for installing asn1c but the check fails with the following error in the test-suite.log
@@ -1,3 +1,5 @@
+FATAL: Inappropriate value {3 2 1} for type raf
+FATAL: Inappropriate value {3 2 2} for type rcf

 /*** <<< INCLUDES [Attribute] >>> ***/

Checking ../../tests/tests-asn1c-compiler/99-class-sample-OK.asn1 against ../../tests/tests-asn1c-compiler/99-class-sample-OK.asn1.-EFprint-class-matrix
Error while processing ../../tests/tests-asn1c-compiler/98-attribute-class-OK.asn1.-P (from ../../tests/tests-asn1c-compiler/98-attribute-class-OK.asn1)
FAIL check-parsing.sh (exit status: 1)

Im using an UBUNTU 20.04 with gcc 9.4.
I can still manage to use the library as I used it to compile NGAP ASN1 specification pretty normally. For RRC(16.4.0 from OSS Nokalva playground website) however I cant crate the converter-example program as I get the  following error when running make -f converter-example.mk:
cc  -DASN_PDU_COLLECTION -I. -o BCCH-DL-SCH-Message.o -c BCCH-DL-SCH-Message.c
In file included from RadioResourceConfigCommonSIB.h:15,
                 from SystemInformationBlockType2.h:15,
                 from SystemInformation-r8-IEs.h:16,
                 from SystemInformation.h:15,
                 from BCCH-DL-SCH-MessageType.h:15,
                 from BCCH-DL-SCH-Message.h:15,
                 from BCCH-DL-SCH-Message.c:8:
RACH-ConfigCommon.h:145:9: error: redefinition of ‘struct RACH_ConfigCommon__Member’
  145 |  struct RACH_ConfigCommon__Member {
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~
RACH-ConfigCommon.h:138:9: note: originally defined here
  138 |  struct RACH_ConfigCommon__Member {
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~
RACH-ConfigCommon.h:150:5: error: duplicate member ‘Member’
  150 |  } *Member;
      |     ^~~~~~
In file included from SystemInformationBlockType2.h:15,
                 from SystemInformation-r8-IEs.h:16,
                 from SystemInformation.h:15,
                 from BCCH-DL-SCH-MessageType.h:15,
                 from BCCH-DL-SCH-Message.h:15,
                 from BCCH-DL-SCH-Message.c:8:
RadioResourceConfigCommonSIB.h:90:9: error: redefinition of ‘struct RadioResourceConfigCommonSIB__Member’
   90 |  struct RadioResourceConfigCommonSIB__Member {
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RadioResourceConfigCommonSIB.h:84:9: note: originally defined here
   84 |  struct RadioResourceConfigCommonSIB__Member {
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RadioResourceConfigCommonSIB.h:96:9: error: redefinition of ‘struct RadioResourceConfigCommonSIB__Member’
   96 |  struct RadioResourceConfigCommonSIB__Member {
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Same problem here, followed install instructions on WSL ubuntu 20.04 with GCC 9.4.0.
`cat tests/tests-asn1c-compiler/test-suite.log | grep FATAL
+FATAL: Unknown type "REF-ID2" referenced by "REF-ID" at line 15 in ../../tests/tests-asn1c-compiler/102-class-ref-SE.asn1
+FATAL: Unknown type "REF-ID" referenced by "REF-ID2" at line 17 in ../../tests/tests-asn1c-compiler/102-class-ref-SE.asn1
+FATAL: Class field REF-ID.&id lookup at line 18 in something that is not a class: REF-ID2 at line 17 in ../../tests/tests-asn1c-compiler/102-class-ref-SE.asn1
+FATAL: Unknown type "REF-ID.&id" referenced by "field" at line 18 in ../../tests/tests-asn1c-compiler/102-class-ref-SE.asn1
+FATAL: Unknown type "REF-ID.&Type" referenced by "params" at line 20 in ../../tests/tests-asn1c-compiler/102-class-ref-SE.asn1
+FATAL: EXPORTS section of module ModuleTestConstraint2 in ../../tests/tests-asn1c-compiler/16-constraint-OK.asn1 does not mention ten at line 29 in ../../tests/tests-asn1c-compiler/16-constraint-OK.asn1
+FATAL: EXPORTS section of module ModuleTestConstraint2 in ../../tests/tests-asn1c-compiler/16-constraint-OK.asn1 does not mention ten at line 29 in ../../tests/tests-asn1c-compiler/16-constraint-OK.asn1
+FATAL: Name "e_a" is generated by ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:34 and ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:40
+FATAL: Name "enum a" is generated by ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:34 and ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:40
+FATAL: Name "a_PR" is generated by ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:34 and ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:40
+FATAL: Name "enum a_PR" is generated by ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:34 and ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:40
+FATAL: Name "struct a" is generated by ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:34 and ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:40
+FATAL: Name "a" is generated by ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:34 and ModuleTestSameNames.a at line ../../tests/tests-asn1c-compiler/72-same-names-OK.asn1:40
+FATAL: ... 13 more name clashes not shown
+FATAL: Use "-fcompound-names" flag to asn1c to resolve name clashes
+FATAL: Inappropriate value {3 2 1} for type raf
+FATAL: Inappropriate value {3 2 2} for type rcf`

I am going to use the latest release from https://github.com/vlm/asn1c/releases until the issue is resolved.
P.S make check passed all the tests.

I also find this in WSL
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy

@swordXwind I recommend using this fork as it is maintained regularly.

authors: kbaccar swordXwind turabek-cc


text:
When panel is enabled, only /index.html can be directly visited

Describe the bug
When the panel is enabled --enable-panel, the logic that handles the panel endpoints will only serve /index.html and any assets that are discovered under client/dist when building.
The logic that handles this is at: https://github.com/vmware-labs/wasm-workers-server/blob/549387b83be50b1b2ec7e04782c629a2c2e38965/crates/panel/src/handlers/panel.rs#L18-L29
There are other virtual paths such as /_panel/workers that are not covered by any of this cases.
Ideally, to avoid duplicating routing in multiple places, this logic should:

If path is empty, default to index.html, as per the current logic.
If an asset exists, serve it, as per the current logic.
Otherwise, serve a static page, that will perform an AJAX request to the current path and will forward the response to the client.

This way, we keep the current Single Page Application (SPA) approach, while making arbitrary paths directly visitable (e.g. reload endpoint, write path in location bar and hit enter...)
Reproduction steps
Run wws with --enable-panel. Visit /_panel/workers. The server will return a 404  HTTP status code.
Expected behavior
Visiting /_panel/workers directly should be equivalent to visiting / and navigating through the UI to the list of workers.
Additional context
No response

I reproduced the problem, except I don't know what it is now.
But it looks like the odds are that the front-end file isn't receiving the route forwarding.
Because I tried to change the path to /_panel/workers  and I can't access it either.
It only works if you visit /panel first, go to the UI and then click on the sidebar.

I tried to fix this bug and was able to access /_panel/workers through my browser.
I mainly utilized the fact that the pages I couldn't find were using the front end to forward requests.
I'm not sure if this is the desired result, can you help me out?
/// Find the static assets of the administration panel
#[actix_web::get("/_panel{_:.*}")]
pub async fn handle_static_panel(path: web::Path<String>) -> impl Responder {
    let path = if path.is_empty() {
        "index.html"
    } else {
        path.as_str().strip_prefix('/').unwrap()
    };

    let (content_type, content_data) = Asset::get(path)
        .map(|content| {
            (
                from_path(path).first_or_octet_stream().to_string(),
                content.data.into_owned(),
            )
        })
        .unwrap_or_else(|| {
            let default_content = Asset::get("index.html").unwrap();
            (
                "text/html; charset=utf-8".to_string(),
                default_content.data.into_owned(),
            )
        });

    HttpResponse::Ok()
        .content_type(content_type)
        .body(content_data)
}

Hello @dierbei,
Thank you for taking the issue and submit the PR to fix it! 👏

I tried to fix this bug and was able to access /_panel/workers through my browser.
I mainly utilized the fact that the pages I couldn't find were using the front end to forward requests.
I'm not sure if this is the desired result, can you help me out?

Yes, this is the expected result. The administration panel is a Single Page Application (SPA), so the routing happens in the browser. If you access the panel on / and then navigate to /workers through a link, it works. However, if you reload the site, it will return a 404 error as the admin panel dist package doesn't include any workers.html file.
The solution you proposed fix this error by returning the index.html file when there's no file in the admin panel dist folder that matches it.

But it looks like the odds are that the front-end file isn't receiving the route forwarding.
Because I tried to change the path to /_panel/workers  and I can't access it either.

This is the reason why you were getting these errors. The server didn't find any workers.html file.
Thank you!!

authors: Angelmmiguel dierbei ereslibre

repo: vmware-labs/wasm-workers-server


text:
Traceflow resources must be cleaned up after use

Describe the bug
Once a Traceflow is initiated, a TF CRD object is created in the cluster which is used to provide the functionality and the result of the trace. However, once the result is posted, the TF object remains in the cluster until it is explicitly deleted by the user. This is not ideal.
To Reproduce
Create a TF. Observe the result. Wait for a few days. Still see the TF object in cluster.
Expected
Some sort of garbage collection mechanism to clean up such old TF objects from the system.
Additional context
Need to introduce a garbage collection mechanism.

Hi @abhiraut, for antrea-octant-plugin, we will automatically delete the traceflow CRD created by UI after 300s/5min.

thanks for the confirmation. closing this issue.

authors: abhiraut mengdie-song

repo: vmware-tanzu/antrea


text:
Add build-wrapper fragment

This introduces an option to include build wrapper that is enabled by default but can be turned off to prevent issues in air-gapped environments where the builds won't be able to download wrapper files.
For the multi-module accelerators (spring-smptp-gateway and where-for-dinner) the mvn wrapper has been removed from the modules and will only be added to the top level parent directory.

I'm confused. How would passing an unknown buildTool value (say "make") make sense for the fragment, which doesn't know about it?
What I'm proposing is to have a single option, whatever its name, whose values are none, maven and gradle (and could later be expanded, but let's start with those)

It's my turn to be confused, how would you express "I want maven" and "no wrapper" with single option that would also work for an accelerator that only supported maven so "no wrapper" would be the only option needed. As for passing in buildTool there would be a limited set that the fragment supports and "make" is not one of them so the accelerator author would need to use a different fragment or write their own logic. I guess one solution would be to have a buildTool option that could be hidden and set to the desired value.

One way of solving this would be to have two fragments, one for "maven" and one for "gradle" and let the accelerator call invoke the appropriate one.

authors: ericbottard trisberg


text:
Do not delete subpath when there are updates to source spec

Pull request

What this PR does / why we need it
Avoid deleteting subpath when there is an update to other source specifications, as source image or git reference.
Which issue(s) this PR fixes

Fixes #431
Describe testing done for PR

Created/updated various workloads with different source specifications
Added unit testing

Additional information or special notes for your reviewer

In the GitHub issue, there was a description relating this error to Git references, but it happens to be also affecting source image specification, so whenever the image was updated, if there was a subpath, was being deleted in the process.
This PR also addresses and corrects this behaviour.

Signed-off-by: Wendy Arango warango@vmware.com

With this approach, despite subpath is not being deleted when there is an update, a problem that I encountered is that whenever updating a workload from one source to another, then the subpath remains in the workload source.
For example, let's say I have a workload created with a source image, like the following:
tanzu apps workload apply java-web-app --local-path . -s my-registry.nip.io/apps/warango-java-web-app --type web  --registry-username my-username --registry-password my-password --label hello=world --sub-path tanzu-java-web-app -y

and after created I would like to completely change the source
tanzu apps workload apply java-web-app --git-repo https://github.com/vmware-tanzu/application-accelerator-samples --git-tag tap-1.3

Then the update would look like:
🔎 Update workload:
...
  8,  8   |  name: java-web-app
  9,  9   |  namespace: default
 10, 10   |spec:
 11, 11   |  source:
 12     - |    image:my-registry.nip.io/apps/warango-java-web-app:latest@sha256:130b834c03da878f37222551b68ab580e337d728712636b656f08e5648b680dd
     12 + |    git:
     13 + |      ref:
     14 + |        tag: tap-1.3
     15 + |      url: https://github.com/vmware-tanzu/application-accelerator-samples
 13, 16   |    subPath: tanzu-java-web-app
❓ Really update the workload "java-web-app-no-cert"? [yN]

As demonstrated, the workload subpath is not being deleted as part of the source changes.
Would this be the right behaviour?

With this approach, despite subpath is not being deleted when there is an update, a problem that I encountered is that whenever updating a workload from one source to another, then the subpath remains in the workload source.
For example, let's say I have a workload created with a source image, like the following:
tanzu apps workload apply java-web-app --local-path . -s my-registry.nip.io/apps/warango-java-web-app --type web  --registry-username my-username --registry-password my-password --label hello=world --sub-path tanzu-java-web-app -y

and after created I would like to completely change the source
tanzu apps workload apply java-web-app --git-repo https://github.com/vmware-tanzu/application-accelerator-samples --git-tag tap-1.3

Then the update would look like:
🔎 Update workload:
...
  8,  8   |  name: java-web-app
  9,  9   |  namespace: default
 10, 10   |spec:
 11, 11   |  source:
 12     - |    image:my-registry.nip.io/apps/warango-java-web-app:latest@sha256:130b834c03da878f37222551b68ab580e337d728712636b656f08e5648b680dd
     12 + |    git:
     13 + |      ref:
     14 + |        tag: tap-1.3
     15 + |      url: https://github.com/vmware-tanzu/application-accelerator-samples
 13, 16   |    subPath: tanzu-java-web-app
❓ Really update the workload "java-web-app-no-cert"? [yN]

As demonstrated, the workload subpath is not being deleted as part of the source changes.
Would this be the right behaviour?

Nope. Because the plugin cannot know whether the same sub-path would exist when the new source was specified, this would not be the right behavior.

Thanks @warango4
Here's what I think the expected behavior should be for various scenarios:

for an existing workload created from --git* and which included a --sub-path:

if the user changes --git-tag, --git-commit or --git-branch - original sub-path should remain intact
if the user changes to --image, --local-path or --maven* - original subpath should be removed

for an existing workload created from --local-path and which included a --sub-path:

if the user changes to --git* or --image or --maven* - original subpath should be removed

Delete sub-path when changing from one source to another

AC
overall summary - failed AC
PASS - subPath removed as expected when swapping from --git* to --local-path or --image

FAIL - subPath removed unexpectedly when switching a --git reference

create workload via git*tanzu apps workload apply java-web-app --git-repo https://github.com/vmware-tanzu/application-accelerator-samples --git-tag tap-1.3 --sub-path tanzu-java-web-app

update workload to reference a different --git-tag -OR- a  --git-commit -OR- a --git-branch

results in removing subPath - this isn't expected

hey @heyjcollins
So I just tried with your sample in the latest from main and I'm not getting this error.

Can you please tell me what's your apps version
I have this one
$ tanzu apps version
v0.10.0+dev-042d5df7

repo: vmware-tanzu/apps-cli-plugin


text:
Publish a ROADMAP

Description of problem
Currently, the project repository lacks a ROADMAP document that could guide users and potential contributors about the future of the project and align ideas and contributions around a clear vision.

Ask for Zach Robinson to provide us with the details for this (or edit the docs directly)

Ask for Zach Robinson to provide us with the details for this (or edit the docs directly)

Correct, Zach is already aware of this request and will provide updates when available

Example from paketo - https://github.com/paketo-buildpacks/community/blob/main/ROADMAP.md

authors: davidmirror-ops emmjohnson squeedee

repo: vmware-tanzu/cartographer


text:
Accept File Marks for any valid path (via --file-marks-yaml)

Describe the problem/challenge you have
Tool integrators would like the ability to integrate with ytt, accepting paths to files without limitation.
That integration includes the ability to configure processing of sets of files via File Marks.
Today, file marks are supplied via a command-line flag whose argument is of a specific format that uses the : and = characters as delimiters.
These are valid characters for paths on most operating systems.
This means there are valid path names (however uncommon) for which there is no way to configure a file mark.
Describe the solution you'd like
Introduce a new command-line flag: --file-marks-yaml which contains a sequence of file mark-shaped mappings. In this way, any string can be supplied for path.
For example:
$ ytt -f . --file-marks-yaml '[{"path": "conf:ig.yml", "type": "yaml-plain"}]'

This flag should be able to process all known file marks: https://carvel.dev/ytt/docs/latest/file-marks/#docs
Anything else you would like to add:
This request originated with #468.

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

While this is not on the roadmap for the core maintainers, if someone would fashion this contribution, we'd happily accept. 👍🏻

repo: vmware-tanzu/carvel-ytt


text:
Use mirror.gcr.io by default

What this PR does / why we need it:
While still rate-limited, GCR's mirror of Docker Hub has a significantly higher threshold (assuming the same rate limit for any GCR repository)
Reference: https://cloud.google.com/container-registry/quotas
Which issue(s) this PR fixes
None
Special notes for your reviewer:
None
Release note:
dockerLibraryRegistry default entry is now mirror.gcr.io

Was this being debated or does this need to merge?

This is not enough actually -- changing the manifest would not result in Sonobuoy passing the manifest to the Conformance container.
Do you want to pick this up?

Will do.

Are we trying to, by default, pass that to the k8s container in the same way they do custom registries in general? E.g. the same way we do airgap?

E.g. the same way we do airgap?

In my mind, yes. I don't know if that's still the best approach though. Last time I worked on this, I had these edge cases in mind:

we use GCR by default, meaning always passing the manifest to conformance image
users specify some other registry, so we pass that on to conformance image
users specify that they actually want to use DockerHub, then we should detect and prevent our GCR override from being put in place

I'm not certain this is the right approach tbh at this point. It sounds like this is something that upstream should be fixing and actually, I've not seen the rate limit issues on those core images. Does anyone have logs showing it rate limiting those? Certain OSS repos can get exempted and other projects may pay for it.
As for our dockerhub images, we are starting to mirror them in our public harbor registry and so we may consider using that by default which would actually be our responsibility and a much more simple, in-code fix.

Closing for now, can be reopened if someone feels differently and we talk about it.

authors: johnSchnake wilsonehusin

repo: vmware-tanzu/sonobuoy


text:
[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc we don't use Prow
/assign we don't use Prow
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/pkg 7b5ecbc...bda81c0:
  > bda81c0 upgrade to latest dependencies (# 2218)
bumping knative.dev/eventing 4b18ab8...19fcdf4:
  > 19fcdf4 Fix DeadLetterSink on Trigger status (# 5642)
  > cfcab6f remove vaikas from roster (# 5645)
  > 3a4912d upgrade to latest dependencies (# 5635)
  > 9dd1419 Fix deprecation of controller.Run to controller.RunContext (# 5644)

Codecov Report

Merging #276 (18b3dcd) into main (cb72aeb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #276   +/-   ##
=======================================
  Coverage   80.39%   80.39%
=======================================
  Files          20       20
  Lines         765      765
=======================================
  Hits          615      615
  Misses        136      136
  Partials       14       14

Continue to review full report at Codecov.

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

authors: codecov-commenter knative-automation

repo: vmware-tanzu/sources-for-knative


text:
Expand clr-tree-node by clicking its text

[ ] bug
[x] feature request
[ ] enhancement

Expected behavior
I was wondering if it would be possible to expand a <clr-tree-node> by clicking/touching it's label in addition of the caret icon
Actual behavior
For now it's only possible to expand a <clr-tree-node> by clicking/touching its associated caret icon.

@MattMattV: We won't be able to provide that functionality because that wouldn't work for cases like routing with trees where users use a link in the tree-node to route to different components. But if you had to, you could simply use the clrTreeNodeExpanded input and toggle it when the node is clicked. Something like this: https://plnkr.co/edit/jX6JmHnEblzgqWRWYJN8?p=preview

Closing this issue based on the above comment.

Thank you for the workaround !

@adityarb88  Could you please reupload the Plunker? I don't know how to use the clrTreeNodeExpanded input.

@hubertkubiak - this is a very old issue. Can you ask your question on StackOverflow and label it with vmware-clarity? We can answer implementation questions there.

authors: MattMattV adityarb88 hippee-lee hubertkubiak

repo: vmware/clarity

license: MIT


text:
content-container/area not displayed properly when using routing!

Describe the bug
When using the "Vertical-Navbar" inside a component, loaded through a <router-outlet></router-outlet>, the navbar is not taking its full content-height on the left side of the application and only uses a small portion. It seems like there is a problem with using the router-outlet together with "content-container", "content-area" and so on.
How to reproduce
Just see the example I build:
https://stackblitz.com/edit/angular-10-claritybug-verticalnav?file=src/app/app.component.html
If you comment out the "router-outlet" and instead uncomment the other part, it works as intended. When using the same structure inside the dummy.component.html, it stops working again.
Expected behavior
Expecting to act just as if it was loaded without , properly displaying the vertical navbar and content-area.
Versions
Clarity project:

[ ] Clarity Core
[X] Clarity Angular/UI

Clarity version:

[ ] v3.x
[X] v4.x
[X] v5.x

Framework:

[x] Angular

Framework version:
_ie: Angular 10.2.5
Additional notes
Maybe I did something wrong but tried a lot of stuff and it boils down to the same problem again and again.

I see what you are trying to do, but it comes to the way Angular components are built, and there is not much we can enforce as solution from the Clarity side, without some heavy-lifting code, which may have many unexpected side effects. The good news is that you have a very easy solution for your code.
Why this happens?
Our nav and content-area sections get their placement from the content-container. The content container dictates that it will be a flex-box and it's children, placed by default, one next to the other.
When you add the nav and content area through a component, though, they are not the immediate children of the content-container anymore. There is an intermediate host-container for the component. It is the single child of the content-container now and it has no display definitions on its own. So, its children (the nav and content-area) are placed naturally, as divs, one below the other.
What we can do is to add flex-box to the host-container. I.e. add this to your dummy.component.css file:
:host {
  display: flex;
}


text:
LDAP Library used is deprecated

According to the OpenLDAP library used on Harbor project (https://github.com/mqu/openldap), it's deprecated and the maintainer is not going to continue it's development.
This brings some other non desirable behaviour, as not supporting StartTLS, non configurable dial timeout (this brings a lot of problems when you try to pull an image from an anonymous repository) and limits a future work to support LDAP Group (and a lot of other problems).
Fortunatelly, there is another library (that is much more updated) here: https://github.com/go-ldap/ldap
So, this issue is to register an attempt to migrate from the old library to a new one. I'm going to open a PR submitting changes to this, and then some other commits to solve the "TODO" marked on the code.
Any suggestion? :smile:

@rikatz
Thank you for your recommend~
We already start working on this. Will update LDAP library soon.
#1136

Solved in the PR, closing the issue.

repo: vmware/harbor


text:
Fix bugs infinity copy of reponame and auth

everytime click deploy or add additional info will add a prefix before reponame
add constrait on button on cardview

Coverage increased (+0.07%) to 64.464% when pulling ef00ffbab8d3dfa842d23b6c0f50e6c72fe3f883 on ninjadq:fix_copy_name_bug into 535ffbe28fdfd4f5beb3ce0ba46bbe43be6d8f3f on vmware:release-1.5.0.

authors: coveralls ninjadq


text:
var name should not be error

var name should not be error.

Pull Request Test Coverage Report for Build 7679

2 of 6 (33.33%)  changed or added relevant lines in 2 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.02%) to 64.604%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/common/dao/config.go
2
3
66.67%

src/adminserver/systemcfg/store/database/driver_db.go
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/common/dao/config.go
1
72.22%

src/jobservice/logger/sweeper.go
4
63.46%

Totals

Change from base Build 7678:
-0.02%

Covered Lines:
11769

Relevant Lines:
18217

💛  - Coveralls

authors: coveralls silenceshell


text:
https changed the home page

Hi,
We added a cert to Webcommander. and now the home page is no longer working correctly. Is there something else we have to change? The menu choices are all jammed up on the left, and nothing happens if you try to choose a category.
Thanks!

made changes according to this web site but still have the same issue:
https://ssbkang.com/2014/02/11/webcommander-ssl-certificate-installation/

I made the above changes to no avail. We saw errors showing that we could not get to index.xsl:40:                 using https, so he copied the script down c:\webcommander\www and changed index.xsl to reflect the new location.
That solved the problem.

repo: vmware/webcommander

license: mit

license_source: bigquery


text:
Assertion error in 'get_uptodate_def_insn' relating to division by sizeof(char)

#include <stdio.h>

struct string { char* begin; char* end; };

unsigned long size(struct string a) {
	return (a.end - a.begin) / sizeof(char);
}

struct string2 {
	char* begin;
	unsigned long size;
};

struct string2 convert(struct string a) {
	return (struct string2) {a.begin, size(a)};
}

void main(void) {
	char c[3] = "foo";
	struct string s = {c, c + 3};
	printf("%lu\n", size(s));
}

Running c2m a.c -eg, I get:
c2m: mir-gen.c:4600: get_uptodate_def_insn: Assertion `!gen_ctx->selection_ctx->hreg_refs_addr[hr].del_p' failed.

I've done my best to reduce this error, but it seems to depend on a pretty specific scenario.

There's no error if you use unsigned instead of unsigned long for the size.
There's no error if you remove convert (which isn't used) or remove either member of string2 (also unused).
There's no error if you remove / sizeof(char) or replace it with / 1.

Update: It's not the sizeof that's the problem, but the type of the divisor. It breaks the same if you replace sizeof(char) with 1uLL.

Thank you for reporting this issue which is actually a bug in code selection pass.
I've fixed it on master by b79c0ee2e919bea54ac0f877b5aba5a6cf68b69e.

Thanks, I confirmed it's working now.

authors: andy-hanson vnmakarov

repo: vnmakarov/mir


text:
CTPJ接口在替换海通的api后无法显示行情，交易功能正常

环境

操作系统: Windows 10
Python版本: 如VNStudio-2.0.7
vn.py版本: 如v2.0.7

Issue类型
三选一：Bug/Enhancement/Question
预期程序行为
实际程序行为
重现步骤
针对Bug类型Issue，请提供具体重
现步骤以及报错截图
行情和交易显示连接成功，合约也可以查询，但是不能显示行情。

看不到图片，请检查行情地址是否设置正确了

authors: liuyunjr vnpy

repo: vnpy/vnpy


text:
VNPY2.0.x 在mongoDB没有连接的情况下，记录数据没有任何报错，也不提示错误信息

操作系统: 如Windows 10
vn.py版本: 如v2.0.7发行版

Issue类型
三选一：Bug
预期程序行为
mongo数据库没建好的情况下应该有提示或者报错的。
实际程序行为
群主，您好
数据库没有连接的情况下，应该报错或有提示信息，但是实际mongodb中没创建任何库，程序没任何提示的。
特意把把数据库drop了进行测试的。

先是drop库后debug的时候发现这种情况的，然后又不再用debug模式进行测试，图是非debug模式测试结果。


text:
ubuntu-install-failure

环境

操作系统: Ubuntu desktop 16.04
Anaconda版本: 如Anaconda 5.0.1 Python 2.7 32位
vn.py版本: 1.7.3

Issue类型
Question
预期程序行为
python run.py OK
实际程序行为
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$ python run.py
Traceback (most recent call last):
  File "run.py", line 19, in <module>
    from vnpy.trader.gateway import (ctpGateway, oandaGateway,
  File "/home/tom/.ana/lib/python2.7/site-packages/vnpy/trader/gateway/ctpGateway/__init__.py", line 4, in <module>
    from ctpGateway import CtpGateway
  File "/home/tom/.ana/lib/python2.7/site-packages/vnpy/trader/gateway/ctpGateway/ctpGateway.py", line 16, in <module>
    from vnpy.api.ctp import MdApi, TdApi, defineDict
  File "/home/tom/.ana/lib/python2.7/site-packages/vnpy/api/ctp/__init__.py", line 3, in <module>
    from vnctpmd import MdApi
ImportError: No module named vnctpmd
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$

重现步骤
针对Bug类型Issue，请提供具体重现步骤以及报错截图
我也遇到了同样的问题....按 @vnpy 的方法, 也未解决...
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3$ cd examples/VnTrader/
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$ pip show vnpy
Name: vnpy
Version: 1.7.3
Summary: A framework for developing Quantitative Trading programmes
Home-page: http://www.vnpy.org
Author: Xiaoyou Chen
Author-email: vn.py@foxmail.com
License: MIT
Location: /home/tom/.ana/lib/python2.7/site-packages
Requires:

说明安装了...
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$ ls
CTA_setting.json  CTP_connect_带客户端认证.json  FEMAS_connect.json  OANDA_connect.json  run.py         SEC_connect.json  temp                VnTrader.bat     XSPEED_connect.json
CTP_connect.json  DR_setting.json                IB_connect.json     RM_setting.json     run_simple.py  ST_setting.json   TKPRO_connect.json  VT_setting.json  XTP_connect.json
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$ python run.py
Traceback (most recent call last):
  File "run.py", line 19, in <module>
    from vnpy.trader.gateway import (ctpGateway, oandaGateway,
  File "/home/tom/.ana/lib/python2.7/site-packages/vnpy/trader/gateway/ctpGateway/__init__.py", line 4, in <module>
    from ctpGateway import CtpGateway
  File "/home/tom/.ana/lib/python2.7/site-packages/vnpy/trader/gateway/ctpGateway/ctpGateway.py", line 16, in <module>
    from vnpy.api.ctp import MdApi, TdApi, defineDict
  File "/home/tom/.ana/lib/python2.7/site-packages/vnpy/api/ctp/__init__.py", line 3, in <module>
    from vnctpmd import MdApi
ImportError: No module named vnctpmd
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$ pip list | grep vnctpmd
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$

说明没有安装成功
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$ pip install vnctpmd
Collecting vnctpmd
  Could not find a version that satisfies the requirement vnctpmd (from versions: )
No matching distribution found for vnctpmd
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3/examples/VnTrader$

看来这么安装vnctpmd是没有成功的.

安装过程中的一些可怀疑点
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3$ bash ./install.sh
.......省略
Scanning dependencies of target vnib
make[2]: Leaving directory '/home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/build'
make -f CMakeFiles/vnib.dir/build.make CMakeFiles/vnib.dir/build
make[2]: Entering directory '/home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/build'
[ 50%] Building CXX object CMakeFiles/vnib.dir/vnib/vnib/vnib.cpp.o
/usr/bin/c++   -DBUILD_IB -DUSE_64BITS -Dvnib_EXPORTS -I/home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/./ibapi/linux/client -I/home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/IB_PATH -I/usr/include/python2.7  -fPIC -std=c++11 -O3 -DNDEBUG -fPIC   -o CMakeFiles/vnib.dir/vnib/vnib/vnib.cpp.o -c /home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/vnib/vnib/vnib.cpp
In file included from /home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/./ibapi/linux/client/EClientSocket.h:8:0,
                 from /home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/vnib/vnib/vnib.h:25,
                 from /home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/vnib/vnib/vnib.cpp:5:
/home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/./ibapi/linux/client/EClient.h:350:10: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
     std::auto_ptr<ETransport> m_transport;
          ^
In file included from /usr/include/c++/5/memory:81:0,
                 from /usr/include/boost/function/function_base.hpp:16,
                 from /usr/include/boost/function/detail/prologue.hpp:17,
                 from /usr/include/boost/function/function_template.hpp:13,
                 from /usr/include/boost/function/detail/maybe_include.hpp:13,
                 from /usr/include/boost/function/function0.hpp:11,
                 from /usr/include/boost/python/errors.hpp:13,
                 from /usr/include/boost/python/handle.hpp:11,
                 from /usr/include/boost/python/to_python_value.hpp:12,
                 from /usr/include/boost/python/default_call_policies.hpp:10,
                 from /usr/include/boost/python/make_function.hpp:10,
                 from /usr/include/boost/python/def.hpp:11,
                 from /home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/vnib/vnib/vnib.h:10,
                 from /home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/vnib/vnib/vnib.cpp:5:
/usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^
[100%] Linking CXX shared library lib/vnib.so
/usr/bin/cmake -E cmake_link_script CMakeFiles/vnib.dir/link.txt --verbose=1
/usr/bin/c++  -fPIC  -fPIC -std=c++11 -O3 -DNDEBUG  -shared -Wl,-soname,vnib.so -o lib/vnib.so CMakeFiles/vnib.dir/vnib/vnib/vnib.cpp.o ../ibapi/linux/build/lib/twsapi.so -lboost_python -lboost_thread -lboost_date_time -lboost_system -lboost_chrono -lboost_atomic -lpthread /home/tom/.ana/lib/libpython2.7.so -Wl,-rpath,/home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/ibapi/linux/build/lib:/home/tom/.ana/lib
make[2]: Leaving directory '/home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/build'
[100%] Built target vnib
make[1]: Leaving directory '/home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/build'
/usr/bin/cmake -E cmake_progress_start /home/tom/vnpy/vnpy-1.7.3/vnpy/api/ib/build/CMakeFiles 0
~/vnpy/vnpy-1.7.3/vnpy/api/ib
~/vnpy/vnpy-1.7.3
Requirement already satisfied: pymongo in /home/tom/.ana/lib/python2.7/site-packages (from -r requirements.txt (line 1))
Requirement already satisfied:

过了一会儿
/usr/bin/c++   -DBUILD_IB -DUSE_64BITS -Dtwsapi_EXPORTS -I/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/IB_PATH  -fPIC -std=c++11 -O3 -DNDEBUG -fPIC   -o CMakeFiles/twsapi.dir/client/EClientSocket.cpp.o -c /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClientSocket.cpp
In file included from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClientSocket.h:8:0,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClientSocket.cpp:8:
/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:350:10: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
     std::auto_ptr<ETransport> m_transport;
          ^
In file included from /usr/include/c++/5/memory:81:0,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:9,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClientSocket.h:8,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClientSocket.cpp:8:
/usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^
[ 13%] Building CXX object CMakeFiles/twsapi.dir/client/EMutex.cpp.o
/usr/bin/c++   -DBUILD_IB -DUSE_64BITS -Dtwsapi_EXPORTS -I/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/IB_PATH  -fPIC -std=c++11 -O3 -DNDEBUG -fPIC   -o CMakeFiles/twsapi.dir/client/EMutex.cpp.o -c /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EMutex.cpp
[ 18%] Building CXX object CMakeFiles/twsapi.dir/client/OperatorCondition.cpp.o
/usr/bin/c++   -DBUILD_IB -DUSE_64BITS -Dtwsapi_EXPORTS -I/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/IB_PATH  -fPIC -std=c++11 -O3 -DNDEBUG -fPIC   -o CMakeFiles/twsapi.dir/client/OperatorCondition.cpp.o -c /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/OperatorCondition.cpp
In file included from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/OperatorCondition.cpp:4:0:
/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:350:10: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
     std::auto_ptr<ETransport> m_transport;
          ^
In file included from /usr/include/c++/5/memory:81:0,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:9,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/OperatorCondition.cpp:4:
/usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^
[ 22%] Building CXX object CMakeFiles/twsapi.dir/client/PriceCondition.cpp.o
/usr/bin/c++   -DBUILD_IB -DUSE_64BITS -Dtwsapi_EXPORTS -I/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/IB_PATH  -fPIC -std=c++11 -O3 -DNDEBUG -fPIC   -o CMakeFiles/twsapi.dir/client/PriceCondition.cpp.o -c /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/PriceCondition.cpp
In file included from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/PriceCondition.cpp:5:0:
/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:350:10: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
     std::auto_ptr<ETransport> m_transport;
          ^
In file included from /usr/include/c++/5/memory:81:0,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:9,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/PriceCondition.cpp:5:
/usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^
[ 27%] Building CXX object CMakeFiles/twsapi.dir/client/EReader.cpp.o
/usr/bin/c++   -DBUILD_IB -DUSE_64BITS -Dtwsapi_EXPORTS -I/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/IB_PATH  -fPIC -std=c++11 -O3 -DNDEBUG -fPIC   -o CMakeFiles/twsapi.dir/client/EReader.cpp.o -c /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EReader.cpp
In file included from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClientSocket.h:8:0,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EReader.cpp:10:
/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:350:10: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
     std::auto_ptr<ETransport> m_transport;
          ^
In file included from /usr/include/c++/5/memory:81:0,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:9,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClientSocket.h:8,
                 from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EReader.cpp:10:
/usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here
   template<typename> class auto_ptr;
                            ^
[ 31%] Building CXX object CMakeFiles/twsapi.dir/client/EClient.cpp.o
/usr/bin/c++   -DBUILD_IB -DUSE_64BITS -Dtwsapi_EXPORTS -I/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/IB_PATH  -fPIC -std=c++11 -O3 -DNDEBUG -fPIC   -o CMakeFiles/twsapi.dir/client/EClient.cpp.o -c /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.cpp
In file included from /home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.cpp:8:0:
/home/tom/vnpy/vnpy-1.7/vnpy/api/ib/ibapi/linux/client/EClient.h:350:10: warning: ‘template<class> class std::auto_ptr’ is deprecated [-Wdeprecated-declarations]
     std::auto_ptr<ETransport> m_transport;
          ^

最后输出是下面这样的
vnpy.trader.gateway.xspeedGateway.xspeedGateway: module references __file__
vnpy.trader.gateway.xtpGateway.xtpGateway: module references __file__
vnpy.trader.gateway.zbGateway.zbGateway: module references __file__
creating 'dist/vnpy-1.7.2-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing vnpy-1.7.2-py2.7.egg
removing '/home/tom/.ana/lib/python2.7/site-packages/vnpy-1.7.2-py2.7.egg' (and everything under it)
creating /home/tom/.ana/lib/python2.7/site-packages/vnpy-1.7.2-py2.7.egg
Extracting vnpy-1.7.2-py2.7.egg to /home/tom/.ana/lib/python2.7/site-packages
  File "/home/tom/.ana/lib/python2.7/site-packages/vnpy-1.7.2-py2.7.egg/vnpy/trader/gateway/okexGateway/okexGateway.py", line 576
    for symbol in :
                  ^
SyntaxError: invalid syntax

Removing vnpy 1.7.0 from easy-install.pth file
Adding vnpy 1.7.2 to easy-install.pth file

Installed /home/tom/.ana/lib/python2.7/site-packages/vnpy-1.7.2-py2.7.egg
Processing dependencies for vnpy==1.7.2
Finished processing dependencies for vnpy==1.7.2
tom@udvbud-vnpy-py2-a:~/vnpy/vnpy-1.7.3$

那...怎么破呢?

在1.8中，出现了同样问题，有人解决了么？

authors: nehcuh tomtsang


text:
callback(bar) 重复调用

https://github.com/vnpy/vnpy_ctastrategy/blob/main/vnpy_ctastrategy/backtesting.py#L789
重复调用 callback(bar) 导致重复调用on_bar
vnpy_ctastrategy/template.py
    def load_bar(
        self,
        days: int,
        interval: Interval = Interval.MINUTE,
        callback: Callable = None,
        use_database: bool = False
    ) -> None:

        if not callback:
            callback: Callable = self.on_bar

        bars: List[BarData] = self.cta_engine.load_bar(
            self.vt_symbol,
            days,
            interval,
            callback,
            use_database
        )

        for bar in bars:
            callback(bar)

vnpy_ctastrategy/backtesting.py
    def load_bar(
        self,
        vt_symbol: str,
        days: int,
        interval: Interval,
        callback: Callable,
        use_database: bool
    ) -> List[BarData]:
        """"""
        self.callback = callback

        init_end = self.start - INTERVAL_DELTA_MAP[interval]
        init_start = self.start - timedelta(days=days)

        symbol, exchange = extract_vt_symbol(vt_symbol)

        bars: List[BarData] = load_bar_data(
            symbol,
            exchange,
            interval,
            init_start,
            init_end
        )

        for bar in bars:
            callback(bar)

        return bars

已修复https://github.com/vnpy/vnpy_ctastrategy/pull/34

已修复，感谢反馈

authors: noranhe szshower vnpy


text:
[2.x] Updated Class Names to commonly using form

Updated Class Names to commonly using form.

This is a major breaking change because it breaks autoloading on case-sensitive filesystems..

This PR doesn't do what it says btw. PSR-4 says nothing about having to use uppercase for the first name of the vendor. It actually says:

Alphabetic characters in the fully qualified class name MAY be any combination of lower case and upper case.

@GrahamCampbell Commonly Studly Case using of php packages.

But not required for PSR-4...

@GrahamCampbell Ok, updated.

authors: GrahamCampbell voyula

repo: voku/portable-ascii


text:
Override fespec#touch API

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

#30

repo: volcengine/tosfs


text:
Make nodes option working again for generate_cluster_xml.py

The nodes option for generate_cluster_xml.py is confusing because it does nothing when the file option is provided, but the file option got mandatory about 3 years ago when the file exists check was added.
Therefore I propose this fix, or alternatively remove this option altogether (since it's not working since 3 years I guess nobody will miss it?)

I merged it in. Thanks!

authors: FelixGV bitti

repo: voldemort/voldemort


text:
Updated KinaseFocusedLibrary

Description
Update this Repository
Todos
Notable points that this PR has either accomplished or will accomplish.

[x] Update README
[x] Update .gitignore
[x] Update packages (#32 )
[x] Resolve #27
[x] Resolve #23
[x] Re-run all scripts

Status

[x] Ready to go

Hi @dominiquesydow, @kabu00002 updated the kffl repository and fixed some open issues. If you have time, could you review the changes so we can merge them? Thanks a lot!


text:
about this powerful Framework

hi Volkanceylan ,
Your framework is very powerful, to help me reduce the most of the programming time.
When I first started to use, has been learning how to use it.
But now I want to know how to do it so cool I believe and I have the same idea certainly a lot of people.
Can you  use a few chapters about your framework?
Not how to use the angle, but how to achieve the point of view.
Thank you for sharing the framework, for me it is like a treasure, so I am eager to explore

You can use a few chapters to introduce this framework?
Roughly the outline

Thanks @thisXYH, but what chapter you exactly request? Something about design patterns, or how things work behind the scene?

You can describe how it works behind the scenes, using what tools and what design patterns, but not too deep into the design pattern.
Mainly to give us a direction and outline to understand the framework, so that we can more easily absorb the framework.
We can read your source code and these chapters to understand the framework,Instead of looking at samples and manuals to use this framework.
We should all know that learning things are generally used from the transition to understand why so use.
Thanks @volkanceylan .I hope I can make you understand the description

Carelessly press the Close button ...

authors: thisXYH volkanceylan

repo: volkanceylan/Serenity


text:
Error when querying lookup table

Hi, I am trying to get a dropdown field for a foreign key reference on my form. I followed the instructions in the guide (p74 ff), but when I query it with q.getLookup(Researcher.Publisher), I get the following error:
Script data Lookup.Researcher.Publisher is not found in registered script list
What am I doing wrong?

You need add lookup attribute on publisher row for auto register.

I have the following on the PublisherRow class:

Still not working.

typo fix Reasercher => Researcher

Thanks! Did not spot that. It works.

Np :smile: extra two eyes always better

authors: VictorTomaili wpvking


text:
how to call jQuery

I found this sample to hide radio button:
$("label:contains('Invoice')").css("display", "none");
but I don't know how to call it in Serenity.
Any ideas?
thx

I figured this one out:
this.element.find("label:contains('Invoice')").css("display", "none");
works ok, but I'd prefer to base search on something else, cause item description can possibly change with different language

Hi!
@ga5tan
Actually, having the same issue
want to hide the radio button from the Transaction grid while editing records
Thanks in advance.

So? Try this one, or get inspired by tab hiding code.
In browser check what div or container radios are and hide it, or hide column. Do u edit in grid or dialog?

thanks, @ga5tan sir
I already try hiding by div and container radios but it's just not working
I  haven't seen any sample for hiding DetailList grid columns from the master dialog

sorry, I have no better idea than hiding.
inspiration was to be taken from tab hiding, not DetailList grid columns hiding.
but there must be some way to hide columns as well, since there is column picker...


text:
what is ss and arrayAddRange ?

When I looking into the source code, i found there is a ss and arrayAddRange?
I don't understand what is ss and arrayAddRange? how to use them in typescript.

Before typescript, serenity was based on Salterelle (A C# to JS compiler). I think this ss is from the salterelle's compiled JS.

I soloved my problem with below code.
private _filterLines: Serenity.FilterLine[];

        get filterLines() {
            return this._filterLines;
        }

        set filterLines(value: Serenity.FilterLine[]) {
            if (this._filterLines !== value) {
                this._filterLines = value;
                (ss as any).clear(this.filterBar.get_store().get_items());
                (ss as any).arrayAddRange(this.filterBar.get_store().get_items(), value);
                this.filterBar.get_store().raiseChanged();

            }
        }

But i still don't understand how is (ss as any).clear() and (ss as any).arrayAddRange working

if you type ss in the browser console you will be able to find the all ss methods as well as definition.

To get the definition you might type ss.clear and press enter

@dfaruque thanks very much


text:
Uncaught TypeError: Cannot read property 'VehiclesGrid' of undefined

Hi,
I have been getting this error and couldn't find any fix in the current issue list. I then Installed Visual Studio 2015, re-downloaded the template and recreated my DB with the migration added, TypeScript was installed but I am still getting the error when I run the solution and try to open the Grid.
Could you please assist me in where to look for the issue?

Check your page index.cshtml. See which namespace your VehicleGrid is in there, and in actual Web.js file.

authors: Thebenmandude volkanceylan


text:
Add XDBC Type info to DuckDB back-end

We need to add the XDBC Type info to the DuckDB back-end to be consistent with the SQLite back-end.

Could this use the ADBC stuff in DuckDB?

repo: voltrondata/flight-sql-server-example


text:
Split bespoken plugin into transform and export commands

See #1
Resources

https://oclif.io/docs/running_programmatically

Got this backwards... I actually want to make the colang plugin have a transform command, rather than an export command.

repo: voxable/cli


text:
[FR] Reasonable frame selection for video datasets with 2+ video samples

Proposal Summary
The dataset.annotate() method accepts kwargs frame_start, frame_stop and frame_step for the CVAT labeling backend. This works for video datasets that only include one video sample. But when there are multiple video samples, each sample includes frames with overlapping frame numbers. annotate end up pulling from frames from the sample.
(In general, it seems like videos are treated more like datasets, rather than samples by many functions/methods in FiftyOne.)
This would help build FO's capabilities for managing video datasets.
Motivation

What is the use case for this feature?

Allow partial labelling of specific clips of videos, in dataset with multiple videos.

Why is this use case valuable to support for FiftyOne users in general?

Enhance the usefulness of datasets with multiple videos.

Why is this use case valuable to support for your project(s) or organization?

I have many videos I need to label, that I want to be able to treat as a contiguous dataset.

Why is it currently difficult to achieve this use case?

Impossible, as far as I'm aware. Can't send FrameViews for annotation, no way to refer to specific samples within a particular dataset.

What areas of FiftyOne does this feature affect?

[ ] App: FiftyOne application
[x] Core: Core fiftyone Python library
[ ] Server: FiftyOne server

Details
I'm proposing a new parameter that allows the user to pass a dict with a key for each sample id, and optional kwargs for [frame_start, frame_stop and frame_step, frame_num_list, frame_ids] that are used to select the frames from each sample that should be sent to CVAT.
Willingness to contribute
The FiftyOne Community welcomes contributions! Would you or another member of your organization be willing to contribute an implementation of this feature?

[ ] Yes. I can contribute this feature independently
[x] Yes. I would be willing to contribute this feature with guidance from the FiftyOne community
[ ] No. I cannot contribute this feature at this time

I've gotten fairly comfortable with using fiftyone as a developer, but haven't really explored the backend and CVAT API specifically. I'm willing to consult, but probably don't have the time to learn enough of the CVAT integration backend to actually implement this myself.

Hey @evatt-harvey-salinger ! Those kwargs should also accept a list and dictionary in the case that you are annotating multiple video samples at once: https://docs.voxel51.com/integrations/cvat.html#requesting-annotations
Let me know if that is what you have in mind

Ah, of course you're right. Apologies for suggesting feature that already exists. I hadn't had the page up, and had trouble tracing the kwargs for dataset.annotate back through the code base. I finally have the CVATBackendConfig pulled up, which would've answered my questions.

authors: ehofesmann evatt-harvey-salinger


text:
Update Rubocop version

https://github.com/voxpupuli/puppet-mongodb/blob/beab7b472fdce98ef640769290ffcd72f369d640/Gemfile#L26
Would it make sense to update the current version spec here or loosen the version specifier to just '>='? Latest rubocop  is 0.58.2 and includes some useful cops.
Ditto for rubycop-rspec. Current version 1.28.0.
I Coud not figure out for a long time why my newer system rubocop was not being used when developing a new module... until I found this in my dependencies.

It's pinned because that's the last version that allows Ruby 2.1 style checks. Because that's the version that's included in Puppet 4, we must pin it.

Thanks for the clarification. I was wondering if there was a dependency I was not recognizing. I just found this in another module too.
Could another version be specified if RUBY_VERSION >= '2.4'?
I'm new at how Ruby & Gems are specified, and from what I read the :require => false should prevent it from being treated as a requirement, but it would still get installed. That seems odd to me.
I'm using a Gemfile.local to install my preferred version now, but it still complains about dependency conflicts from another module. Perhaps I'm going about this the wrong way.

authors: cdchase ekohl

repo: voxpupuli/puppet-mongodb


text:
Allow relative paths for $log_file

0c851ce3cd8d44256a3577dd81eaa88614095ac4 changed $log_dir for SCL deployments. However, $log_file was still absolute. That caused it to log to a non-existing directory.
This patch makes $log_file accept a relative path. If a relative path is specified, $log_dir will be prepended. Absolute paths are still used directly which keeps API compatibility.

Hopefully now with green tests.

Hopefully now with green tests.

repo: voxpupuli/puppet-redis


text:
Emtpy hiera files throw puppet 4 warnings

Following from a recent commit, remove the remaining empty yaml files

Thanks!

authors: benohara ekohl

repo: voxpupuli/puppet-yum


text:
iOS AssemblyName gets messed up under certain circumstances

This error causes

build runs fine
dsym zipping will fail

Log output
/app.iOS/bin/iPhone/Debug//app_iOSapp.iOS.app.dSYM.zip /app.iOS/bin/iPhone/Debug//app_iOSapp.iOS.app.dSYM
[18:28:27]	[Step 5/6] [18:28:27]: ▸ zip warning: name not matched: /app.iOS/bin/iPhone/Debug//app_iOSapp.iOS.app.dSYM
[18:28:27]	[Step 5/6] [18:28:27]: ▸ zip error: Nothing to do! (try: zip -r /app.iOS/bin/iPhone/Debug//app_iOSapp.iOS.app.dSYM.zip . -i /app.iOS/bin/iPhone/Debug//app_iOSapp.iOS.app.dSYM)

Notice: through #14 the zipping should no longer fail, but the outcome is not as expected.

Stale issue, error not happened again.

repo: voydz/souyuz


text:
How to change the color of this part in visual section

Anybody know what is the styling needed in the configuration to affect this part of the visual select mode:

Many thanks!

This is an issue tracker.

@vlrevolution you can post your question here: https://github.com/vscode-neovim/vscode-neovim/discussions

authors: Jendker justinmk vlrevolution

repo: vscode-neovim/vscode-neovim


text:
[Feature Request]: Can you add a refiner node?

There might be some stuff missing from your implementation of Kandinsky 2.2 or I'm not understanding entirely how to use it, but there's a refiner model for Kandinsky as well. My best guess is that it is similar to how SDXL works, with what we've been using as the first pass, and the refiner as a second pass.
https://huggingface.co/kandinsky-community/kandinsky-2-2-decoder-refiner

I’ll have a look. I think I saw it, but the card was empty and I wasn’t sure how to use it.

Just in case, I created HF discussion to figure out if the authors plan to fill out description card: https://huggingface.co/kandinsky-community/kandinsky-2-2-decoder-refiner/discussions/1

authors: Koitenshin vsevolod-oparin


text:
Bootstrap Webhook support

Summary

Adds support for building basic Webhooks for a resource. It works when installed with make package-install in local kind cluster.
The crossplane packaging system is actually the one creating and configuring the webhook when installed via package. It creates and mounts the certificates for authentication by kubernetes.

Checklist

[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[x] Update tests.

review notes: To test it out, try make package-install and then see if the webhook server logs something when installing the sample with make install-samples.

repo: vshn/appcat-service-postgresql


text:
Add vshn postgres

This PR adds crossplane support for stackgres operator.
Added composite and composition
Tested in my local cluster

Checklist

[x] PR contains a single logical change (to build a better changelog).
[x] Update the documentation.
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.

One point I'm not sure if it was looked at:

The customer should not have any access to the namespace kubernetes resources

I'm fine with moving that to a new story if it's too much for the context of this story.

authors: Kidswiss zugao

repo: vshn/component-appcat


text:
Descenders don't show up

The descenders of Bold text don't show up.
Font-settings of the app have not been changed.
MacOSX 10.11.6. Poedit 2.2.3 (5738)
(see attached file)

Thanks for reporting! Will be fixed in 2.2.4.

I know it's not essential, but I want to inform you … The descenders in the green button still don't show. And the green button itself doesn't look "complete" (upper corners are rounded, lower ones are actually missing).
MacOSX 10.11.6. Poedit 2.2.4 (5785)

Thanks :( I addressed the systematic sizing issue that could be causing it. Part of the trouble is that I couldn't reproduce it in your language at all, but could in Czech partially.
This may be specific to you rather old OS version. From the screenshot I gather this is not a retina display, right?
Reopening, I'll try to figure it out. In the meantime, you know what workaround to use to not have to look at that misrendered green box ;)

The explanation turns out to be very simple: I accidentally forgot to merge Poedit Pro's 36d6256 counterpart. Will be fully fixed in 2.2.5.
🤦♂

authors: milotype vslavik

repo: vslavik/poedit


text:
Add impeller

Classify Impeller as Data Structure, close #1840

          1 Warning

:warning:
Found 4 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

876
301
https://github.com/terflogag/FacebookImagePicker redirects tohttps://github.com/floriangbh/FacebookImagePicker

913
Error
https://pspdfkit.com/  Cannot assign requested address - connect(2) for "pspdfkit.com" port 443

1376
301
https://github.com/SwiftOnEdge/Edge redirects tohttps://github.com/skylab-inc/Edge

2404
301
https://github.com/terflogag/OpenSourceController redirects tohttps://github.com/floriangbh/OpenSourceController

  Generated by :no_entry_sign: Danger

Could you have only one project per pull request, thank u

authors: danger-awesome-ios dkhamsing lukecrum

repo: vsouza/awesome-ios


text:
Chore: Updates Envelop from v2 to v3

What's the purpose of this pull request?
Update the Envelop to v3.
How it works?
Added some comments on this PR linking to specific parts of the Envelop doc.
How to test it?
Run the project and check if it continues working the same.
Starters Deploy Preview
Here is the preview of the starter store: https://sfj-8a111d3--starter.preview.vtex.app/ (PR).
I've also updated the playground store to test in a store with some level of customization (API extension for example): https://sfj-e16ec36--playground.preview.vtex.app/ (PR).
References

Envelop Migration doc
Jira task

just out of curiosity: Since this task originated from the cache study, do you noticed any specific improvements that stand out after updating the Envelop framework from v2 to v3?

Not yet, Fan 😞 on my tests I didn't find any significant changes. Hopefully when updating to v5 and tweaking the plugins we'll get some improvement. Nevertheless, it's important to update it since we were so out of date 😅

repo: vtex/faststore


text:
Accessibility: Checklist

Issue that gathers information to build the checklist page.
https://vue-a11y.com/project/vue-a11y-checklist.html

I'm not sure how vue-specific we want this to be, but I think vox media's checklist provides an excellent jumping of point.
Their engineer checklist includes:

[ ]  Use the correct HTML element for your content
[ ]  Support keyboard navigation
[ ]  Understand and use HTML landmarks
[ ]  Write good alt text for your images
[ ]  Design focus states to help users navigate and understand where they are
[ ]  Help users understand inputs, and help them avoid and correct mistakes
[ ]  Use ARIA attributes when applicable
[ ]  Make links descriptive
[ ]  Avoid images and iconography in pseudo-elements
[ ]  Make SVGs accessible to assistive technology
[ ]  Hide decorative elements from screen readers
[ ]  Create alternate routes for users to access information
[ ]  Links should be visually identifiable and have clear :focus and :active states

Perfect @georgialoper
We can try to list specific items to solve accessibility flaws that are common when developing JavaScript applications (focused on Vue.js) and merge with important items from other more comprehensive checklists.
Would you like to build this with us?

@ktquez I'm interested in contributing where I can.
I'm having trouble running the project locally. I'm getting error @vuepress/plugin-blog apply ready failed. RangeError: Invalid array length at getIntervallers when running npm run dev, do I need any keys to get started?

@georgialoper Awesome, we are happy with your initiative.
I think it is a bug in the plugin, I will do a test and see if any version is causing this and give you feedback.

@georgialoper
I updated the README and the .env.example
Before running npm run dev you make cp .env.example .env.

authors: georgialoper ktquez


text:
Roadmap

[ ] Draggable
[ ] Resizable
[ ] Themes for other UI frameworks like BootstrapVue, Vuetify, ElementUI, etc.

Move this to projects Roadmap.

Hello @hunterliu1003,
is it still planned to make the modal draggable and resizable?
Thank you very much.

repo: vue-final/vue-final-modal


text:
grantOfflineAccess

is there a way to call grantOfflineAccess to get the authorization code?

@altoP, it doesn't look like we're returning the authorization code at the moment, but you should be able to retrieve it via getOfflineAccessCode(), i.e.
this.$gapi.grantOfflineAccess().then(() => {
   console.log(this.$gapi.getOfflineAccessCode());
});

@altoP, v1.0 introduces several improvements on this front:

grantOfflineAccess is now resolved with the authorization code
The authorization code is now persisted in local storage and can be retrieved via getOfflineAccessCode

authors: altoP namoscato

repo: vue-gapi/vue-gapi


text:
演示站点视乎出现了些问题

演示站点视乎出现了些问题

fix

repo: vueComponent/ant-design-vue-pro


text:
    Add missing closing parenthesis to the Vue ESM builds' descriptions (…

New updates on head repo.
https://github.com/vuejs/docs/commit/ce2c8dd5970f5cc93182285e392ff4a8dd439543

resolved 3b0bdf9cca98234f775d9d8a15940cf366f5fd72


text:
v2.0 translation

Hi guys. I've started to work on Russian translation for 2.0 documentation at https://github.com/gbezyuk/ru.vuejs.org
If you work on the same issue, let's sync our efforts.

@gbezyuk  sorry for a long response time.
Unfortunately, this project got out of the main priority scope for me. And it looks like no other members activity on 2.0 docs translation. So literally there are no efforts here to sync with.
I propose to add you as an Admin for this organization vuejs-ru, so you can manage it, add your translation fork (and maybe translations for other Vue repos like router etc.) and https://github.com/vuejs-ru/Discussion (that is rather popular russian-speaking Gitter chanell).

I have remembered about this thanks to flame in comments here https://vk.com/wall-30666517_1434369
ha-ha :)

Finally! =) Sure, add me! Thanx!

Done

Grac!

authors: aios gbezyuk iJackUA


text:
Hot-reload works only on production environment

Hi everybody,
I'm trying hot-reload with chrome and the only way to success is with the production flag enabled on my .npmrc file
I'm running the build command npm run dev
Thanks for all your great job!

Sounds weird. OS, Node, npm versions?

I'm working with:
OS: Ubuntu 14.04
Node: 5.9.1
npm: 3.6.0
vue-cli: 1.4.0

@miquelangel-castillo Changing values in data don't trigger a reload because those values are only the initial state for the component. When a component has already been initialized, changing that initial state has no effect. One important difference between hot reloads and a refresh are that reloads maintain the current state of components.
If you add method or computed functions and change those, does the hot reloading work then?

I thought this was clear enough?
Also, in production you are seeing a full reload, not a hot reload. The hot reload preserves your current application state.

@chrisvfritz I tried with methods and computed properties and hot-reload works fine as expected :))
@yyx990803 thanks for the explanation, it has become very clear to me
Thanks so much and congratulations for this great project

@miquelangel-castillo Glad to hear it! And glad you're enjoying Vue. 😀

Updating node and npm also fixed my problem. The vue dev tools chrome extension rocks! thanks

authors: andrewhu chrisvfritz miquelangel-castillo yyx990803

repo: vuejs-templates/webpack


text:
修改了过滤器部分的两个字

看看妥不妥？

?

原文的意思是：以“管道符”（来）指示（这是过滤器）

没问题那就不改

authors: jinlong yanxyz


text:
Uncaught (in promise) Maximum recursive updates exceeded in component

Vue version
3.4.15
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-mgmzpd?file=src%2Fcomponents%2FHome.vue
Steps to reproduce
just need add or remove console.log in Home.vue,  and you will get the error
https://github.com/vuejs/core/assets/4457572/90b37e16-1d4a-4bdb-955f-60b5e72762b5
What is expected?
Find the source of the error and fix it
What is actually happening?
in vue 3.4.15，vue-router 4.2.5.
the code with v-for and ref ,for example

      {{ item }}

and than you change any  script  will trigger an error Uncaught (in promise) Maximum recursive updates exceeded in component <RouterView>
for example add the console.log('========');
by the way, in in vue 3.4.14 ，there won't be this problem
System Info
Need to install the following packages:
envinfo@7.11.0
y

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.14.0 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.4.15 => 3.4.15

Any additional comments?
No response

I don't think this is a core problem with vue because the errors do not occur when I reload the page. Perhaps you can submit an issue in vue-router.

yes,  the errors do not occur when reload the page, it occur when you add or delect the script (console.log) to trigger hmr

I don't think this is a core problem with vue because the errors do not occur when I reload the page. Perhaps you can submit an issue in vue-router.

yes,  the errors do not occur when reload the page, it occur when you add or delect the script (console.log) to trigger hmr

I just encountered this same issue, and after playing with it for a bit, I believe this problem was introduced in version 3.4.6.  I cannot reproduce the issue with vue 3.4.5, but I can with 3.4.6.

This looks like a duplicate of #10210

I just tried 3.4.16 and I'm getting the same "Maximum recursive updates eceeded".

repo: vuejs/core


text:
Test and support indented pug templates

Issue (unfortunately closed already): https://github.com/vuejs/core/issues/3231
Previous PR: https://github.com/vuejs/core/pull/3842
Reproduction: https://github.com/rudolfbyker/vue-pug-indent-reproduction

What does "on hold" mean? Do you need anything else from my side?


text:
when I use devtools with my project， it will be Extremely slow！

Version
6.1.4
Browser and OS info
'5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.0.0 Safari/537.36'
Steps to reproduce
I don't know what happened， but when I switch to browser developer tools [vue] then it become stuck and I can do nothing with my page !
can't click my page and click the content of devtool !
After a period of time， when I close the developer tools，my project becomes normal.
my project uses vue3 + pinia.
What is expected?
Maybe the tool will not make the pages freeze
What is actually happening?
so stucked!

Duplicate of #1875

authors: Akryum yuangegena

repo: vuejs/devtools


text:
typescript-language-features not work

Version Infos
os：macos m3pro v14.3.1
vscode：v1.87.2
typescript-language-features： v1.0.0
Vue - Official：v2.0.7
[Error]: The JS/TS language service immediately crashed 5 times. The service will not be restarted. This may be caused by a plugin contributed by one of these extensions: Vue.volar. Please try disabling these extensions before filing an issue against VS Code.

Could be related to https://github.com/vuejs/language-tools/issues/4130

Duplicate of #4130

authors: johnsoncodehk zernonia zjtakato

repo: vuejs/language-tools


text:
Clicking a router link results in a replaceState and a pushState

Version
4.0.8
Reproduction link
https://jsfiddle.net/gob8sL0q/
Steps to reproduce

Open the JSFiddle.
Click the links.
Check the console.

What is expected?
Only pushState should be called (as far as I know).
What is actually happening?
replaceState is called with the current URL, followed by pushState with the new URL.

I ran into this while trying to integrate Google Tag Manager and Google Analytics. GTM has a History Change trigger, and it is triggering twice for each navigation because of this issue.
While I could probably filter out the replaceState calls, this should not be necessary if I'm understanding correctly, and just makes GTM more difficult to work with.

Hi @glen-84
The replaceState is called here and the pushState is called here.
I think the replaceState is to store the following data to the current state.
{
  forward: to,
  scroll: computeScrollPosition(),
}

I see, then I suppose that this is unlikely to change. I'll go with plan B, and filter out the replaceState calls in GTM.
Thanks for your help.

I see, then I suppose that this is unlikely to change. I'll go with plan B, and filter out the replaceState calls in GTM.
Thanks for your help.

@glen-84 Thank you for this situation. We had the exact same issue and were dumbfound for hours. Filtering out the replaceState was indeed a great "solution". Although not the best one, it seems to avoid this vue-router bug
Did you in the meantime came across another way to solve this?

Did you in the meantime came across another way to solve this?

@cedricbloem I have not. I used Some History Changes (History Source = pushState) in GTM, instead of All History Changes.

authors: PeterAlfredLee cedricbloem glen-84

repo: vuejs/router


text:
Page auto-refreshing doesn't work in Brave

Version
3.4.1
Reproduction link
https://github.com/SilencerWeb/gsap-training
Environment info
  System:
    OS: macOS 10.14.2
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  Binaries:
    Node: 11.7.0 - /usr/local/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.8.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 72.0.3626.119
    Firefox: Not Found
    Safari: 12.0.2
  npmPackages:
    @ant-design/icons-vue:  1.0.1
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0-beta.2
    @vue/babel-plugin-transform-vue-jsx:  1.0.0-beta.2
    @vue/babel-preset-app:  3.4.1
    @vue/babel-preset-jsx:  1.0.0-beta.2
    @vue/babel-sugar-functional-vue:  1.0.0-beta.2
    @vue/babel-sugar-inject-h:  1.0.0-beta.2
    @vue/babel-sugar-v-model:  1.0.0-beta.2
    @vue/babel-sugar-v-on:  1.0.0-beta.2
    @vue/cli-overlay:  3.4.1
    @vue/cli-plugin-babel: ^3.4.0 => 3.4.1
    @vue/cli-plugin-eslint: ^3.4.0 => 3.4.1
    @vue/cli-service: ^3.4.0 => 3.4.1
    @vue/cli-shared-utils:  3.4.1
    @vue/component-compiler-utils:  2.6.0
    @vue/preload-webpack-plugin:  1.1.0
    @vue/web-component-wrapper:  1.2.0
    ant-design-vue: ^1.3.5 => 1.3.5
    babel-helper-vue-jsx-merge-props:  2.0.3
    eslint-plugin-vue: ^5.0.0 => 5.2.2
    vue: ^2.6.6 => 2.6.7
    vue-eslint-parser:  5.0.0
    vue-hot-reload-api:  2.3.3
    vue-loader: ^15.6.4 => 15.6.4
    vue-ref:  1.0.4
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.5.21 => 2.6.7
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
Just clone it, install dependencies, run it, open Brave and try to change any file.
What is expected?
Page auto-refreshing is expected after a file change
What is actually happening?
No page auto-refreshing. It works ok in Chrome.

In case you are referring to hot Module Reloading, it works fine for me on Brave (Mac) with your repository (once I fixed the missing module error).

@LinusBorg what module error?

The one from the missing HelloWorld component. You just fixed it with this commit: https://github.com/SilencerWeb/gsap-training/commit/1e3fc8358c002b52e170d28e011b10f68e2cc5fe

@LinusBorg it still doesn't work :(
It doesn't work in another project too. Any clues why it could be like that?

Hard to say, as I can't reproduce it.

@LinusBorg Same thing in Safari. Even more, if you reload the page, no changes will arrive. Same thing on iOS in any browser.

authors: LinusBorg SilencerWeb

repo: vuejs/vue-cli


text:
Yarn can't run the dev command

Hey.
Having issues using yarn on this
yarn run v0.15.1
$ "node build/dev-server.js"
sh: node build/dev-server.js: No such file or directory
error Command failed with exit code 127.
info Visit http://yarnpkg.com/en/docs/cli/run for documentation about this command.

But it works perfectly when using npm.
npm -v is 5.5.1
node -v is 9.0.0
yarn -v is 0.15.1
vue -V is 2.9.1

I needed to upgrade yarn, now running v1.2.1.
See here: https://github.com/yarnpkg/yarn/issues/1139
Sorry for the unnecessary issue - but hopes it helps someone in the future.

Thanks for posting the solution back 🙂

authors: nothingrandom posva


text:
docs: mention the precedence of .vue & .ts(x) extensions

closes #4936
What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:

I didn't realize you made this to master instead of dev branch.

Yeah because the website is deployed from master

authors: pksunkara sodatea


text:
Selected component is not being highlighted enough

What problem does this feature solve?
I am having trouble finding my currently selected component in certain hierarchies that have lots of child components. The subtle " = $vm0" hint does not pop out enough when scrolling though the list using the scroll bar.

What does the proposed API look like?
Maybe inverting the color would help. White text on a green background. Or just a transparent green background to underline the selection.

The selected component should have an inverted background 🤔

Hm, this was in August. I just checked again, and $vm0 was now properly selected…

authors: Akryum spaceemotion

repo: vuejs/vue-devtools