text:
Ability to decrement input value with a different step size

I've added a separate 'downStep' property to allow setting a different step size when decrementing the value. The need for this arose as the project I'm working on requires the "price" input component to have different step sizes given the range of values (See below)
From | To         | Step Size
0    | 0.9999     |  0.0001
1    | 9.99       |  0.01
10   | 99.9       |  0.1
100  | infinity   |  1.0

So for e.g. if component is showing value 10 pressing the UP key should take the value to 10.1 (step size 0.1) but pressing DOWN key should go to 9.99 (step size 0.01).

Thank you  for this. Looks like a good addition to the component and the code changes are well written.
That being said, I think I have different architectural ideas of achieving the same thing but before I share them, could you explain how are you using this? I guess you have a piece of logic externally somewhere that given the current value will provide the next step and downStep prop values?

That's exactly right. There's a code in the back-end that picks step and downStep given a price point and sends it to the front-end. Every time user changes the price in the input component we send that value to the BE to do the step picking.
BE has some business logic to evaluate which price range is applicable for the given context and price point and it picks step and downStep property based on that logic. So when the price is exactly within the range both values will be equal. Only in case when the price is moving from one range to the other, there will be a difference in their values.

OK then. Thanks for sharing. I think having  a backend involved in such a discrete front-end "event" makes your case unique.
I had plans to make some props like min, max, step and precision more dynamic than they are now because in rare cases, having to re-render to pass new props is simply not good enough. In fact I already did that for precision at https://github.com/vlad-ignatov/react-numeric-input/commit/4c7280825a496a3fa0ca7591be494d09962aebe5.  The idea is to simply allow for these props to also be functions and call them if they are.
This could also solve your case if you didn't have to involve the backend (which also makes that interaction asynchronous). Having a step function could look like
<NumericInput  step={(component, direction) => {
    if (component.state.value == 10) {
        return direction == "up" ? 0.1 : 0.01;
    }
    // other custom conditions...

    // default
    return 1;
}}/>

In my opinion those prop functions must not be async. Otherwise that would significantly increase to complexity of the entire component. For people like you, who are sending requests to a back-end service to determine the value, re-rendering with different props will continue to be the better solution.
A think I will merge your PR soon just to cover those rare cases and then add the "function" option on top of it. Frankly, if I were you I would consider fetching a set of rules from the backend once and then building a step function that uses those rules (assuming that it is possible) so that people can use the component in real time.

I agree, Making these props dynamic is a better solution. I think you can decline my PR in that case.
The rules of range picking are still bit too complicated to bring into the FE. I think I still would want to keep them in the BE.  So after your change I'll still get the two step values from BE once the value in the component is changed. I'll then use the step function to pick the right step value based on the direction.
Any ideas when you'll be able to release that change.
Thanks,

Well, I only get to work on this for a few hour per week now but the code is ready. I just need to do some more testing, update the readme and fix a few other things so I guess it will take about a week.

got it. I'll wait for the release then. You can decline this PR.

2.2.0 is now on NPM. I hope you can confirm if that works for you.

I've tested it. It works like a charm :). Thanks.

Thank you!

authors: sbhaleka vlad-ignatov

repo: vlad-ignatov/react-numeric-input


text:
Unable to run build.vsh when building from source

System Information
V doctor
OS: macos, macOS, 11.5.1, 20G80
Processor: 8 cpus, 64bit, little endian, Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
CC version: Apple clang version 12.0.5 (clang-1205.0.22.11)

getwd: /Users/ali/tools/vls
vmodules: /Users/ali/.vmodules
vroot: /usr/local/Cellar/vlang/0.2.4/libexec
vexe: /usr/local/Cellar/vlang/0.2.4/libexec/v
vexe mtime: 2021-08-30 19:25:14
is vroot writable: true
is vmodules writable: true
V full version: V 0.2.4 b72a2de

Git version: git version 2.30.1 (Apple Git-130)
Git vroot status: Error: fatal: bad revision 'HEAD'
.git/config present: true
thirdparty/tcc: N/A

VLS info
n/a

Problem Description
Unable to build:

Expected Output
It builds
Actual Output
analyzer/symbol_registration.v:173:84: error: `void_sym` evaluated but not used
  171 | fn (mut sr SymbolAnalyzer) struct_field_decl(field_access SymbolAccess, field_decl_node C.TSNode) ?&Symbol {
  172 |     field_type_node := field_decl_node.child_by_field_name('type') ?
  173 |     field_sym := sr.store.find_symbol_by_type_node(field_type_node, sr.src_text) or { void_sym }
      |                                                                                ~~~~~~~~
  174 |     field_name_node := field_decl_node.child_by_field_name('name') or {
  175 |         // struct embedding
Failed building VLS

Steps to Reproduce
Clone e4ae12f117e7241a61db6a0c11e184d6ca0fe6b3 & run v run build.vsh clang
Last Recorded LSP Requests
n/a

@alii Based on the V version, your version has been outdated. Please use the latest version of V and try again.

Ahh I apologise, that should've been the first thing I should have checked! I installed the latest from home brew with the assumption it would be up to date 😅 thank you!! sorry for wasting your time

source: gharchive/issue

authors: alii nedpals

repo: vlang/vls

license: MIT

license_type: permissive

license_source: github-api


text:
Enhancement - add Raspberry Pi Pico microcontroller support

Hi,
Any plans to support the new Raspberry PI Pico microcontroller board?

I don't have this device, so I cannot test it at this point. Contributions adding Raspberry Pi Pico support to the plugin are welcome. The plugin supports several devices and the code for supporting a new one is relatively easy to add.

I don't have this device, so I cannot test it at this point. Contributions adding Raspberry Pi Pico support to the plugin are welcome. The plugin supports several devices and the code for supporting a new one is relatively easy to add.

I just received my Raspberry Pi Pico board a few minutes ago, but I'm new to this.  Is there a doc somewhere that demonstrates how to add a new device?  Or a PR that added a different device that I can use as an example?

I just received my Raspberry Pi Pico board a few minutes ago, but I'm new to this.  Is there a doc somewhere that demonstrates how to add a new device?  Or a PR that added a different device that I can use as an example?

Hah - I just found this: https://github.com/vlasovskikh/intellij-micropython/pull/114
I'll see if I can knock up something similar.

Hah - I just found this: https://github.com/vlasovskikh/intellij-micropython/pull/114
I'll see if I can knock up something similar.

It is working quite ok with the "Pyboard" device. The only exception is the soft reset: For whatever reason this is not working on my Mac. It is sending the right commands (Ctrl-C, Ctrl-D), but the board does not perform the reset.
If I connect to the board after having flashed through IDEA, with e.g. screen, it immediately runs the (pending?) reset. Maybe it's just a timing issue, e.g. disconnecting too quickly.
To be clear: I am using IDEA with Python and MicroPython plugins, not PyCharm.

It is working quite ok with the "Pyboard" device. The only exception is the soft reset: For whatever reason this is not working on my Mac. It is sending the right commands (Ctrl-C, Ctrl-D), but the board does not perform the reset.
If I connect to the board after having flashed through IDEA, with e.g. screen, it immediately runs the (pending?) reset. Maybe it's just a timing issue, e.g. disconnecting too quickly.
To be clear: I am using IDEA with Python and MicroPython plugins, not PyCharm.

I'm not familiar enough with Python to help code it, but it would be great to have Pi pico support in PyCharm :) I will try to test it using the "Pyboard" device re: @tinue

I don't have this device, so I cannot test it at this point. Contributions adding Raspberry Pi Pico support to the plugin are welcome. The plugin supports several devices and the code for supporting a new one is relatively easy to add.

@vlasovskikh would mailing you one of these devices be helpful for this? I have a spare and they are very inexpensive in my area

I live in New Jersey, USA. I also have a known good Pico board I could mail you. Let me know.

If someone like timsavage does a pull request, what does it take to get that merged in - as in what is the process/timeline?
Does it need other people to fork the plugin and pull in the pull request to do testing?

Raspberry Pi Pico support is coming to the MicroPython plugin for PyCharm v1.2:

Ability to flush your files to RPi Pico via MicroPython run configurations
Basic type hints (please contribute more of them via PRs!)

🙏 Thank you @timsavage for contributing code for Raspberry Pi Pico support! Thanks @lensvol for reviewing the PR!

authors: cakoronkowski lwr20 mlewus smith9 tinue vlasovskikh

repo: vlasovskikh/intellij-micropython

license_source: bigquery


text:
[Bug]: LLaMA3.2 90B Vision Model and Pipeline Parallelism - Error

Your current environment

The output of `python collect_env.py`
Your output of `python collect_env.py` here

Model Input Dumps
No response
🐛 Describe the bug
I'm trying to load LLaMA 3.2 90B Vision model across two nodes. Each node has 2 A100 80GB GPUs. I'm using tensor parallel size=1 and pipeline parallel size = 4. I get the following not implemented error.
I'm using the latest published version of vLLM (version: 0.6.2). Any help to resolve this would be greatly received. Thank you.
raise NotImplementedError(

NotImplementedError: Pipeline parallelism is only supported for the following  architectures: ['AquilaForCausalLM', 'AquilaModel', 'DeepseekV2ForCausalLM', 'GPT2LMHeadModel', 'InternLM2ForCausalLM', 'InternLMForCausalLM', 'InternVLChatModel', 'JAISLMHeadModel', 'LlamaForCausalLM', 'LLaMAForCausalLM', 'MistralForCausalLM', 'MixtralForCausalLM', 'NemotronForCausalLM', 'Phi3ForCausalLM', 'Qwen2ForCausalLM', 'Qwen2MoeForCausalLM', 'QWenLMHeadModel', 'Qwen2VLForConditionalGeneration'].
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.

Command that I'm using to load the model:
vllm serve meta-llama/Llama-3.2-90B-Vision-Instruct --enforce-eager --max-num-seqs 16 --tensor-parallel-size 4

Yeah, PP is not supported for most vision models yet.

repo: vllm-project/vllm


text:
The model to consider.
https://huggingface.co/nvidia/NV-Embed-v2
The closest model vllm already supports.
No response
What's your difficulty of supporting the model you want?
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.

Would be great if this was supported, this has be the top of the MTEB for some time!

authors: agm-eratosth warlockedward


text:
[BugFix] Don't start a Ray cluster when not using Ray

The logic to auto-select the distributed executor backend uses ray.util.get_current_placement_group() to check whether it's already running in a Ray placement group, but this function has a side effect of starting a Ray cluster if it's not already started.
The result is that a Ray cluster gets started even when defaulting to the multiprocessing distributed backend.

Could this PR establish multiprocessing as the default setting, unless there is an explicit selection of Ray for distributed inference?

source: gharchive/pull-request

authors: EgorovM njhill


text:
fix(server): fix garbled characters stream output

The reason is: The word which takes up more than one token ids was sent out before it was fully generated. When a new token is generated, and the word length remains unchanged, it indicates that the word at the current position occupies multiple tokens.
To address this issue, I cached the previous word and modified the output from the current word to the previous word. This allows me to recognize any garbled word and wait for the cached word to be fully generated before outputting it.
This code change works on my WizardCoder model, but haven't test other model with an insufficient cjk vocabulary.
Test case in stream mode: 翻译：mouse
Generate output: 鼠标  where 鼠 takes up two tokens.
Hope it's helpful for people using CJK languages..：）

@zhuohan123 i think this PR is ready for review. No more changes by me.

@esmeetu thanks a lot. Your code correction has solved my problem. However, there is a minor issue: garbled characters have been restored to the correct Chinese characters, but the space character that was originally in front of this Chinese character is now missing. I manually added a space character and it appears to be normal, but it may only be suitable for my particular scenario. Could you please help me check if you have the same problem on your end? Thank you.

HI @esmeetu @zhuohan123
May I ask when this pr is expected to be merged?  We have this problem now. thank you

@zhuohan123 Yes, I checked #984, it is indeed the issue of missing a space after the dot. This was my problem, and I resolved it by adding a space. However, I hope this issue can be fixed and merged. Thank you.

@leoxing99

hello, I also ran into a problem with missing Spaces,Can you tell me how you solved it,thanks

It seems that this problem has been solved in PR #984 and #1044.
Is there any difference between this PR and PRs mentioned above?

@HermitSun Yes. I will close this PR.

authors: HermitSun allenhaozi esmeetu jeurtr leoxing99


text:
[Misc] Use marlin kernel when cutlass fp8 is not support

Only relying on the compute capability is not enough to determine whether we can use fp8 activation. We can re-use the cutlass_fp8_supported function that also takes cuda version into consideration.

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

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

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

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

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

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

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

We have the option to fall back to torch._scaled_mm when cutlass is not supported (this is for Ada Lovelace -- which we are about to turn on for cutlass)

So does it mean that this logic will be factored? Currently, it will not automatically fallback to another fp8 compuation method, resulting
void cutlass::arch::Mma<cutlass::gemm::GemmShape<16, 8, 32>, 32, cutlass::float_e4m3_t, cutlass::layout::RowMajor, cutlass::float_e4m3_t, cutlass::layout::ColumnMajor, float, cutlass::layout::RowMajor, Operator_>::operator()(cutlass::Array<float, 4, true> &, const cutlass::Array<cutlass::float_e4m3_t, 16, false> &, const cutlass::Array<cutlass::float_e4m3_t, 8, false> &, const cutlass::Array<float, 4, true> &) const [with Operator_ = cutlass::arch::OpMultiplyAdd] not implemented

Oh I see, in line 149, we should not hardcode cutlass_fp8_supported=True

Oh, thanks. I have updated the code accordingly.

Thanks for the contribution!


text:
Update documentation

add missing linters
emphasize that new test cases should be added as part of new
contributions and include more details about the different categories
of tests we support; this is related to
https://github.com/vmware-tanzu/antrea/issues/989

Thanks for the reviews, I addressed all comments

/skip-all

repo: vmware-tanzu/antrea


text:
Add -s as shorthand for --source-image

Pull request

What this PR does / why we need it
Remove -s as shorthand for --service-account and add it for --source-image
Which issue(s) this PR fixes

Fixes #126
Describe testing done for PR

Created workload in local cluster using -s and passing a source image after flag

Inside pet-clinic folder (https://github.com/spring-projects/spring-petclinic)

$ tanzu apps workload create petclinic-local --local-path . -s gcr.io/tanzu-framework-playground/petclinic-local --type web
Note: use your gcr (or whichever registry) repository to publish source

Additional information or special notes for your reviewer

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

$ tanzu apps workload get petclinic-local

repo: vmware-tanzu/apps-cli-plugin


text:
remove conditions column from inspect/diff since it's misleadingly colored for resources like HPA which always have a false condition

What steps did you take:
Namespace  test
Name       test-71295
Kind       HorizontalPodAutoscaler
Status     conditions:
           - lastTransitionTime: "2021-06-24T11:56:39Z"
             message: recommended size matches current size
             reason: ReadyForNewScale
             status: "True"
             type: AbleToScale
           - lastTransitionTime: "2021-06-24T12:41:27Z"
             message: the HPA was able to successfully calculate a replica count from cpu resource
               utilization (percentage of request)
             reason: ValidMetricFound
             status: "True"
             type: ScalingActive
           - lastTransitionTime: "2021-06-24T11:58:24Z"
             message: the desired count is within the acceptable range
             reason: DesiredWithinRange
             status: "False"
             type: ScalingLimited
           currentMetrics:
           - resource:
               current:
                 averageUtilization: 3
                 averageValue: 16m
               name: cpu
             type: Resource
           currentReplicas: 1
           desiredReplicas: 1
           lastScaleTime: "2021-06-24T12:45:06Z"

Namespace           Name                              Kind                     Owner    Conds.  Rs  Ri  Age
test  				test-71295                        HorizontalPodAutoscaler  kapp     2/3 t   ok  -   52m

What happened:
ScalingLimited: false is interpreted as an error.
What did you expect:
ScalingLimited indicates that autoscaling is not allowed because a maximum or minimum replica count was reached.
A True condition indicates that you need to raise or lower the minimum or maximum replica count in order to scale.
A False condition indicates that the requested scaling is allowed.
Source: https://docs.openshift.com/container-platform/3.9/dev_guide/pod_autoscaling.html
Environment:

kapp version (use kapp --version): 0.37.0
OS (e.g. from /etc/os-release): Ubuntu
Kubernetes version (use kubectl version): 1.19.4

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.

@StarpTech yeah, conditions coloring is a bit misleading. i wonder if we should remove coloring or may be even remove entire column -- ive not found myself using it at all. wdyt? (since conditions are very much resource specific there isnt a good pattern to follow here).

I mean if we can't determine if a condition is successful we should remove it. Otherwise, fix it. I think the information that all conditions are meet useful.

I mean if we can't determine if a condition is successful we should remove it.

unfortunately kubernetes doesnt provide any foundation for describing something being "successful" or not. conditions are more like facts. they are either True or False but that does not indicate whether something is succesful or not. so ultimately today in kubernetes, only human can decide whether something is "succesful".
ive added conds. column long time as more of an experiment in determining if it's going to be useful, but so far didnt have strong reaction from folks about it being actually useful.

Task
Remove conditions column from kapp inspect and during diff stage since it's misleadingly coloured for some of the resources like HPA which always have a false condition.
Currently this condition comes in the GUI output as mentioned in the description of the issue. So we need to remove it.
Code Changes

We have to make the changes in the places where we are feeding the data to the ui table in the print method. This is happening at 3 places.

https://github.com/vmware-tanzu/carvel-kapp/blob/6b191d2550397dc1007f5bcb2ef536d0358fdd3f/pkg/kapp/cmd/tools/inspect_tree_view.go#L25
https://github.com/vmware-tanzu/carvel-kapp/blob/6b191d2550397dc1007f5bcb2ef536d0358fdd3f/pkg/kapp/cmd/tools/inspect_view.go#L22
https://github.com/vmware-tanzu/carvel-kapp/blob/6b191d2550397dc1007f5bcb2ef536d0358fdd3f/pkg/kapp/clusterapply/changes_view.go#L35

Remove the Conds. header column and part of the row which populates this column.

After that, we have to fix the test cases to remove this column from the output. e.g.
https://github.com/vmware-tanzu/carvel-kapp/blob/6b191d2550397dc1007f5bcb2ef536d0358fdd3f/test/e2e/exists_ann_test.go#L58
Like this, it has been mentioned in various test cases across multiple files. We have to remove this column from all of them.

Available as part of kapp v0.47.0

authors: StarpTech cppforlife renuy rohitagg2020

repo: vmware-tanzu/carvel-kapp


text:
Should YAML nodes included through a merge operation << or anchor reference & have updated line numbers.

Consider this fragment:
seq1: &tag
 - 1
 - 2

seq2: *tag

Running this through ytt returns: (the expected parsed YAML)
seq1:
- 1
- 2
seq2:
- 1
- 2

As we've started to introduce schemas, a situation could arise where a legal value in one place becomes unacceptable in another. For example, consider a schema validation that says "all entries in seq2 are greater than 10". This is obviously a broken contract, so how can we alert the user that validation has failed?
One of the more useful debugging tools is showing line numbers so that the user knows where to go to correct the error. In this scenario, which line numbers should we show? The original "anchored" location? The location of the  "reference" point?
Should we treat the merge/anchor actions as if their operations had already completed?
Should we update other line numbers below the merged content?

@gcheadle-vmware and I reviewed and had the following thoughts on some questions:

In this scenario, which line numbers should we show? The original "anchored" location? The location of the "reference" point?

From an error message standpoint, it would be helpful to show the error at the line number of the reference, such as below:
Error: schema validation...

seq1: &tag
 - 1
 - 2

seq2: *tag (Schema validation: must be greater than 10)

However, it would be nice to have a way (e.g. possibly an option with ytt) to further visualize what the error is for the rendered reference, such as below:
Error: schema validation...

seq1:
- 1
- 2
seq2:
- 1 (Schema validation: must be greater than 10)
- 2 (Schema validation: must be greater than 10)

So by default, error line number is where the reference is located, but there could be a way to debug the error further. However, this may be difficult to actually implement, so it's possible that the further debugging might be too tough to put in place. We should look into it further though before deciding.

Should we treat the merge/anchor actions as if their operations had already completed? Should we update other line numbers below the merged content?

Based on the proposed UX for the error above, it's possible there may need to be a way to support both. One thing to consider is whether merge/anchor actions currently occur before schema validation takes place. This would help us understand whether it would be extra work to actually provide the UX like below:
Error: schema validation...

seq1:
- 1
- 2
seq2:
- 1 (Schema validation: must be greater than 10)
- 2 (Schema validation: must be greater than 10)

Considering a schema violation below the merged content, a user would want to see that error line number match the line number in his or her data values file. In the debugging case, a user would want the line numbers to change based on the rendered reference.

authors: StevenLocke danielhelfand

repo: vmware-tanzu/carvel-ytt


text:
Describe how to go from code to container

Describe the various ways that a developer may build container images for their code.

What are the various ways that I can build a container?

Docker
Tanzu Build Service
Kaniko

Provide an example of how these build tools may be used in a CI/CD pipeline
How can the build process be similar/same developer workflow?
Where does image scanning fit in?

A failed scan should break the build

Just to roundup some of the existing content if we'd like to reference/rewrite:
Docker

What are Containers?
Getting Started with Docker Containers on Kubernetes
Python Like a Pro: Building Docker Containers
From Commit to Container
Container Basics Workshop

Tanzu Build Service

What are Cloud Native Buildpacks?
Getting Started with the pack CLI
Getting Started with kpack
Spring Live: Build Images with Confidence and Ease with Cloud Native Buildpacks
Video: Getting Started with kpack

Kaniko
We don't have a ton on Kaniko directly, but some content does mention it

Getting Started with Tekton Part 2: Building a Container
TGIK 055: Building container with Kaniko

CI/CD

What is CI/CD?
Getting Started with ArgoCD on Kubernetes
Create a Continuous Integration Pipeline with GitLab and Kubernetes
Getting Started with Tekton Part 1: Hello World
Getting Started with Tekton Part 2: Building a Container
Getting Started with Concourse CI

Developer Workflow

Developing Locally for the Cloud
Kubernetes at Home: Local k8s Options](https://tanzu.vmware.com/developer/blog/kubernetes-at-home-local-k8s-options/)
Continuously Develop and Monitor an Express Application on Kubernetes with Bitnami, Skaffold and Octant

Image Scanning

Managing and Securing Container Images in a Registry
Best Practices for Securing and Hardening Container Images

authors: BrianMMcClain craigtracey

repo: vmware-tanzu/tanzu-dev-portal


text:
With Clarity v1.1.5, disabled attribute doesn't work with buttons under dropdown

Describe the bug
With Clarity v1.1.5, disabled attribute doesn't work with dropdown. This seems to be regression of https://github.com/vmware/clarity/pull/3417
<clr-dropdown>

          Click Me

        <clr-dropdown-menu *clrIfOpen>
          <button type="button" clrDropdownItem
        [disabled]="true" clrTooltipTrigger>Transfer </button>
        </clr-dropdown-menu>
      </clr-dropdown>

This used to work with all version <1.1.5 .
How to reproduce
Please check this stackblitz: https://stackblitz.com/edit/clarity-custom-theme-v1-0-6kylnz?file=src%2Fapp%2Fapp.component.html
Steps to reproduce the behavior:

Go to https://clarity-custom-theme-v1-0-6kylnz.stackblitz.io
Click on Click Me link which is a dropdown.

Expected behavior
Transfer button should be disabled.
Versions
App

Angular: 7.2
Clarity: 1.1.5

Additional notes
This may be similar : https://github.com/vmware/clarity/issues/3610

I confirm this is an issue - it looks like we promoted [disabled] to @Input on the clrDropdownItem so we can sync it with aria-disabled.
Unless we intentionally do not want to use disabled (I have some memories that disabled menu items should be focusable), this is broken.

authors: Jinnie jkjha

repo: vmware/clarity


text:
[NG] Change locale strings to nominative form

This PR changes the currently used CLDR data strings provided by Angular (month names and day names) from their genitive to nominative form.
The change is motivated by the current (incorrect) form of strings for the Polish locale. For example September is rendered as września while it should be wrzesień.
The change itself doesn't make a visible difference for most languages (i.e. English, German) but fixes the form for the Polish locale and possibly others.
Signed-off-by: Paweł Białaszczyk pawelbialaszczyk@gmail.com

Thanks for the contribution. This change makes sense to me. More info here: http://cldr.unicode.org/translation/date-time
Make sure that the correct forms are provided, especially for the months, and used in the patterns. That is, suppose that the language uses "Dezembro"  for December when standing alone (LLLL), but "Dezembru" when with a date (MMMM, when it means the nth day of that month)
It looks like when the month is used alone, we should use the Stand-Alone style.
@youdz can you please verify?

Thanks for approving this PR!
In the meantime I've also updated the implementation for abbreviated month names accordingly (forgot last time) and updated test cases. Let me know if more changes are needed.
I've forgot to sign off my last commits. Is it OK to rebase & force push them again?

Yes please rebase and force push into a single commit!


text:
Unable to power on Harbor VM in vSphere 6.5 env

Docker version: 1.12.3
Harbor: 0.4.5
OVA: harbor_0.4.5_beta_OVF10.ova
Got an error "The guest operating system 'other3xLinux64Guest' is not support." when powering on Harbor VM in vSphere 6.5 env.
NOTE:

Deploy harbor_0.4.1_beta.ova and the VM can power on in vSphere 6.5 env.

Add download link to UI with PR #1120

Fixed by changing the OS type.

Verified and passed on 0.5.0 rc2 build.

repo: vmware/harbor


text:
Unit test cannot handle docker push and pull cases

When push to registry, registry needs notification service to notify the cache to update. However, import service in package api will cause the cycle import problem.
Now the solution is to push images before test using a shell script.
Just mark for better solution.

This is no longer a problem as we are running E2E test to cover the push/pull scenarios

authors: reasonerjt wemeya


text:
can't pull the image vmware/harbor-ui:0.4.0

can't pull the image vmware/harbor-ui:0.4.0 with both 0.4.0 and latest tag:
$ docker pull vmware/harbor-ui:0.4.0
Pulling repository docker.io/vmware/harbor-ui
Tag 0.4.0 not found in repository docker.io/vmware/harbor-ui

$ docker pull vmware/harbor-ui
Using default tag: latest
Pulling repository docker.io/vmware/harbor-ui
Tag latest not found in repository docker.io/vmware/harbor-ui

I just try this cmd:
docker pull vmware/harbor-ui:0.4.0
0.4.0: Pulling from vmware/harbor-ui
3d8fd83d62fc: Pull complete
41cd2e7b78a9: Pull complete
5dd79dfedec8: Pull complete
b67df568cce6: Pull complete
82b72c257ae5: Pull complete
955390f4ea06: Pull complete
09c52f732891: Pull complete
63166e097589: Pull complete
Digest: sha256:7fbd44371b05244ad9c4ca23fba3929af8f124107a1d3c4728dba5196654e460
Status: Downloaded newer image for vmware/harbor-ui:0.4.0

Thanks, @yhua123.
It's my local setting problem. I can pull now.


text:
bug in utils/admission_control.rb

Module "VIM" is not undefined. Replace "VIM" by "RbVmomi::VIM" for the lines:
80/84/101/104/115/119/134/148/171/176/182/183/186/205/209/217/303/333/
For example:
L84:
@vm_folder ||= datacenter.vmFolder.traverse!(@vm_folder_path, VIM::Folder)
shouldn't that instead be:
@vm_folder ||= datacenter.vmFolder.traverse!(@vm_folder_path, RbVmomi::VIM::Folder)

Fixed by #66

authors: jrgarcia thanhngn

repo: vmware/rbvmomi

license: mit


text:
WIP: ci/cd: Migrate Tern from CircleCI to GH Actions

This commit translates the current lint/test suite from the circleci
yaml file to a new yaml file that will be run by GitHub actions.
Fixes #492
Signed-off-by: Rose Judge rjudge@vmware.com

Closing this PR as some experimentation is still needed. Will open a new one when it's ready for Tern's repository.

repo: vmware/tern


text:
vdk-oracle: ingestion

Support job_input.send_object_for_ingestion(method="oracle") or send_tabular_data_for_ingestion(method='oracle')
If user passes method=oracle then the data would be insert in pre-configured oracle instance
So what needs to be done:

Create IngestToOracle which implements IIngesterPlugin

50% of the implementation is already done actually - in this branch - https://github.com/vmware/versatile-data-kit/blob/feature/vdk-oracle/projects/vdk-plugins/vdk-oracle/src/vdk/plugin/oracle/ingest_to_oracle.py . So use it as a starting point

Create functional tests that have an ingestion job . Make sure to cover all possible data types (that is have columns in the dataset with all types include datetime and decimal!!!) . Example job could be https://github.com/vmware/versatile-data-kit/blob/main/projects/vdk-plugins/vdk-trino/tests/test_ingest_to_trino.py . The tests should cover both cases into non-existing table (so auto-create works) and existing table (so it's updated)

Load test (can be manual one time , ad-hoc, no need for special tools, even could be functional test). Record results in this ticket), Try to ingest 1,000,000 and 10 million rows, record time and memory consumption.

Update README.md to indicate ingestion support and example (short code snippet)

Load test result

Records
Time
Memory

100 000
10.4s
30Mb

1 000 000
60.76s
250Mb

10 000 000
568.58s
2.5GB

Note that the above is not the worst case scenario. The worst case scenario would be something like ingesting one million objects with the same schema, but randomized keys, e.g. one object would get a random number of keys from the schema. This will trigger batching of the ingestion queries based on the keysets. Ingestion rows with the same keyset are batched together. This increases the number of queries, so it should theoretically be slower.

authors: DeltaMichael antoniivanov

repo: vmware/versatile-data-kit


text:
Getting error from Server (Vsphere API)

Getting no response from server for Power Start and Stop requests

[ ] I am using the [latest SDK version]:6.7.1
[ ] This API is compatible with my vCenter version 6.7
[ ] Yes I have searched existing issues

Description
Vsphere API: VM Power Start/Stop requests are sending error in the response
Environment

SDK version: 6.7.1

Java version:1.8

vSphere version:6.7

Steps or code snippet to reproduce

Login to vsphere vcenter in api explorer
Get the vm id from VM request
POST /vcenter/vm/{vm}/power/start
Enter vm-id in the above request
Request starts running for more than 30 minutes
Server sends the Error: "error": "no response from server"
Same respose is observed for /vcenter/vm/{vm}/power/stop

Actual behavior
No response from the server, getting error after 15-30 minutes.
Error: "no response from server"
Expected behavior
Server should send the proper response
Note: I think above issue is happening because of the parameter invocationConfig either it is set as null or set as false

The issue seems to be from your server side, as you are getting 'no response from server' error.
Also I'm not able to reproduce these issue.

authors: LakshmanPatil jobingeo

repo: vmware/vsphere-automation-sdk-java


text:
可否考虑用开源的xlwings代替PyXLL

https://github.com/xlwings/xlwings
毕竟pyxll还是要年费的。-：）

xlwings没有提供RTD功能，所以没办法了，pyxll是市场上唯一能提供的，人家收钱还是有点底气

authors: vnpy yhmickey

repo: vnpy/vnpy


text:
可以增加OKEX期货gateway吗?

环境

操作系统: 如Windows 10
Anaconda版本: 如Anaconda 5.0.1 Python 3 64位
vn.py版本: v1.7.2发行版

Issue类型
三选一：Enhancement
预期程序行为
实际程序行为
重现步骤
针对Bug类型Issue，请提供具体重现步骤以及报错截图

群里有个OKEX期货接口但是持仓不能推送到数据库，群主看下能修复吗

1.8没时间做了，1.9来看下吧

群里已经有大佬修复完BUG了

authors: vnpy xldistance


text:
修改quick start

让后来的小白少踩些坑，能安装先跑起来。

怎么又传了这个，传错文件了，不好意思

怎么又传了这个，传错文件了，不好意思

怎么又传了这个，传错文件了，不好意思

怎么又传了这个，传错文件了，不好意思

怎么又传了这个，传错文件了，不好意思


text:
Allow users to login via email & store login data in Firebase

Create LoginController and LoginDirective
Implement functionality in those files to allow users to login via email
Store login info in Firebase
Utilize cookies to ensure that by default users are signed in
Add login button via HTML/CSS
Add pop-up template for logging in

Wireframe: 6. Main Page w/social media, menu & login button

repo: voiceofrae/RelaxIO


text:
InitContext panic when not set CookieStoreMaker

I only use SessionStoreMaker, and want to get CurrentUser, it panic , is it on purpose？
CurrentUser call InitContext, InitContext call CookieStoreMaker.
// CurrentUser retrieves the current user from the session and the database.
func (a *Authboss) CurrentUser(w http.ResponseWriter, r *http.Request) (interface{}, error) {
return a.currentUser(a.InitContext(w, r), w, r)
}
func (a *Authboss) InitContext(w http.ResponseWriter, r *http.Request) *Context {
ctx := a.NewContext()
....
ctx.SessionStorer = clientStoreWrapper{a.SessionStoreMaker(w, r)}
ctx.CookieStorer = clientStoreWrapper{a.CookieStoreMaker(w, r)}
return ctx

}

Will look into this. Is your use case that you don't want people to be able to click a "Remember Me" button?
Trying to understand why you would have a session storer only.

These interfaces should no longer be required if you're not using them in v2 (see releases page for more details).

authors: aarondl azumads

repo: volatiletech/authboss


text:
Change lookupkey in typescript

Hi Jaiq,
I have this lookup in form
public class ProductPriceForm
{
[LookupEditor("MasterModule.SparePartNumber")]
public Int32 ProductId { get; set; }
[LookupEditor("MasterModule.OrderCategory")]
public Int32 OrderCategoryId { get; set; }
public Decimal Price { get; set; }
}
Ho to to change lookupkey programmatically? i wanto to change lookupkey in typescript ProductId field from 'MasterModule.SparePartNumber' to 'MasterModule.UnitNumber'

You should make multiple forms and dialogs.

authors: ahsansolution volkanceylan

repo: volkanceylan/Serenity


text:
Old/New value in after save

Hello! You need to make a notification after the task is completed! Is it possible to understand that the task for the first time has passed to the status "Completed"? Or just the button to complete?

if you mean a service call, there are samples in code

I am lol
private class MySaveHandler : SaveRequestHandler<MyRow> {
        protected override void AfterSave()
        {
            base.AfterSave();

            if (base.Row.TaskStateId == 3 && base.Old.TaskStateId!=3)
            {
             .....
             }
     }

}


text:
Will there be an api to track device addition or removal?

Currently I'm looking at ways to make any device addition or removal event to be bubbled up to nodejs. I'm interested only in devices which come up as serial devices, and I was wondering if that sort of API will be supported? Mainly it would be good to abstract OS specific code that does the tracking of devices - RegisterDeviceNotification like function in Windows, udev on linux for example. Any thoughts?

Sadly we're kind of in feature lock down around here with our original maintainer out of commission for a while, and while we wait for some lower level node changes to better support serialport builds across platforms. That said if you come up with something let us know.

I have written a separate library using nan/libuv to surface code written by my colleague to do device notification in windows which notifies addition/removal of composite devices to nodejs. It's a callback based API. Though it's made for composite devices, I can probably make looking up drives associated to a serialport optional. I can use udev to do the same thing in linux too and I'd have to do this anyway. But I have no experience building for macos. I think this code can be merged into serialport library to setup tracking of devices rather than publishing it as a separate library.
The API currently takes a vid/pid, a callback for device addition and a callback for device removal. The callbacks are called with a device object which has various low level details along with serial port the device is enumerated as and mounted drive name for device attached.
Would this feature be of any interest? If it makes sense to include it into node-serialport then i can spend time to make it work with it.

Were actually kind of in feature lockdown as were currently in a node working group looking at using libuv or something else to remove most of our compiled code. I could see the emitters/whatever living in there and us utilizing those new apis. Can you get with them and see what they think?

authors: jacobrosenthal opensourcegeek

repo: voodootikigod/node-serialport


text:
Remove the implement_signals_with_pipe macro

It was previously being used to share logic that was common across multiple tokio versions. It's unnecessary now that
only one version is supported.

Codecov Report

Merging #89 (8f217e9) into master (dbe63f6) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #89   +/-   ##
=======================================
  Coverage   61.26%   61.26%
=======================================
  Files          27       27
  Lines        3565     3565
  Branches      181      181
=======================================
  Hits         2184     2184
  Misses       1380     1380
  Partials        1        1

Impacted Files
Coverage Δ

signal-hook-tokio/src/lib.rs
92.59% <100.00%> (ø)

Codecov Report

Merging #89 (8f217e9) into master (dbe63f6) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #89   +/-   ##
=======================================
  Coverage   61.26%   61.26%
=======================================
  Files          27       27
  Lines        3565     3565
  Branches      181      181
=======================================
  Hits         2184     2184
  Misses       1380     1380
  Partials        1        1

Impacted Files
Coverage Δ

signal-hook-tokio/src/lib.rs
92.59% <100.00%> (ø)

Thank you. It's time for me to spin up a release.

Thank you. It's time for me to spin up a release.

authors: bdash codecov-io vorner

repo: vorner/signal-hook


text:
Bug beadtype memory leak

If I fix the memory leak here, the integration tests fail.
  Start 14: Run_csg_fmatch

14/50 Test #14: Run_csg_fmatch .........................***Exception: SegFault  0.23 sec
Start 15: Compare_csg_fmatch_output
15/50 Test #15: Compare_csg_fmatch_output ..............***Failed    0.03 sec
Start 16: Run_csg_fmatch_3body
16/50 Test #16: Run_csg_fmatch_3body ...................***Exception: SegFault  0.23 sec
Start 17: Compare_csg_fmatch_3body_output1
17/50 Test #17: Compare_csg_fmatch_3body_output1 .......***Failed    0.03 sec
Start 18: Compare_csg_fmatch_3body_output2
18/50 Test #18: Compare_csg_fmatch_3body_output2 .......***Failed    0.03 sec
Start 19: Compare_csg_fmatch_3body_output3
19/50 Test #19: Compare_csg_fmatch_3body_output3 .......***Failed    0.03 sec
Start 20: Run_csg_map
20/50 Test #20: Run_csg_map ............................   Passed    0.03 sec
Start 21: Compare_csg_map_output
21/50 Test #21: Compare_csg_map_output .................***Failed    0.05 sec
Start 22: Run_csg_stat
22/50 Test #22: Run_csg_stat ...........................***Exception: SegFault  0.22 sec
Start 23: Compare_csg_stat_output1
23/50 Test #23: Compare_csg_stat_output1 ...............***Failed    0.03 sec
Start 24: Compare_csg_stat_output2
24/50 Test #24: Compare_csg_stat_output2 ...............***Failed    0.03 sec
Start 25: Run_csg_stat_angular
25/50 Test #25: Run_csg_stat_angular ...................***Exception: SegFault  0.23 sec
Start 26: Compare_csg_stat_angular_output
26/50 Test #26: Compare_csg_stat_angular_output ........***Failed    0.03 sec
Start 27: Run_csg_stat-imc
27/50 Test #27: Run_csg_stat-imc .......................***Exception: SegFault  0.23 sec
Start 28: Compare_csg_stat-imc_output
28/50 Test #28: Compare_csg_stat-imc_output ............***Failed    0.03 sec
Start 29: Compare_csg_stat-imc_output_2
29/50 Test #29: Compare_csg_stat-imc_output_2 ..........***Failed    0.03 sec

What is this about, what does it change and what does it fix?

When the topology object was being deleted, the BeadType was originally created with new and the corresponding delete was not being called. This is a benign memory leak, as it is only leaked when a toplogy object is released, typically at the end of simulation.

@JensWehner, I don't know, maybe @ruehle remembers.

The topology object has a destructor it calls on everything but whoever wrote it failed to free the beadtypes

authors: JensWehner JoshuaSBrown junghans

repo: votca/csg


text:
Remove NOT NULL constraints on non-id columns

There were NOT NULL constraints on columns that are either NULLable, or are often provided in imports without values.
The "processing-migrations" migrations don't need a separate migration to remove the constraint and can be edited in place because they are run on a fresh database for each import.
Pivotal bug 99134060

LGTM.

authors: bwreid tie-rack

repo: votinginfoproject/data-processor


text:
OrdersItem is missing some types

node_modules/@voucherify/sdk/dist/types/Orders.d.ts
export interface OrdersItem {
    sku_id?: string;
    product_id?: string;
    related_object?: 'product' | 'sku';
    source_id?: string;
    quantity?: number;
    price?: number;
    amount?: number;
    discount_amount?: number;
    applied_discount_amount?: number;
    product?: {
        override?: boolean;
        name?: string;
        metadata?: Record<string, any>;
    };
    sku?: {
        override?: boolean;
        sku?: string;
    };
}

From stackableAPI I get following orderItem:
{
        object: 'order_item',
        product_id: 'prod_0bb1dde463c907bdab',
        sku_id: 'sku_0bb1dee58a4c0093ca',
        quantity: 1,
        discount_quantity: 1,
        initial_quantity: 0,
        amount: 22900,
        discount_amount: 22900,
        initial_amount: 0,
        applied_discount_amount: 22900,
        price: 22900,
        subtotal_amount: 0,
        product: {
          id: 'prod_0bb1dde463c907bdab',
          source_id: 'c1a94282-088d-4006-8200-72c5bcdd8671',
          name: 'Sweater “Dayton“ Crossley blue',
          price: 28625,
        },
        sku: {
          id: 'sku_0bb1dee58a4c0093ca',
          source_id: 'M0E20000000EE12',
          sku: 'Sweater “Dayton“ Crossley blue',
          price: 22900,
        },
      }

Please fix :)

@p-zielinski Thank you for reporting this, fix has been implemented in following pull request: https://github.com/voucherifyio/voucherify-js-sdk/pull/152
I have released new version 2.0.15 which includes this fix and it should be shortly available in NPM registry.

repo: voucherifyio/voucherify-js-sdk


text:
Background process does not work

I have:

yii2 advanced
ubuntu 14.04

I placed this in the common\main.php:
'consoleRunner' => [
    'class' => 'vova07\console\ConsoleRunner',
    'file' => '@app/yii'
]

Inside of the SiteController I have created action called actionTest which is the following: (based on this issue)
public function actionTest() {
    $connection = \Yii::$app->db;
    $connection->createCommand()->dropTable('TestTable');
    $connection->createCommand()->createTable('TestTable', ['column1' => 'string', 'column2' => 'integer']);

    return 0;
}

and I am calling console runner from actionIndex like this:
Yii::$app->consoleRunner->run('site/test');

This problem happens in front-end and back-end side of the application, meaning that I cannot run background processes on either side.
And problem is that site/test does not want to execute on the background. I did this example just to test the class, however in real I need this class to send ~1000 emails.
Any clues what can be the cause of the issue?

Btw, according to this:
Yii::$app->consoleRunner->run('site/test');

I can pass params (eg. Yii::$app->consoleRunner->run('site/index param1 param2')) to the actions. However in the documentation it does not say how to get them inside from the action which is being called as a background.

I have created controller in a wrong place. It should be in console/controllers/


text:
Add acceptance test

We have an example in this project and can run acceptance tests against it.  Will it work?

With no experience with this module, fixing acceptance tests might be tricky… I feel like somebody used to the module can quickly manage to fix these tests so that we can have more coverage during tests. @FlorentPoinsaut maybe wink wink wink :wink: ?
The idea would be to adjust examples/init.pp until it works on all supported OS…

I take a look.

There are a problem with dependency packages (*_package_name) set in param class.
For Bareos 18.2 and 19.2, it need *-python-plugin package but for 20 and 21 versions, it is *-python3-plugin.
I don't find a way to do this without moving this variables form param class to repository class.
May I do that or you see another solution?

Okay, if I follow correctly the package lists are OS dependent and dependent on the usage of external repos. Maybe me can have for each OS the list of packages by repo in params.pp, e.g.:
$system_director_packages = ['foo']
$bareos_director_packages = ['python2-foo']

And for another OS:
$system_director_packages = ['python-foo']
$bareos_director_packages = ['python3-foo']

Then depending on the repo used we use the suited variable in the main manifest:
$director_package_name = undef, # change to undef so we can pick later

# Get the right packages for fallback if not provided
$default_director_packages = $manage_repo ? {
  true  => $bareos_director_packages,
  false => $system_director_packages,
}

# pick the right package
$director_packages = pick($director_package_name, $default_director_packages)

# use it
package { $director_packages:
  # ...
}

That way we don't change the interface for end users of the module and all the actual data is in params.pp (making it easy to switch to hiera data in the future).
Probably not the only way to do it?

Rebased on current master.

It looks like this is failing because the bareos-database-mysql doesn't exist for baseos 21:  https://www.bareos.com/end-of-life-mysql/

Rebased on current master.

authors: FlorentPoinsaut jhoblitt smortex

repo: voxpupuli/puppet-bareos


text:
Add license to gemspec

fixes: #90

@timhughes Thanks!

authors: alexjfisher timhughes

repo: voxpupuli/puppet-blacksmith


text:
puppetlabs/stdlib: Allow 9.x

also contains

#62
#63
#64
#65

this need another puppetlabs/docker release

i think we only need to rebase all the respective PRs now?

superseded by #82

authors: bastelfreak zilchms

repo: voxpupuli/puppet-hdm


text:
Pagination prototype

Hi,
I recently installed puppetboard, but was not able to go in production. With thousands hosts, I got some issues with response time and laggy browser.
I am trying to patch in order to get pagination everywhere (PR code). But, I'm kinda stuck with pypuppetdb nodes endpoint. I can not find a reliable way to count nodes on status.
Looking at pypuppetdb, this situation is normal as status is determined only after request. Do you think (in a reasonable future) every field can / may be suitable for filter or count ?
I am available to work on it if this is ok for you.

Thank you for your submission. I do, however, have some notes for this PR in no particular order.

Please restrict your changes to default_settings.py to ONLY the entries you wish to add. This includes whitespace
Please especially refrain from changing the values of existing configuration settings, the PR may be closed as a result if the changes are not reverted.
The development work done in #271 can be implemented for the Nodes page for pagination and result limiting
The PuppetDB queries for the index page can be improved to exclude nodes in an 'unchanged' state, will create a separate issue for this
The index page will only provide users with an overview to their environment's health, any functionality about result limiting and pagination should be done in the nodes page (see Point 4)

authors: corey-hammerton redref

repo: voxpupuli/puppetboard


text:
Puppet 5 deprecation

This issue is a result of https://github.com/voxpupuli/voxpupuli.github.io/pull/228
Puppet 5 will be end of live soonish. In the past, when Puppet 3 and Puppet 4 were end of live, we removed them from the metadata.json. I propose we do the same with Puppet 5 now. Since our modulesync_config release 4, we generate our acceptance tests based on operating systems in metadata.json and the puppet versions in metadata.json. his means as soon as we drop Puppet 5 from metadata.json, we also stop running our unit tests on it.
Benefits:

This would fix Ubuntu 20.04 tests where Puppet does not even provide puppet 5 packages anymore
It's consistent behaviour with our Puppet 3/4 deprecation
It won't encourage people to use outdated software

@voxpupuli/collaborators please provide feedback :)

My only concern is how do we release new major versions for all the modules?  I would expect a major release for this type of change.

I agree. A major release should follow (which we also did in the past).

When we drop it, we need to figure out a new minimum version. I'd recommend Puppet 6.1.0 as a lower bound. This means we can drop the systemctl daemon-reload workaround that's present in various modules.
If we drop it, we should also drop any compatibility code that may be present. Otherwise that just sits there and complicates the module.
Some considerations:

There is very little Puppet 5 compatibility code since 5 & 6 are largely compatible.
It's not EOL yet
Debian and Fedora native packages are still Puppet 5 and some people prefer those (myself included)
Generally the extra CI is not that much overhead

That's why I'm in favor of holding off on dropping it in every module. I can provide a list of modules that I care about and will ensure they keep working on Puppet 5 if desired.
A good reason may be that a dependency has dropped Puppet 5 support, whether released or still in git. Perhaps we can automate that check somehow.

Sounds good to me. 👍

As has said a major release would be warranted it would also be nice if we could create a branch before increasing the release e.g. puppet5.x.  no commitments or modsync on this branch but it would make it a little easier for people who need to use puppet 5 for a little longer to contribute any critical fixes

As has said a major release would be warranted it would also be nice if we could create a branch before increasing the release e.g. puppet5.x. no commitments or modsync on this branch but it would make it a little easier for people who need to use puppet 5 for a little longer to contribute any critical fixes

this is kind of how we've dealt with 3.x

We didn't do a puppet4 branch because the changes from 4 to 5 were so small.

I'd prefer to leave Puppet 5 compatibility up to individual modules.
I would be okay with  a policy where maintainers are free to add Puppet 6 -specific features if the module benefits from them, but I on't see much value in going through Voxpupuli modules explicitly making them incompatible with Puppet 5. While it'll be unsupported by upstream, it will still be found in stable distros for a long time.

:+1: I am generally in favor of a (current major release) + (current major release -1) support policy.dd

LGTM, We should have a look at modules where changes are in the pipeline which require a major melease to, and coordinate them together

Of possible note, it appears that debian hasn't updated 4.x & 5.x packages to the latest upstream patch releases (stretch is still on 4.8.2 and buster is install on 5.5.10).  I'm fairly skeptical that distros are going to put in the effort to backport security fixes.  We should consider if we as a project are enabling this behavior.

Of possible note, it appears that debian hasn't updated 4.x & 5.x packages to the latest upstream patch releases (stretch is still on 4.8.2 and buster is install on 5.5.10). I'm fairly skeptical that distros are going to put in the effort to backport security fixes. We should consider if we as a project are enabling this behavior.

This is how debian , and many linux distros,  work.  They pick a stable release to use before going into  a release freeze and then they backport and maintain all security/bug fixes.  A better description of the process is here (this is ubuntu but the same or simlar holds true for debian, redhat etc)

@b4ldr I understand the theory of how stabilized distro packages work. My point was that process appears to not be working for debian as they have not packaged the latest patch releases and I don't see any obvious back-porting.  Nor is there, to my knowledge, any major effort to maintain major releases once they have been EOL'd by upstream that distros could draw from.
In took me only seconds to find known security issues with the debian packaged versions:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7942
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2295
Users are obviously free to chose any environment.  However, if someone has chosen to use Slackware 1.01 and doesn't want to invest the effort to upgrade, it doesn't mean that this project should automatically try to support that decision.

Another strike against el5 is that it is not support by puppet 7.x: https://puppet.com/docs/puppet/7.0/new-since-puppet-7.html

For me the major reason to use the Debian distro packages is that they don't bundle a Ruby version but I'll agree that the distro versions are in a sad state. That is my impression of the overall state of Puppet in the open source world. It appears most users have moved on. Those still using it are often in stable environments where little changes.

The "upstream moves too fast for distro packaging problem" is what SCLs and modularity/streams support in el8/fedora are trying to solve.  It would be nice if the official packages would take advantage of either of these solutions.  I have long used the foreman SCL which once upon a time even packaged puppet.
I am in the camp that believes stabilized distros can't reasonably support "fast" moving projects and the limited effort available would could be used much more productively than trying to do things such as de-vendorizing k8s libs.  Complex apps like k8s should be running in containers anyways (E.g. rke).  Puppet is somewhat of a special case in that containerizing the agent would be fairly difficult.

I agree that it would be nice if Puppet used SCLs on EL7. Puppet's RPM packages are dreadful. Sadly, they invented their own packaging solution so I can't provide any patches. My bug reports have generally gone unanswered or closed with WONTFIX. If it wasn't for distro packages there's a good chance I would simply stop using Puppet.

It is essentially the opposite for me.  Bare metal hosts have a puppet yum repo mirror setup and the agent installed as part of kickstart.  What the distro packages or doesn't isn't really a significant impact as there are a fair number of non-distro repos that have to be managed anyways. The majority, but not all, of applications have migrated to containers/k8s and are outside the scope of puppet.

My point was that process appears to not be working for debian as they have not packaged the latest patch releases
Sid has https://packages.debian.org/source/sid/puppet which seems to be the current path release and work is underway to package puppet6 for bullseye

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7942
This one is being tracked

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2295
This is claimed to be fixed and the patch is in the git repo

So sure not perfect but i think its disingenuous "that process appears to not be working for debian"

i second @jhoblitt general strategy proposal of  a (current major release) + (current major release -1) support policy. With the added addendum that both versions need to be in support.
So with puppet 7 only being freshly released i would say its the right time to start the discussion but perhaps not to pull the trigger as yet but there are only a couple more weeks of puppet 5 support left so respite wont be to long.
I generally only track/consider the upsteam puppet inc repos as many of us have remarked the distro packages are lagging behind significantly. Also not releasing puppet 5 on ubuntu 20.04 by puppet inc to me signals (perhaps incorrectly) intend for a quick "stage left" exit for Puppet 5 on their end.
So for the the time being i would second @igalic suggestion to move puppet5 support into a branch but remove puppet 5 support from the main/master branch. And let individual contributors to repos decide how long they are willing to take the engineering time/cost of maintaining puppet 5 support

Also not releasing puppet 5 on ubuntu 20.04 by puppet inc to me signals (perhaps incorrectly) intend for a quick "stage left" exit for Puppet 5 on their end.

Back then Puppet 5 was the LTS release. Just as that they did build puppet-agent for Puppet 5 but not puppetserver 5 on Debian 10. I still don't understand how they made those choices. Still frustrates me and since there was no real good explanation IIRC (other than "we just don't want to"). If there was a technical reason, it would be much easier to understand.

my distro just dropped a puppet7 release four days ago but i haven't had time to update yet…

Do we have a consensus in the text on #232?

Do we have a consensus in the text on #232?

quite uncool as puppet 5.5 is shipped with debian stable (buster). version rushing is quite a bad thing :(

authors: SimonHoenscheid attachmentgenie b4ldr bastelfreak c33s crazymind1337 ekohl igalic jhoblitt logicminds oranenj towo


text:
Cannot reproduce the results on the PanNuke dataset

Hello! I am trying to reproduce the results in the paper PanNuke Dataset Extension, Insights and Baselines. I used the following dataset split :Training: Fold 1; Validation: Fold 2; Testing: Fold 3.
I used the PyTorch version of the code for training and obtained the following results:
mean,0.4213653276623722,0.6425824540937765(PQ, PQ bin)

The obtained results are lower than the average results mentioned in the paper.I used the fast model mode and commented out the affine transformation.

Hello, I have encountered the same problem. How did you solve it?

authors: Xujingkk mqbin


text:
Allow updating remote parameters by network-syncing certain OSC messages

What's the idea?*
This is a proposal for network synced OSC messages. This proposal is closely related to the Allow driving local parameters with OSC proposal. I'm submitting this as its own proposal to avoid derailing that one with a different topic, but I'm happy if someone wants to merge them as well.
Certain OSC messages themselves could be sent (and rate limited) as events over the network. Even though the animator parameters themselves would only be local, everyone's local copy could update at roughly the same time when an OSC message is broadcast. This is similar in some ways to the difference between Udon variables and events.
Perhaps the OSC json config can have a property specifying whether messages should be networked.
		{
			"name" : "Face",
			"input" : {
				"address" : "/avatar/parameters/Face",
				"type" : "Int",
                                "synced": true // Only makes sense for inputs to be synced
			},
			"output" : {
				"address" : "/avatar/parameters/Face",
				"type" : "Int"
			}
		},

By having an inventory of the parameters that can be synced, the network protocol could be made quite efficient as well. Rather than transmitting a full parameter name on every update, the client could do something like:

When another player joins, send them our mapping of parameter names to binary IDs.
As the game runs, send packets of the form 0x00 0xFF (set the first networked OSC slot (0x00), which according to our mapping above is the Face parameter, to 127).

This example protocol could give players up to 256 possible OSC parameters that could be networked, at 2 bytes per message. (Maybe 16-bit numbers are affordable? 🙏 )
A rate limit could be built on top of this, where rather than limiting the number of parameters, we limit the total bitrate of OSC updates: "You get to transmit up to 512 bytes/sec in OSC updates before messages start getting dropped."
Is there another way?
The only other way to network avatar data is through animator parameters, which are very limited (for good reason!) and have semantics that are very useful for some things (like reliable, atomic updates of multiple parameters) but not needed for everything.

I'll note that if this is implemented, it would be useful to also consider a state behavior that could drive transmitting a synced avatar message without going through OSC.

Now that Contacts are public: Triggering an RPC-like message from remote users to the avatar owner would be a nice feature for AVD as well, and would fit in nicely with similar messages in the other direction from OSC.

authors: bdunderscore seanedwards

repo: vrchat-community/osc


text:
Filters in wf list, remove reana-client dependency

After testing reana_client, we have faced some limitations. We could solve the REANA_SERVER_URL with the solution proposed by Marco (#11), but after that we have seen that the methods in reana_client do not return all the information that the REST API returns (e.g., pagination info), and also restrict some of the requests we can do (e.g., sorting the workflows list). Note that this can be solved on the client side, but may affect the performance.
For this reason, the extension requests the information directly to the REST API, giving us more flexibility to decide which information is shown in the extension.
We have also added some workflow filters in this PR (filter by status and sort by).

Important: In this PR we used /api/ping to check the connection, which always returns a 200 status. In 5467f39f074424c08e35f68abc836788b6bfd14e it is fixed by using the endpoint /api/you instead (as reana-client does).

repo: vre-hub/reana-jupyterlab-extension