text:
Create prerequisites appropriate for load balancer.

This tutorial creates a Service of type LoadBalancer, so the reader needs to be using a cloud provider. I have updated the Before You Begin section to say, "Use a cloud provider ...".
This text was in the document originally, but I accidentally removed it in https://github.com/kubernetes/kubernetes.github.io/commit/c60107ea1c8b560a57fd4d190d832abe7ce49f58.

This change is

cc @waprin
Looking at Bill's minikube tutorial, can't type: LoadBalancer work with minikube as well?
Otherwise, I think a stand-alone page with instructions for running tutorials w/ node port might be good. It would be a shame of almost all of our tutorials stated they required a cloud provider.

@jeffmendoza

Looking at Bill's minikube tutorial, can't type: LoadBalancer work with minikube as well?

Otherwise, I think a stand-alone page with instructions for running tutorials w/ node port might be good. It would be a shame of almost all of our tutorials stated they required a cloud provider.
I think the three of us should discuss this in a meeting. It probably depend on whether you need an actual external IP address; you don't get that with Minikube.

Sounds good

/lgtm
If you want to merge now sounds good. We can come up with a better prereq template in January for how to run type: LoadBalancer on a non-cloud.

LoadBalancers don't work on Minikube in the sense that they don't provision an actual LoadBalancer. However do they make the Service externally visible (i.e. in your browser) via the minikube service command. In that sense, if you want to see your app run in the browser on Minikube, you must use type LoadBalancer.

authors: jeffmendoza steveperry-53 waprin


text:
fix typo

fix typo

This change is

\lgtm

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
Revert "ZTE-SH-CN-configure-pod-container-opaque-integer-resource-2017-09-15"

Reverts kubernetes/kubernetes.github.io#5469

This change is

lack of oir-pod-2.yaml may result in deploy failed.


text:
authentication: add service account and webhook docs and update formatting

It was brought up in #sig-auth today that the service account authenticator isn't mentioned in the authentication docs, and that this document is generally pretty outdated. Took the opportunity to fix up the following:

Added top level section about what authenticators do.
Added section about service account tokens.
Added section describing webhook authenticator.
Updated OpenID Connect section.
Provided more recent link to Keystone authenticator work.
Generally updated formatting to bring more in line with the authorizer document.
Removed @yifan-gu from assignees as I'm taking over the OpenID Connector authenticator from him.

cc @kubernetes/sig-auth @lavalamp @erictune
edit:
This possibly addresses #598 @nVitius

@deads2k

@lavalamp should @deads2k be the reviewer?

YEs.
On Wed, Aug 3, 2016 at 4:09 PM, Phillip Wittrock notifications@github.com
wrote:

@lavalamp https://github.com/lavalamp should @deads2k
https://github.com/deads2k be the reviewer?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes.github.io/pull/959#issuecomment-237402992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnglo4q6EcCjTu_TAeNjPvVilb2xnrJks5qcR-qgaJpZM4JcJqw
.

@ericchiang Please also add @deads2k as an assignee

Nice improvements, Eric, thanks!

@ericchiang friendly bump.

Fixed typos and resolved some smaller issues pointed out by @erictune and @deads2k.
Added a section at the top titled "Users in Kubernetes" to emphasize how Kubernetes thinks of users and the difference between service accounts and normal users.
Expanded the service accounts section to note that they're automatically created and associated with pods by the ServiceAccount Admission Controller.

Oh couple questions. How do we spell:

service account vs Service Account
API server, API Server, apiserver?

Oh couple questions. How do we spell:

I do "service account" and "API server", but I suspect that an editor will sweep eventually.
Changes lgtm.

I do "service account" and "API server", but I suspect that an editor will sweep eventually.

Okay, I've standardized on those for now and will defer to a future editor.

lgtm, manually merging per: https://github.com/kubernetes/kubernetes.github.io/pull/946#issuecomment-238952955

authors: deads2k ericchiang erictune lavalamp pwittrock


text:
Add benchmark app

What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds a tool that spawns n goroutines that synchronously send requests to a given URI.
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
/assign @marseel
/assign @mborsz
Does this PR introduce a user-facing change?:
NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/retest pull-perf-tests-verify-lint

/test pull-perf-tests-verify-lint

/lgtm
/approve

authors: jupblb mborsz

repo: kubernetes/perf-tests

license_source: bigquery


text:
Temporarily increase scheduler cpu constraint.

This is to deflake presubmit until we figure out what has changed.
Ref. https://github.com/kubernetes/kubernetes/issues/80212

/assign @krzysied

/lgtm


text:
Issue with k8s.io/docs/concepts/workloads/controllers/statefulset/

This is a Bug Report

Problem:
Third bullet in the "limitations" section says "Deleting and/or scaling a StatefulSet down will not delete the volumes associated with the StatefulSet".
It is not wrong, but not totally right. I think it should better refer to the PVCs created from the statefulset's volumeClaimTemplate than to the pre-provisioned or dynamically created PVs boudn to those PVCs (note also that removing/not removing those PVs is really related to the PV/StorageClass set reclaimPolicy .. once PVC and PV are unbound, of course)
Proposed Solution:
Following text proposed for that third bullet in the "statefulset - limitations" subsection (changed text remarked with bold letters)

Deleting and/or scaling a StatefulSet down will not delete the persitent volumes claim objects created from any volumeClaimTemplates included in the StatefulSet. This is done to ensure data safety, which is generally more valuable than an automatic purge of all related StatefulSet resources.

Page to Update:
https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#limitations

Thanks for the suggestion!

/language en

/assign

/priority backlog

/remove-lifecycle stale
/help
(almost a good-first-issue, too, IMO)

/retitle Improve wording for StatefulSet limitations around storage

source: gharchive/issue

authors: antaloala medmedchiheb sftim

repo: kubernetes/website


text:
clarify behavior of memory request vs limit parameters

https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#exceed-a-container-s-memory-limit says:

A Container can exceed its memory request if the Node has memory available. But a Container is not allowed to use more than its memory limit. If a Container allocates more memory than its limit, the Container becomes a candidate for termination. If the Container continues to consume memory beyond its limit, the Container is terminated.

This paragraph is very confusing. Is this a correct reading?

the container may rely on at least 'request' bytes of memory.
the container is immediately terminated if it ever exceeds 'limit' bytes of memory.
in between these values, the container may be terminated at any time due to memory exhaustion.

It would be helpful to explain what system mechanism is used to limit memory, and whether it interacts with Linux overcommit. Also, whether garbage-collected language runtimes have any particular expectations or preferences. The latter two points could be addressed by links to other articles.

/sig node

/language en

The doc says "[a] Container can exceed its memory request if the Node has memory available", which implies (though it is not unambiguously stated) that if memory is not available, then a container that allocates more than its request is liable to be terminated. If this is true, and it is also true that, as you say, "a container that allocates more than its memory limit is liable to termination" but "might be able to continue", then why have the concept of limit at all? It appears to add nothing.
Assuming limit >= request, there are three situations of interest:

ram <= request
request < ram <= limit
ram > limit
What can the user assume when operating in these three regimes?

/remove-lifecycle stale

authors: adonovan sftim


text:
EndpointSlice example does not work as documented

From：https://kubernetes.io/docs/concepts/services-networking/service/
Chapter： Services without selectors
Ineffective：

===》Actually，command ”kubectl get endpointslices” could get 2 specified IP，but iptables can only get first ip

only iptables rule of 10.4.5.6， no 10.1.2.3

After the modification：
endpoints:

addresses:

"10.4.5.6" # the IP addresses in this list can appear in any order

addresses:

"10.1.2.3"
===》There are 2 separate iptables rules：

/triage accepted

This was introduced in 1eef7424651bdc681711572e1042169faebe8e81.

This looks like a duplicate of https://github.com/kubernetes/website/issues/42405
I'd prefer to triage the older issue as accepted
/remove-triage accepted
/triage duplicate

authors: hl843901190 sftim tengqm


text:
Look and Feel of Layout of Storage  Section

This is a Bug Report
In ref of https://github.com/kubernetes/website/issues/42947 issue the same issue is in Storage various pages.

Problem:
The  top right section of the page having  links (Edit this page, Create child page, Create an issue, Print entire section)  are displaying in the bottom of the page.
Proposed Solution:
It should be displaying in upper right side of the page. The page design should be universal in all.
Pages to Update:
Volumes
Persistent Volumes
Projected Volumes
Volume Snapshots

/language en
/sig docs

/area web-development

You don't need to open separate issues for each individual section where this issue is present, instead mention all the pages in #42947
/triage duplicate

/close


text:
Translate Spotlight on SIG Release (Release Team Subproject) into Japanese

This is a Feature Request

What would you like to be added

Translate Spotlight on SIG Release (Release Team Subproject) into Japanese.
Why is this needed
This page has not been translated.
Comments

/language ja
/assign

/triage accepted

/close
completed in #44935

authors: Gauravpadam shukawam


text:
Contradiction in Kubernetes API Aggregation Layer and Custom Resources pages

This is a Bug Report

Problem:
In Kubernetes API Aggregation Layer:

The aggregation layer is different from Custom Resources, which are a way to make the kube-apiserver recognise new kinds of object.

Yet in Custom Resources:

Kubernetes provides two ways to add custom resources to your cluster:

CRDs are simple and can be created without any programming.
API Aggregation requires programming, but allows more control over API behaviors like how data is stored and conversion between API versions.

Proposed Solution:
I'm not really sure what the intention here is/was, but perhaps where the Kubernetes API Aggregation Layer page says

Custom Resources

It should say

Custom Resource Definitions

What do you think?
Page to Update:
One of the following

https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#adding-custom-resources
https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/

/wg api-expression
/sig architecture
/language en
The proposed change sounds reasonable.

/assign

/remove-lifecycle stale

/triage accepted
although I don't think this change makes a huge difference.

The issue is fixed in #47165 and hence we can close this isse

/close

authors: ricardoapl sftim tengqm vaibhav2107


text:
Add new community-maintained nodejs client

Adds a link to a new nodejs client library. New library builds on top of the godaddy lib, providing useful kubectl-like abstractions like get and updateOrCreate, and adds API-mapping and version-handling so the client code does not need to worry about compatibility across cluster versions.

/check-cla

/approve /lgtm

@jaredbhatti it doesn't look like the /lgtm flag went through?

/lgtm

authors: ajpauwels jaredbhatti


text:
Added FIAAS Python client library

I have added the FIAAS Python client library. The library is still in development, and not complete. It has a different approach than most other libraries, which some developers might find more suited to their tastes.

/assign @sftim

Hi. What can I do to get this merged?


text:
[zh] sync and update statefulset.md

update based on English version of statefulset.md

added a block inside #stable-network-id
sync tables and blocks
added a sentence in #parallel-pod-management

welcome all the comments :)

/lgtm


text:
API Reference v1.22

Replaces https://github.com/kubernetes/website/pull/28635

Move the assets necessary to build the API Reference from the api-ref-generator submodule (https://github.com/kubernetes-sigs/reference-docs) to this repository. This is in preparation to add translation assets for the API Reference (https://github.com/kubernetes/website/pull/27842)

Generated files for the API Reference for v1.22 (beta.0 at this time)

Hi @feloy looks like there is a conflict in the README. would you be able to address this?

/approve
We can push a merge commit if need be, but a rebase against current dev-1.22 would be ideal.

Hi @feloy looks like there is a conflict in the README. would you be able to address this?

Hi @annajung I addressed the conflict

Did this merge accidentally (no lgtm)?

authors: annajung feloy kbhawkey sftim


text:
[zh] Resync secret

This one is big. It is a rework because the upstream Secret concept was almost rewritten.

Thanks @SataQiu, all fixed.


text:
[zh] sync1.26  leases.md

Add zh text to:
content/zh-cn/docs/concepts/architecture/leases.md

Preview: https://deploy-preview-38490--kubernetes-io-main-staging.netlify.app/zh-cn/docs/concepts/architecture/leases

/lgtm
/approve
Kicking this in because some new changes are coming like #38307.

authors: tengqm windsonsea


text:
[zh-cn] Sync cpu-default-namespace.md

Sync content/zh-cn/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace.md with en page.

/lgtm
/approve

authors: Zhuzhenghao tengqm


text:
[Storage Version Migrator] docs: adds feature gates and runtime config information

Adds feature gates and runtime config information required to use storage version migration feature.
Fixes https://github.com/kubernetes/website/issues/46862
/cc @enj @jpbetz @deads2k

LGTM once Tim's comments have been addressed.

Try these changes?

@sftim PTAL when you get a chance. Thanks for review!

authors: enj nilekhc


text:
Update kubeadm_init.md

Some flags have been removed in v1.9.

This change is

@zacharysarah @chenopis  Are files under generated/ allowed to change? Some contents are outdated.

@islinwb Yes, though changes to generated docs happen upstream (often in kubernetes/kubernetes).

authors: islinwb zacharysarah


text:
Format security note with proper highlighting

The information about security of ssh keys might benefit from standing out more. Thus included it in a caution shortcode. Formatting is now more aligned with the style guide.
Preview: https://deploy-preview-9942--kubernetes-io-master-staging.netlify.com/docs/concepts/configuration/secret/

@tvshc BTW, please check the build preview to verify that the page is rendering correctly. For example, the caution tag was not closed properly, so it looked like this:

I fixed it, so it should be ok now.

/lgtm
/approve

authors: chenopis tvshc


text:
Missing right side panel in OpenShift

Describe the bug
The right side panel in the UI isn't displaying after setting Kubeshark up in Openshift.
Provide more information
Running on a 14 node Openshift cluster (version 4.10)
To Reproduce
Steps to reproduce the behavior:

Run kubeshark tap
Run kubeshark proxy
Open local host for UI
See missing panel

Expected behavior
I want to see both the left and right side panels in the kubeshark UI.
Logs
Upload logs:
Logs not optional right now, tore kubeshark down for the moment. All pods were running without errors.
Screenshots

Desktop (please complete the following information):

Windows 10 22H2 19045.3086
Web Browser: MS Edge

Additional context
Works fine and as expected in minikube and AKS.

Hiya, just noting that I experience this issue in Chrome as well. Other than the missing panel this tool is super cool! Thanks to the kubeshark team for creating this!

Hi @WyrickC, we don't have an OpenShift env at this point. Hopefully we'll get to that soon as OpenShift is definitely an environment we want to support.

Hi @alongir! Thanks for getting back to me. Is there a concrete timeline at all for this? Or any temporary workaround? I'd really love to use this tool in our clusters

Still waiting for openshift support!

authors: WyrickC alongir bakalor

repo: kubeshark/kubeshark


text:
Dashboard: UX Debt - Policies

UX Feedback from #426  :

Root row is being incorrectly included in filter results

Can we enlarge expand target area so it's easier for user to select control

check hover styling for hide/enable menu - sizing, hover styling/behaviour and icon color.

menu should height should reach to bottom of screen

Form sub headers (CORS) should be font weight regular/400

Styling of a disabled path or operation should match that of figma design
https://www.figma.com/file/wecNPLnwPgaQiZaXDWolSa/Kusk-Gateway-Dashboard?node-id=3208%3A55542

input label is incorrect style

addressed: https://github.com/kubeshop/kusk-gateway-dashboard/pull/346

@mortada-codes there's still a couple of things here - the CORS sub headers, disabled path/operation styling and the menu styling. We can have a chat about it.

authors: donnalux mortada-codes

repo: kubeshop/kusk-gateway

license: MIT


text:
chore(release): 2.4.5

This PR...
Changes

Fixes

How to test it

Screenshots

Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

@monojack could we check if there are any major electron/electron-builder upgrades available?

@monojack could we check if there are any major electron/electron-builder upgrades available?

Electron has 2 major increments. I took a quick look at the documented breaking changes and tried a search through the source code - looks like we're not using any of the changed/deprecated/removed symbols.

thanks @monojack - perhaps there is a 27.X upgrade that we should use for security fixes that won't break our build?

Was just checking 27.x and 28.x, they both work. Which one would you like??

then I'd go for 28 - thanks!

authors: monojack olensmar

repo: kubeshop/monokle


text:
bug: CI testing succeeded for PR that broke some tests

Describe the bug
The merge of PR #814 made some of the docs-ecutable tests start failing.  Indeed, the branch in that PR --- the new-issue-559-560 branch in https://github.com/fileppb/edge-mc, which pointed to commit 0e6e3f90c12020bcba9cc409c2278f8a4e8c6108 at the time --- also fails those tests.  And yet the testing in CI succeeded!  See https://github.com/kubestellar/kubestellar/actions/runs/5626329356 for an example.  See https://github.com/kubestellar/kubestellar/pull/814#issuecomment-1646894692 and the later comments for an explanation of the problem introduced and what is mysterious about the CI testing.
Steps To Reproduce
See above.
Expected Behavior
For a PR that breaks some tests, running those tests on the merge of that PR does not succeed.
Additional Context
No response

will work on this tomorrow

@MikeSpreitzer @clubanderson I also noticed that there are references in the .md's to SyncTarget.workload.kcp.io and Location.scheduling.kcp.io that need to be replaced with references to the edge.kcp.io api group. Will take a look at all the .md's.

@MikeSpreitzer @fileppb
I would like to get the CI to fail for 814.  It appears that the simple checkout that the workflow (for all docs-ecutable files) is referencing the base branch and not the the latest commit in any given PR.  To fix this I would like to test by

unmerging PR 814
add (at line 50 of docs-ecutable-example1.yml)
“with:
ref: ${{ github.event.pull_request.head.sha }}”
push a commit.

what do you think about this approach?  Or do you see another way to test the fix?

I am recommending (for all docs-ecutables)
 - uses: actions/checkout@v3.5.3
        with:
          ref: ${{ github.event.pull_request.head.sha }}
        if: github.event_name == 'pull_request'

      - uses: actions/checkout@v3.5.3
        if: github.event_name != 'pull_request'

@clubanderson , the workflow is already checking out and testing the relevant merge.  If you look at https://github.com/kubestellar/kubestellar/actions/runs/5626329356/job/15246915748?pr=814 , in the output of the actions/checkout, you will see that it checked out https://github.com/kubestellar/kubestellar/commit/bb51749176bcdfbd36f36249ab599b9917b1ab95 , which is a merge of @fileppb 's branch with what I surmise was in main at the time.  This is what we want tested.

I have re-created https://github.com/kubestellar/kubestellar/commit/bb51749176bcdfbd36f36249ab599b9917b1ab95 by the following commands.
(venv) mspreitz@mjs12 kubestellar % git checkout -b 817-test1 3281ffe2bb684bd738a7803e002c415568f71eca
Switched to a new branch '817-test1'
(venv) mspreitz@mjs12 kubestellar %
(venv) mspreitz@mjs12 kubestellar % git merge 0e6e3f90c12020bcba9cc409c2278f8a4e8c6108
hint: Waiting for your editor to close the file... 2023-07-24 13:31:02.324 Emacs[25786:3206670] It's not legal to call -layoutSubtreeIfNeeded on a view which is already being laid out.  If you are implementing the view's -layout method, you can call -[super layout] instead. Break on void _NSDetectedLayoutRecursion(void) to debug.  This will be logged only once.  This may break in the future.
Merge made by the 'ort' strategy.
...
(venv) mspreitz@mjs12 kubestellar % git status
On branch 817-test1
nothing to commit, working tree clean
(venv) mspreitz@mjs12 kubestellar % git log
commit 3092ac2827190d96183ee116ef487e56e8972b98 (HEAD -> 817-test1)
Merge: 3281ffe2 0e6e3f90
Author: Mike Spreitzer <mspreitz@us.ibm.com>
Date:   Mon Jul 24 13:31:01 2023 -0400

    Merge commit '0e6e3f90c12020bcba9cc409c2278f8a4e8c6108' into 817-test1

commit 0e6e3f90c12020bcba9cc409c2278f8a4e8c6108 (fileppb/new-issue-559-560, new-issue-559-560)
Author: Robert Filepp <filepp@us.ibm.com>
Date:   Fri Jul 21 16:26:18 2023 -0400
...

I then tested it, and it failed as it should:
(venv) mspreitz@mjs12 kubestellar % make MANIFEST="'docs/content/Coding Milestones/PoC2023q1/placement-translator.md'" docs-ecutable
...
++ kubectl kubestellar ensure location florin loc-name=florin env=prod
--- current directory is /Users/mspreitz/go/src/github.com/kubestellar/kubestellar/kubestellar
current ws is root:imw-1
imw is .
current cwsi is root:imw-1
error: apibindings.apis.kcp.io "edge.kcp.io" is forbidden: unable to create APIBinding: no permission to bind to export root:espw:edge.kcp.io
make: *** [docs-ecutable] Error 1

So I am still mystified about why https://github.com/kubestellar/kubestellar/actions/runs/5626329356/job/15246915748?pr=814 --- which tested the same contents --- succeeded.

I am out of ideas for how to investigate why https://github.com/kubestellar/kubestellar/actions/runs/5626329356/job/15246915748?pr=814 succeeded.
We need to make some testing gate merging a PR.  Right now the GitHub Actions for docs-ecutables are only FYI and not connected to the merge that updates the base branch of the PR.  I do not know whether or how GitHub Actions could be used to make these tests gate the merge that updates the base branch.  I think this sort of thing is part of what Prow does.

lets try a different PR (a simple and non consequential one) that we know breaks the docs.  Then we can fast-forward and rewind as much as we like.

Yes, that sounds like a good idea.

should we continue to chase this or regard it as a flake and re-open if we find this behavior again?  @MikeSpreitzer ?

If you're asking me, I would regard it as a weird combination of events that might be difficult to recreate, and shouldn't recur now that we're pointing to the correct (or expected) source for our build.

I am going to close this for now as a flake.

authors: MikeSpreitzer clubanderson fileppb

repo: kubestellar/kubestellar


text:
:soap: CI use console latest image

Issue:
UI CI scripts use console latest image, CI may brake if console latest changes.
Fix
Lock console image used for CI

Addressed by: https://github.com/kubev2v/forklift-console-plugin/pull/1316


text:
Log velero backup and restore in tests

Signed-off-by: Bartosz Rybacki brybacki@redhat.com

What this PR does / why we need it:
Log velero backup and restore objects and also the pod logs (especially velero pod logs might be interesting).
Additionally adds a Junit reporter which might be used by PROW to better show failed/skipped tests.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

ok, I can see backups, restore and pod logs correctly here:
https://gcsweb.ci.kubevirt.io/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt-velero-plugin/16/pull-kvp-functional-test/1455905384765067264/
I will mark pull-kvp-functional-test  successful since the failures are not related, and need investigation (for which I need this PR).
Issue already open: https://github.com/kubevirt/kubevirt-velero-plugin/issues/14

/override pull-kvp-functional-test

/lgtm

/approve

repo: kubevirt/kubevirt-velero-plugin


text:
Add live-updatable VM tolerations

What this PR does
This PR will allow updating of the VMs' node tolerations which will live update the relevant VMI fields.
To have the tolerations actually reflected on the virt-launcher pod the VM owner will have to migrate the VM, only then the tolerations will be applied. Prior to this PR a VM owner had to restart the VM to apply tolerations.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Allow live updating VMs' tolerations

/cc

@xpivarc @fossedihelm I think I addressed all comments, please take a look.

/lgtm
Thanks

/test pull-kubevirt-e2e-k8s-1.31-sig-network

/retest

/retest

/hold
rebase needed

/lgtm
/unhold

/test pull-kubevirt-e2e-k8s-1.30-sig-operator

authors: acardace fossedihelm xpivarc

repo: kubevirt/kubevirt


text:
Fixed Openshift check for tests

What this PR does / why we need it:
Fixed Openshift check for tests, the /version/openshift endpoint doesn't exist anymore
Which issue(s) this PR fixes:
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1714991
Release note:
NONE

/retest

/cherrypick release-0.17

logs of running tests look good, the only test using this is skipped on os-3.11, but not on k8s-1.11, will merge

/retest

authors: fabiand slintes


text:
use canonical name for box

Signed-off-by: Raghavendra Talur rtalur@redhat.com

Hello contributor, thanks for submitting a PR for this project!
I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.
In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

Type ci test please on this PR to trigger automated tests for it.
Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically.
If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

Thanks @raghavendra-talur! I had to look up this setting to remember what it does. https://www.vagrantup.com/docs/vagrantfile/machine_settings.html
Just to be sure I understand: because we also specify config.vm.box_url, I understand this is basically an arbitrary value of our choosing?

@stu-gott

Just to be sure I understand: because we also specify config.vm.box_url, I understand this is basically an arbitrary value of our choosing?

the condition is like this
if vm.box exists
    skip download from given url
else
   download from given url and name as vm.box

As this box url is same as what we get when we do vagrant box add centos/7 and many users might already have it, I suggest we keep it same. If not, there would be two large files with different names but same content.

@rmohr objections against merging this?

ok to test

Thanks

authors: fabiand ovirt-infra raghavendra-talur rmohr stu-gott


text:
Fix DHCP server options to allow Windows accept offered IP

Server-ID Option 54 and Domain-Name-Server Option 6
should have length 4 instead of 16
Signed-off-by: Vladik Romanovsky vromanso@redhat.com

Should resolve #789

@cynepco3hahue can you please check if this fix is really fiing your issue?

authors: fabiand vladikr


text:
Point to the design proposal document in the contrib guide

Advertise the design proposal document in the contributors guide.
https://github.com/kubevirt/kubevirt/issues/8566
NONE

/retest-required

/retest

/retest

authors: acardace rthallisey


text:
e2e tests: Reuse VMIs in multiple tests

What this PR does / why we need it:
In Kubevirt e2e test suite, there are test suites/tests-batches where the exact same VMI is created before each test but each test asserts different things regardless of the VMI spec.
In other words, we could use a single VMI for all the tests in the batch.
Since Ginkgo v2.8.0, a new decorator was introduced ContinueOnFailure which enables an Ordered tests container (e.g: Context/Describeclouse that uses BeforeAll/AfterAll) to tolerate failing tests and continue.
(The default behavior for Ordered tests-containers was to exist early as soon as a test fails).
The new  ContinueOnFailuredecorator was the missing part in order to introduce tests that reuse VMIs.
Naturally reusing VMs enables cutting down the overall time of tests as we save the boot time each VM takes.
For example:
Assuming the global test suite setup and teardown takes 1 minute and VMIs boot time is 1 minute.
Given a batch of four tests that takes 5 minutes to finish, by reusing the same VMI we can cut down the time to 2 minutes.
This PR PoCs resuing VMIs in multiple tests and takes the network Expose tests suite as an example.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
This PR:

Bumps Ginkgo to v2.8.3 and Gomega to v1.27.1.
Introduces additional test-containers decorators in order to make the global-test-suite-clean-up skip VMIs and virt-launcher pods deletion (and enable reusing them for other tests).
Changes network Expose tests suite to reuse VMIs.

By having the combination of Ordered, ContinueOnFailure, retain-VMIs decorators and setting a VMI creation in a BeforeAll clause, its possible to reuse VMI in multiple tests:
Context("running virtual machine", Ordered, ContinueOnFailure, RetainVirtualMachineInstances, func(){
    var vmi *v1.VirtualMachineInstance
    BeforeAll(func() {
        vmi = createVMI()
    })
    It("case1", func(){
        Expect(vmi.Annotations).To(...)
    })
    It("case2", func(){
        Expect(vmi.Status).To(...)
    })
})

The last commit verifies:

The new ContinueOnFailure actually works and a falling test doesn't cause the whole suite to exit.
Failing test artifacts in an ordered test container are collected
It's for debugging and will be removed soon.

Release note:

/test pull-kubevirt-e2e-k8s-1.26-sig-network

/cc @EdDev @phoracek

/test pull-kubevirt-e2e-k8s-1.26-sig-network

/cc

/test pull-kubevirt-e2e-k8s-1.26-sig-network

/test pull-kubevirt-e2e-k8s-1.26-sig-network


text:
launcher, nic hotplug: use recommended attach device func

What this PR does / why we need it:
Reading the libvirt documentation it is clearly stated the AttachDeviceFlags command is preferred to the AttachedDevice call - [0]:

For compatibility, this method can also be used to change the media in an
existing CDROM/Floppy device, however, applications are recommended to use the virDomainUpdateDeviceFlags method instead.

[0] - https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainAttachDevice
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cc @ormergi

/sig network

/lgtm

authors: AlonaKaplan maiqueb


text:
Fix kubelet arguments and unix socket protocol 3.0

Remove unsupported --require-kubeconfig argument deprecated in Kubernetes (and removed in 1.10)

Add protocol to the unix socket location, suggested by Kubelet 1.10:

    [Experimental] The endpoint of remote runtime service. Currently unix socket is supported on Linux, and tcp is supported on windows.  Examples:'unix:///var/run/dockershim.sock', 'tcp://localhost:3735' (default "unix:///var/run/dockershim.sock")

Backport of https://github.com/kubic-project/salt/pull/562

 Bug 1094217 - The kubelet on Kubernetes 1.10 refuses to start if --require-kubeconfig is provided

repo: kubic-project/salt


text:
UnhandledPromiseRejectionWarning: Error: ENOENT

Describe the bug
Html report not generated (others are)
To Reproduce
Steps to reproduce the behavior:
 $ pwd
/tmp
$ npm install jscpd
npm WARN saveError ENOENT: no such file or directory, open '/tmp/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/tmp/package.json'
npm WARN tmp No description
npm WARN tmp No repository field.
npm WARN tmp No README data
npm WARN tmp No license field.

+ jscpd@3.3.0-rc.5
updated 1 package and audited 987 packages in 1.7s

4 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

$ node node_modules/.bin/jscpd --reporters html ./node_modules/jscpd/
Clone found (javascript):
 - node_modules/jscpd/dist/init/index.js [1:1 - 6:25]
   node_modules/jscpd/dist/print/index.js [1:1 - 6:27]

(node:12907) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/tmp/node_modules/@jscpd/finder/dist/reporters/../../html/report.pug'
    at Object.openSync (fs.js:439:3)
    at Object.readFileSync (fs.js:344:35)
    at handleTemplateCache (/tmp/node_modules/pug/lib/index.js:214:37)
    at Object.exports.compileFile (/tmp/node_modules/pug/lib/index.js:356:10)
    at HtmlReporter.report (/tmp/node_modules/@jscpd/finder/dist/reporters/html.js:14:38)
    at reporters.forEach (/tmp/node_modules/@jscpd/finder/dist/in-files-detector.js:76:26)
    at Array.forEach (<anonymous>)
    at detect.then.then (/tmp/node_modules/@jscpd/finder/dist/in-files-detector.js:75:28)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
(node:12907) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5205)
(node:12907) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Expected behavior
./report/jscpd-report.html must exists
Desktop (please complete the following information):

OS: Ubuntu 19.10 , kernel 5.3.0-46-generic, x86_64
NodeJS Version: 10.15.2
jscpd version 3.3.0-rc.5

Additional context
On jscpd v 3.2.1 html report is generated.

thank you for the report, investigating the issue

fixed at jscpd@3.3.0-rc.6

authors: alinsoare kucherenko

repo: kucherenko/jscpd

license: mit


text:
Flaky instance-controller-param-change-custom-trigger

Needs investigation https://circleci.com/gh/kudobuilder/kudo/5433?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

The bug hasn't surfaced since so we declare it squashed 🐛

authors: alenkacz zen-dog

repo: kudobuilder/kudo


text:
Is the project still alive/maintained?

Dear kuttl team,
I heard about this great project by looking at Viktor's video (https://youtu.be/ZSTQQNu4laY?si=INP-j45zcDrJUB7I) and wanted to start using it to test our Kubernetes manifests. As mentioned in the video, it looks like the project is not actively maintained anymore. Is it really the case? What is the current status?
Thanks in advance for your response!

@tgdfool2, thanks for reaching out. Kuttl is a great tool, and we still use it in all our operators. But I would say that the current status is that it's little/no activity and unmaintained. It has some nasty bugs and many important features are missing.
The Kyverno project tried to involve at one point, but with just a single (and busy) Kuttl maintainer (@kensipe), it was impossible to satisfy a busy and fast-moving project as Kyverno. This resulted in a friendly fork being created in Kyverno org: https://github.com/kyverno/kuttl where the Kyverno team fixed bugs and added features they needed to test Kyverno.
I know that @eddycharly, one of the Kyverno maintainers has worked on a replacement tool. He can share details if/when it's ready tobe shared. But I still think/hope everyone is eager to sort things out and join forces in something based on the ideas behind Kuttl. 🚀

Thanks @erikgb for all the details. Let's wait for @eddycharly's feedback. I also hope that this will result in a common solution that will fit most of the people needs.

I think this is the project @erikgb mentioned: https://github.com/kyverno/chainsaw

I think the project has been picking up lately. I notice that @porridge is doing a great job pulling the project out of the trench.

The biggest problem at the moment seems to be lack of active reviewers with write permission to the repo (such that approvals satisfy the pre-merge check), which is a bit of catch-22. I recently started to try and review+merge contributions, but my PRs have been pending a review for a while...

I've been able to make a release recently, so I think this ticket can be closed.
OTOH for completeness I should probably mention that https://github.com/kyverno/chainsaw sprang to existence which has some nice features.

repo: kudobuilder/kuttl


text:
Add Operator Labels to OperatorVersions

To support queries like:
kubectl get frameworkversions -l framework=flink

with the name change it should look like
kubectl kudo get operatorversions -l operator=flink

authors: kensipe runyontr

repo: kudobuilder/operators


text:
求助：数据库问题

能否提供你的环境变量 .env 的内容？
我猜测你数据库可能添加了 ssl 验证，因此你可能需要到 database.config.ts 中添加 ssl: false 来解决。

这个问题我没遇到过，不过看样子应该是 Mysql 的服务所导致的，你可以添加 ssl: false 或 insecureAuth: true 这两个属性来尝试解决。

话说为什么不用mysql2去连接数据库，而选择了mysql这个包呢呢？

话说为什么不用mysql2去连接数据库，而选择了mysql这个包呢呢？

这是个好建议，至于为何选择mysql，是因为本项目我是从旧版本不断演进的，我主要更新了几个核心的包，而由于数据库依赖几乎怎么改动，在意一个 mysql 版本。
不过官方也推荐安装 mysql2，该项目后续会对此有所改进。

repo: kuizuo/nest-vben-admin


text:
Add default value for WikiUrlEndingBlockList

Fixes "List of all blocks" link leading to the main page by default

Thanks! Merged in :)

authors: fumple kulttuuri

repo: kulttuuri/DiscordNotifications


text:
feat: refreshes sidebar counters periodically

Adds a polling utility for refreshing the counters in the sidebar periodically. The polling interval is set to 10 seconds.
Resolves #327.
Signed-off-by: Philipp Rudloff philipp.rudloff@konghq.com

Is there anyway to skip the polling if the tab is not active? This is just to avoid hammering the api for no reason.

Yep, I can add logic for this. We could also use exponential back off (while the tab is active) if we want.

I don't think exponential backoff is what we want though (There's no reason less change happens because you've been on the tab for a longer time).

I don't think exponential backoff is what we want though

I agree; I wasn’t planning on adding it anyway.
I’ve added the logic now for disabling the polling while the window isn’t active.

authors: kleinfreund lahabana

repo: kumahq/kuma-gui


text:
Reformatting descriptions for the organization of multiple Prometheus instances in multi-zone environments

Reformatting descriptions for the organization of multiple Prometheus instances in multi-zone environments.

Thx for the contrib!

authors: GigaPrimatus lahabana

repo: kumahq/kuma-website


text:
Add syntax highlighting to graphql-tools

Please add support for highlighting for graphql-tools, or add a settings like EmbeddedQueryParser in .gqlconfig with startTag and endTag to enable highlighting.
The convention in graphql-tools is to declare types like this:
const typeDefs = `
  interface Node {
    id: Int!
  }
`;

@klis87 the .gqlconfig file is something you have to edit. To add support, modify the example gqlconfig file in the readme with a regex which would match your file. In this case, it'll be:
/* .gqlconfig */
{
  ...
  query: {
    files: [
      {
        match: 'ui/src/**/*.js',
        parser: ['EmbeddedQueryParser', { startTag: 'const typeDefs = `', endTag: '`' }],
      }
    ]
  }
}
}

I'm not familiar with gqltools, but I don't think adding support for syntax-highlighting might not be trivial for this kind of code - this plugin will have to go through every template string in JS/JSX files and attempt to highlighted it as gql - I don't think that's possible with vscode.

@kumarharsh It is possible because gql tags for react-apollo client are highlighted, so doing the same for typeDefs must be also possible.

@klis87 - yes that is possible. But I feel like it can cause issues:

Is it guarenteed that users will always write:

const typeDefs = `
   ...
`

and not:
const type_defs = `
   ...
`

or any other variation?

What if someone has to put two sets of graphql queries in a file? They can't use the typeDefs variable, because that's already used.

const typeDefs = `
  { ... query 1 }
`;
...

const typeDefs2 = ` // won't highlight
  { ... query 2 }
`;

Granted, the gql and Relay.QL tags can also suffer from this problem:
import Relay_XX from 'react-relay';
const frag = Relay_XX.QL`
  fragment on ... {}
`

but I feel that this convention doesn't cause clashes for the code below it. On the other hand, the graphql-tools convention seems flaky to me, as I've tried to highlight here.
But, I'm not aware of how the code for graphql-tools looks like, so maybe my reservations might not matter in reality. What are your thoughts?

I agree with you that it might be dangerous to assume typeDefs convention. But would it be possible to make code highlighting configurable? for example as vscode setting like:
GQLCodeHighlitingPatterns: [
  {
    "path": "src/**/*.js",
    "startTag": "const typeDefs = `",
    "endTag": "`"
  }
]

Then it would be flexible and everyone could set things up to a specific tools/frameworks.

I don't think vscode allows that. Because the syntaxes are defined in JSON, and the config file can't have a say in that. I think it'll be super hard to support it and still retain any amount of flexibility.

I found a related issue on VSCode pertaining to this: https://github.com/Microsoft/vscode/issues/130#issuecomment-325005190

Ohhh, pity. So there is nothing what could we do? Could we add typeDefs as hardcoded rule in graphql syntax or you would prefer not to?

I'd prefer to wait for a better solution to this, or if more people are interested, then maybe we can figure out an approach which works best.
One question: Do you use webpack in your code?

Ok, so let's wait, Thank you for custom gql tag, this would actually work :)
Btw, I guess this library won't work for dynamic types right? Which you set programatically. If that is so, would you consider adding ability to introspect schema from a graphql server endpoint? In a similar fashion like in apollo-codegen, which can generates flow types from graphql endpoint.

Yes, that is one thing we might add (possibly). There is an open issue for apollo support in the gql library where you can give your inputs.

repo: kumarharsh/graphql-for-vscode


text:
where is openvpn status file located ?

when we run openvpn_exporter --help
we get
-openvpn.status_paths string
Paths at which OpenVPN places its status files.
What I want to know when you say Path at which OpenVPN places its status files , Do you mean OpenVPN Exporter ?

What for OpenVPN Access server? Because we have a setup with 2 servers that have one Database behind them.

authors: nickjmv sanfx


text:
permission denied / file not found

Hey,
I installed everything according to your instructions without noticing any errors, but I cannot get chipseq.py to work. If I use fastq or bam as input, I get an error of the following form
fork/exec /media/nico/data/home2/projects/macrophages/chip_ana2/8-ENCODE-pipeline/chipseq.bds.20171207_115700_844/task.postalign_bam.dedup_bam_1_rep1.line_155.id_10.sh: permission denied
If I use peaks as input, the error has the following form:
Error (/home/nico/TF_chipseq_pipeline/modules/input_peak.bds, line 31, pos 33): 		File not found!
The files pass the initial check, though.
I don't know what to do next.
Here is the stderr output when running with a fastq and with a peak input.
log-17_12_07-11:56:57.txt
log-17_12_07-11:54:38.txt

Please check permission for directories and files on your pipeline output
directory (/media/nico/data/home2/projects/macrophages).
Jin
On Thu, Dec 7, 2017 at 3:14 AM, michdass notifications@github.com wrote:

Hey,
I installed everything according to your instructions without noticing any
errors, but I cannot get chipseq.py to work. If I use fastq or bam as
input, I get an error of the following form
fork/exec /media/nico/data/home2/projects/macrophages/chip_
ana2/8-ENCODE-pipeline/chipseq.bds.20171207_115700_844/
task.postalign_bam.dedup_bam_1_rep1.line_155.id_10.sh: permission denied
If I use peaks as input, the error has the following form:
Error (/home/nico/TF_chipseq_pipeline/modules/input_peak.bds, line 31,
pos 33): File not found!
The files pass the initial check, though.
I don't know what to do next.
Here is the stderr output when running with a fastq and with a peak input.
log-17_12_07-11:56:57.txt
https://github.com/kundajelab/chipseq_pipeline/files/1538790/log-17_12_07-11.56.57.txt
log-17_12_07-11:54:38.txt
https://github.com/kundajelab/chipseq_pipeline/files/1538791/log-17_12_07-11.54.38.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kundajelab/chipseq_pipeline/issues/23, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AIOd_A7Xnbn0g-ZB41X4aKqDW2EDe_jKks5s98iIgaJpZM4Q5YSC
.

the directory is drwxrwxr-x
and the files are -rw-rw-r--
the bam files are even -rwxrwxrwx

What about pipeline's repo directory (chipseq_pipeline/)?

TF_chipseq_pipeline/ has drwxrwxr-x as well. I'm assuming the Aquas-Pipeline directory does not have to be put into a specific place? It's right now in my home directory.

Gesendet: Samstag, 09. Dezember 2017 um 19:21 Uhr
Von: "Jin Lee" notifications@github.com
An: kundajelab/chipseq_pipeline chipseq_pipeline@noreply.github.com
Cc: michdass nico.barth@gmx.net, Author author@noreply.github.com
Betreff: Re: [kundajelab/chipseq_pipeline] permission denied / file not found (#23)
What about pipeline's repo directory (chipseq_pipeline/)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I am sorry for long delay.
Permissions on the pipeline source directory looks okay, but I suspect that
you still have a permission issue on your output directories. Our pipeline
makes many temporary files and directories under your working directory
(it's not -out_dir but where you run the pipeline command line). Does your
cluster limit file/dir permission on your working directories?
Please run the following command lines and post outputs here.
$ touch /media/nico/data/home2/projects/macrophages/chip_
ana2/8-ENCODE-pipeline/file_permission_test
$ mkdir /media/nico/data/home2/projects/macrophages/chip_
ana2/8-ENCODE-pipeline/dir_permission_test
$ touch /media/nico/data/home2/projects/macrophages/chip_
ana2/8-ENCODE-pipeline/dir_permission_test/file_permission_test
Thanks,
Jin
On Mon, Dec 11, 2017 at 1:06 AM, michdass notifications@github.com wrote:

TF_chipseq_pipeline/ has drwxrwxr-x as well. I'm assuming the
Aquas-Pipeline directory does not have to be put into a specific place?
It's right now in my home directory.
Gesendet: Samstag, 09. Dezember 2017 um 19:21 Uhr
Von: "Jin Lee" notifications@github.com
An: kundajelab/chipseq_pipeline chipseq_pipeline@noreply.github.com
Cc: michdass nico.barth@gmx.net, Author author@noreply.github.com
Betreff: Re: [kundajelab/chipseq_pipeline] permission denied / file not
found (#23)
What about pipeline's repo directory (chipseq_pipeline/)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kundajelab/chipseq_pipeline/issues/23#issuecomment-350663113,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIOd_KTeQVk7mZDYQcOtf7D9mTrKeGgXks5s_PCggaJpZM4Q5YSC
.


text:
🎮 Game Request
Astray is a 3D Adventure Game in which you have to move the ball inside the Maze and get out of it to reach the destination and win the game.
Point down the features
Visuals: The game is presented in a 3D graphical environment, allowing players to experience immersive gameplay.
Controls: The controls are designed to provide a responsive and intuitive way for players to maneuver the ball through the maze.
Obstacles and Challenges: The maze may contain obstacles such as walls, moving platforms, gaps, locked doors, and other puzzles that require the player to solve them to progress.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

/assign

Hey @linga66 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @linga66 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

repo: kunjgit/GameZone


text:
[Enhancement]: In Tilting Maze adding a restart button and enhancing the text size and style

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
Game enhancement
In Tilting maze , There is no restart button and text are small with no style.

Describe the solution you'd like
Solution steps
I will add restart button and enchance the text size and style.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @jaydeep099 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

/assign

Hey @jaydeep099 ! , This issue is already assigned to @dnyandeepchute. 💗
You can work on other issues 🚀
If there is anything wrong you can contact us on Discord🕹👀

@kunjgit i have created pull request i just forgot to write /assign

Hey @jaydeep099 ! , This issue is already assigned to @dnyandeepchute. 💗
You can work on other issues 🚀
If there is anything wrong you can contact us on Discord🕹👀

Hey @jaydeep099 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

authors: dnyandeepchute jaydeep099 kunjgit


text:
[New game]: QR CODE Generator

🎮 Game Request
Game logic and basic description:
A simple web application which will generate a QR Code.
You Can Create Your Name Number QR codes
Point down the features
Game points :
A simple web application which will generate a QR Code.
You Can Create Your Name Number QR codes**

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @codewithganeshhh !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @codewithganeshhh!
We are already having a similar game request in #4269 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.

Hey @codewithganeshhh ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

authors: codewithganeshhh kunjgit


text:
DOTS GAME

PR Description 📜
issue no:#3074
i have added the DOTS game wherein the center dot has to shoot other upcoming dots to gain points .the other dots are of any shape and size & if they touch the center point or the player the game end .Itt also keep score for the game starting off with the initial score of 0

[✔ ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[✔ ] I have performed a self-review of my own code or work.
[✔ ] I have commented my code, particularly in hard-to-understand areas.
✔[ ] My changes generates no new warnings.
[ ✔] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[✔ ] I have added screenshot for website preview in assets/images
[✔ ] I have added entries for my game in main README.md
[ ✔] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[✔ ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @vedanshipathak ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

authors: kunjgit vedanshipathak


text:
New Game

PR Description 📜
Introducing a new, engaging, and educational game: Currency Conversion! This game is designed to be user-friendly, providing both fun and valuable learning experiences for players.
In this game, users can explore and understand currency exchange rates in an interactive and enjoyable way. The interface is designed to be intuitive and accessible, making it easy for players of all ages to participate and learn.
Fixes https://github.com/kunjgit/GameZone/issues/3584
Mark the task you have completed ✅
[x ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ x] I have performed a self-review of my own code or work.
[x ] I have commented my code, particularly in hard-to-understand areas.
[x ] My changes generates no new warnings.
[x ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x ] I have added screenshot for website preview in assets/images
[x ] I have added entries for my game in main README.md
[x ] I have added README.md in my folder
[x ] I have specified the respective issue number for which I have requested the new game.
Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @kashisharora9462 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @kashisharora9462,
Please make sure to link the relevant issue using the appropriate syntax, such as "#issueNumber" 👀.
Follow the proper guideline and make a new PR again 😀.
Happy Hacking 💗

Thank you  @kashisharora9462 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


text:
new game added

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes # <your_issue_number>

Mark the task you have completed ✅

[ ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ ] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My changes generates no new warnings.
[ ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ] I have added screenshot for website preview in assets/images
[ ] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[ ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @sagnik3788 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @sagnik3788 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


text:
Build an example implementation inside of Kurtosis

Will give us something that we can run as a very basic sanity check in CI
Serve as an in-repo example we can point users to to demonstrate how to implement the library
As we're developing, shortens the dev cycles by allowing us to sanity-test our work without needing to propagate the library to Ava

Related to #123

repo: kurtosis-tech/kurtosis


text:
Track Cadre Payments - Bug

Given a Cadre whose Per Diem's have been paid, and has a zero for food or lodging. On Cadre Payments page, you try to Quick (Pencil) edit the cadre's Payment. The per diem fields are disabled, but validation requires you to put a zero in the empty per diem field(s).
Need to change to display a zero for fields with an actual zero in the database. Should also prevent validating disabled fields.

Changed table.ts to display zeros in input cells instead of empty string.
Changed Payments and Per Diems pages to not validate disabled fields on Update click.

repo: kutting/msexcel-builder


text:
Symmetric_dense_st_matrix

Создать файл source/symmetric_dense_st_matrix.cpp.
В нём разместить класс ogxx::Symmetric_dense_st_matrix<ST> : public ogxx::St_matrix<ST>.
В качестве хранилища использовать vector<ST>.
Матрица квадратная и симметрическая, поэтому храним только половину. В случае вызова reshape с не квадратным размером  можно бросить исключение.
Реализовать методы:

shape()
reshape(Matrix_shape) (о содержимом можно не заботиться, т.е. можно использовать vector::resize)
get(Matrix_index position)
set(Matrix_index position, bool value)
flip(Matrix_index position)
fill(bool value)

Перед началом работы не забудьте обновить свою ветку по main (через rebase).

Делать Rebase было страшно.
Кажется, что получилось.

Если делаете с помощью github desktop, то там можно вместо rebase выбрать update.
Если делаете из консоли, то можно merge:
git checkout pm2-martianov-k-s
git merge main

Интерфейс St_matrix обновился, но из добавленных методов сейчас можно сделать только copy. Остальные реализовать заглушками.

Некоторые методы были удалены?
Их надо удалить?

Нет.

Я написал оператор copy. Поправил формулу в get.

Да, надо St_matrix. Конструктора пока нет. St_matrix -- абстрактный класс, нужны фабричные методы, чтобы создавать конкретные объекты того или иного типа. Пока Dense_st_matrix не готов полностью (хотя почти готов).

Задание выполнено, код добавлен в main.

repo: kuvshinovdr/OGxx


text:
[multi-chat] fix: trust all proxies.

The original setting will cause the front end to only generate http:// links, and requests for these resource files will be blocked by the browser.

Even if the environment variable has been set, it will be ignored by Laravel.

After this setting, Kuwa works well under https, but I am not good at PHP. Please re-evaluate whether this modification is appropriate.

Hi @Phate334,
I doubt that Laravel will not respect environment variables in docker.
Could you try to solve the issue by changing APP_URL in docker/multi-chat/app.env and rebuilding the image?
Thanks.

Could you try to solve the issue by changing APP_URL in docker/multi-chat/app.env and rebuilding the image?

same problem on app.env

Do Kuwa or Laravel have any solutions to set up custom certificates for TLS? Laravel cannot generate HTTPS URLs when the reverse proxy forwards to Kuwa on port 80.
https://laravel.com/docs/10.x/requests#configuring-trusted-proxies
====
I use mkcert and the Caddy server for debugging.

Caddyfile

kuwa.localhost {
  tls /kuwa-cert/kuwa.localhost.pem /kuwa-cert/kuwa.localhost-key.pem

  reverse_proxy host.docker.internal:8080
}

compose.yaml

services:
  caddy:
    image: caddy:2.8.4-alpine
    restart: unless-stopped
    ports:
      - "80:80"
      - "443:443"
    extra_hosts:
      - "host.docker.internal:host-gateway"
    volumes:
      - ./kuwa-cert:/kuwa-cert
      - ./Caddyfile:/etc/caddy/Caddyfile

To configure custom TLS certificates in the Dockerized version of Kuwa, you can modify the Nginx configuration within the "web" container. Here's an example:
diff --git a/docker/web/templates/default.conf.template b/docker/web/templates/default.conf.template
index 56319a66..37076a67 100644
--- a/docker/web/templates/default.conf.template
+++ b/docker/web/templates/default.conf.template
@@ -2,6 +2,22 @@ server {
     listen 80;
     listen [::]:80;
     server_name ${DOMAIN_NAME};
+
+    # Redirect HTTP to HTTPS
+    return 301 https://$host$request_uri;
+}
+
+server {
+    listen 443 ssl;
+    listen [::]:443 ssl;
+    server_name ${DOMAIN_NAME};
+
+    # SSL Configuration
+    ssl_certificate /etc/letsencrypt/live/${DOMAIN_NAME}/fullchain.pem; # Replace with your certificate path
+    ssl_certificate_key /etc/letsencrypt/live/${DOMAIN_NAME}/privkey.pem; # Replace with your private key path
+    ssl_protocols TLSv1.2 TLSv1.3;
+    ssl_ciphers HIGH:!aNULL:!MD5;
+
     root /app/public;

     add_header X-Frame-Options "SAMEORIGIN";

While this pull request's trusted proxy configuration is valuable for scenarios using cloud load balancers, we can enhance its adaptability. To ensure broader applicability, I plan to make the trusted proxy configurable via an environment variable after this pull request is merged.
Thank you for your contribution!

To ensure broader applicability, I plan to make the trusted proxy configurable via an environment variable after this pull request is merged.

That's great.

repo: kuwaai/genai-os


text:
V2: CountNonRoot query is wrong in the V2 benchmark

The CountNonRoot query seems to have changes from v1 to v2. It now seems incorrect in code?
Check this line:
https://github.com/kuzeko/graph-databases-testsuite/blob/133116cbcc1c61cf088441e1b5907c4fbd4531f1/SHELLS/common/src/main/java/com/graphbenchmark/queries/vldb/CountNonRoot.java#L23
While, in the previous version of the benchmark the query was defined as:
https://github.com/kuzeko/graph-databases-testsuite/blob/217cd37d1037bbbfd53b89aab0391b1abcca1590/runtime/tp3/queries/find-non-root-nodes.groovy#L4
To me, the v1 version is the correct one. However, when the benchmark runs, the v2 query definition seems to not be used. And instead the v1 version is run on databases. For instance, on the air-routes.json dataset on neo4j I get the following log:
052dcde0-2407-4412-ac21-1794c270b960;240;Neo4jShell;air-routes.json;dbf21247-0b6b-4123-aedd-a67968a9ba8d;;queries.vldb.CountNonRoot;vldb19-7-dirty;1800;SINGLE_SHOT;[{}];OK;--;117ms;Nodes: 3497;{"invocation":0}

It find 3497 nodes. When I do the exact same query supposed run by the benchmark on the same dataset with the same shell (gts.E().inV().dedup().count().next()) I found 3705 nodes, a different results. Yet, when I run the query g.V.out.dedup().count().next() I found the correct result of 3497 nodes.
So, this means that the query defined in the file CountNonRoot.java is not the one beeing run.

Was using different samples files...

repo: kuzeko/graph-databases-testsuite


text:
demo web page is not working

Hello,
The link to the demo web is not working. It would be nice to see it. Thank you :)

Hi, please find it here. I have updated the README as well. I changed my GitHub username and the redirect probably expired.

authors: ferugit kwatcharasupat

repo: kwatcharasupat/bandit


text:
Segmentation fault when saving

Hello!
After klusta MyRec.prm, I can load the GUI with phy kwik-gui MyRec.kwik and play w/ the data, however, when I press Ctrl+S I get a segmentation fault, with no other apparent error in debug mode, or in the log.
I can reproduce this with Klusta example data:
$ pip install git+https://github.com/kwikteam/phy git+https://github.com/kwikteam/phy-contrib --upgrade
[...]
Successfully installed phy-1.0.9 phycontrib-1.0.15

$ klusta hybrid_10sec.prm
[...]
22:17:39 [I] klustakwik Trying to split clusters
22:17:40 [I] klustakwik No points changed, previous step was full and did not split, so finishing.
22:17:40 [I] launch:131           The automatic clustering process has finished.
22:17:40 [I] launch:268           Save the clustering to `hybrid_10sec.kwik`.
22:17:40 [I] model:1085           Save the Kwik file at `/home/malfatti/TestKlusta/hybrid_10sec.kwik`.
22:17:40 [I] launch:290           Clustering done!

$ phy kwik-gui hybrid_10sec.kwik --debug
# GUI loads correctly, besides the Qt warning
QGtkStyle could not resolve GTK. Make sure you have installed the proper libraries.
22:25:11 [D] model:671            Enable waveform filter.
22:25:11 [D] model:467            Loading traces: hybrid_10sec.dat
22:25:11 [D] model:1067           Kwik file `/home/malfatti/TestKlusta/hybrid_10sec.kwik` loaded.
22:25:11 [D] context:67           Initialize joblib cache dir at `/home/malfatti/TestKlusta/.phy`.
22:25:11 [D] context:91           Load memcache for `phycontrib.kwik.gui.get_best_channels`.
22:25:11 [D] context:91           Load memcache for `phycontrib.kwik.gui.get_probe_depth`.
22:25:11 [D] context:91           Load memcache for `phycontrib.kwik.gui._get_mean_masks`.
22:25:11 [D] context:91           Load memcache for `phycontrib.kwik.gui._get_mean_waveforms`.
22:25:11 [D] context:148          The file `/home/malfatti/TestKlusta/.phy/new_cluster_id.pkl` doesnt exist.
22:25:11 [D] context:134          Save data to `/home/malfatti/TestKlusta/.phy/spikes_per_cluster.pkl`.
22:25:11 [D] config:46            Load config file `/home/malfatti/.phy/phy_config.py`.
22:25:11 [D] gui:432              Load the GUI state from `/home/malfatti/.phy/KwikGUI/state.json`.
22:25:11 [D] gui:173              Load the geometry state.
# Then I just selected a cluster and pressed Ctrl-S
22:25:13 [D] supervisor:342       Select cluster(s): 0.
Segmentation fault

$ cat phy.log
2017-05-31 22:25:11 [D] model:671            Enable waveform filter.
2017-05-31 22:25:11 [D] model:467            Loading traces: hybrid_10sec.dat
2017-05-31 22:25:11 [D] model:1067           Kwik file `/home/malfatti/TestKlusta/hybrid_10sec.kwik` loaded.
2017-05-31 22:25:11 [D] context:67           Initialize joblib cache dir at `/home/malfatti/TestKlusta/.phy`.
2017-05-31 22:25:11 [D] context:91           Load memcache for `phycontrib.kwik.gui.get_best_channels`.
2017-05-31 22:25:11 [D] context:91           Load memcache for `phycontrib.kwik.gui.get_probe_depth`.
2017-05-31 22:25:11 [D] context:91           Load memcache for `phycontrib.kwik.gui._get_mean_masks`.
2017-05-31 22:25:11 [D] context:91           Load memcache for `phycontrib.kwik.gui._get_mean_waveforms`.
2017-05-31 22:25:11 [D] context:148          The file `/home/malfatti/TestKlusta/.phy/new_cluster_id.pkl` doesnt exist.
2017-05-31 22:25:11 [D] context:134          Save data to `/home/malfatti/TestKlusta/.phy/spikes_per_cluster.pkl`.
2017-05-31 22:25:11 [D] config:46            Load config file `/home/malfatti/.phy/phy_config.py`.
2017-05-31 22:25:11 [D] gui:432              Load the GUI state from `/home/malfatti/.phy/KwikGUI/state.json`.
2017-05-31 22:25:11 [D] gui:173              Load the geometry state.
2017-05-31 22:25:13 [D] supervisor:342       Select cluster(s): 0.

The kwik file loads ok in ipython, but no changes were saved to the file.
Does anyone has/had this problem?
Cheers

Hi, that's weird. Does it crash if you don't select any cluster before saving? What is the version of all of your Python packages in your environment (in particular h5py)?

Hej :) Yes, it crashes just opening and saving, with almost the same log (except the "Select cluster(s)" line).
I installed Klusta through conda, according to instructions in the README.md, and upgraded phy to development version. Here are the *-info files:
$ cd $KlustaEnv/lib/python3.5/site-packages/

$ ls *info -d
click-6.7.dist-info
cookies-2.2.1.dist-info
cycler-0.10.0-py3.5.egg-info
Cython-0.25.2-py3.5.egg-info
decorator-4.0.11-py3.5.egg-info
h5py-2.7.0-py3.5-linux-x86_64.egg-info
ipython-6.0.0-py3.5.egg-info
ipython_genutils-0.2.0-py3.5.egg-info
jedi-0.10.2-py3.5.egg-info
joblib-0.11.dist-info
klusta-3.0.16.dist-info
klustakwik2-0.2.6.dist-info
matplotlib-1.5.1-py3.5.egg-info
numpy-1.11.3-py3.5.egg-info
pexpect-4.2.1-py3.5.egg-info
phy-1.0.9-py3.5.egg-info
phycontrib-1.0.15-py3.5.egg-info
pickleshare-0.7.4-py3.5.egg-info
pip-9.0.1-py3.5.egg-info
prompt_toolkit-1.0.14-py3.5.egg-info
ptyprocess-0.5.1-py3.5.egg-info
py-1.4.33.dist-info
Pygments-2.2.0-py3.5.egg-info
PyOpenGL-3.1.0.dist-info
pyparsing-2.1.4-py3.5.egg-info
pytest-3.0.7.dist-info
python_dateutil-2.6.0-py3.5.egg-info
pytz-2017.2-py3.5.egg-info
requests-2.14.2.dist-info
responses-0.5.1.dist-info
scipy-0.19.0-py3.5.egg-info
simplegeneric-0.8.1-py3.5.egg-info
six-1.10.0-py3.5.egg-info
tqdm-4.11.2.dist-info
traitlets-4.3.2-py3.5.egg-info
vispy-0.4.0.dist-info
wcwidth-0.1.7-py3.5.egg-info
wheel-0.29.0-py3.5.egg-inf

Thanks for your response :D

Hej again,
I tried the simplest of things: moved my ~/.gtkrc-2.0 and ~/.config/{Trolltech.conf,gtk-2.0,gtk-3.0} files to a backup folder and... voilà! The QGtkStyle warning disappeared and data is saved without errors.
I would like to ask you to keep this issue open for now. In the next days I'll investigate what setting exactly will generate this segmentation fault. Then, I'll report back and we close it.
Thanks and sorry for the noise :)

Happy to hear that!

Hej! Sorry for the huge delay.
Just to report, in case someone have the same problem. After some digging it turns out that, at least in my gentoo system, using any GTK theme as QT theme (using qt5ct) makes the segmentation fault to happen again. Choosing "Fusion", for example, fix it.
Cheers :)

authors: malfatti rossant

repo: kwikteam/phy


text:
Codes wanted

I have read your paper in IROS 2020. It is an amazing work!
Could you share the code as soon as possible? I can't wait to reproduce your job now.
Thanks a lot!

use wechat , silin @lisilin013

Thanks for your interests of our work. The code has been released. Closed.

authors: crankler kxhit lisilin013


text:
Compare with GPT-4 Advanced Data Analysis (integrating with Python)

This wasn't tested in the original paper, but I've found GPT+4 with Python (Advanced Data Analysis) is often capable of solving these kinds of problems by writing a Python program that finds the solution in the search space:

https://chat.openai.com/c/010d05d3-63f4-4825-9d4c-4f3bead36e7b

Here, GPT wrote a Python program that tries all permutations of the expression (A^B)^(C^D), where "^" are one of the four basic arithmetic operators (+,-,*,/) and A, B, C, D are a permutation of the given numbers.
It then found the solution  (14 - 8) * (8 / 2) = 24, which is correct. And this is in a relatively small number of tokens (input = 112 tokens, output = 512 + prompt for Advanced Data Analysis >= 624 tokens), whereas AoT would likely require far more (the openai.logs file in this repo, for instance, is 15 306 tokens).

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

I'm not sure this issue is helpful given that there some cases where Algorithm of Thoughts may likely be better than OpenAI's current offerings (for now). Instead of finding where AoT is worse it's better to fund searches for where it is better.

authors: aadnk robinsonkwame

repo: kyegomez/Algorithm-Of-Thoughts


text:
[BUG]  bitlinear fix

beta and gamma sizes to be (1, weight.shape[0], not (weight.shape[0], 1) ???

Can you elaborate please? Can you go deeper?

I encountered the same problem. When passing a tensor of 4,2 int to a BitLinear(2,8), I get an error at the line
return x * self.gamma * self.beta / self.Q_b
Saying
"
Exception has occurred: RuntimeError
The size of tensor a (4) must match the size of tensor b (8) at non-singleton dimension 0
File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\bitlinear.py", line 112, in dequantize_activations_groupwise
return x * self.gamma * self.beta / self.Q_b
File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\bitlinear.py", line 137, in forward
output = self.dequantize_activations_groupwise(output)
File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\xor_test_bitlinear.py", line 20, in forward
x = self.layer1(x)
File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\xor_test_bitlinear.py", line 39, in
outputs = model(inputs)  # Forward pass
RuntimeError: The size of tensor a (4) must match the size of tensor b (8) at non-singleton dimension 0
"
I think the shapes of the self.gamma and self.beta shapes are wrong. Gamma is initialized based on # output neuron shape but is set based on batch size

I encountered the same problem. When passing a tensor of 4,2 int to a BitLinear(2,8), I get an error at the line return x * self.gamma * self.beta / self.Q_b Saying " Exception has occurred: RuntimeError The size of tensor a (4) must match the size of tensor b (8) at non-singleton dimension 0 File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\bitlinear.py", line 112, in dequantize_activations_groupwise return x * self.gamma * self.beta / self.Q_b File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\bitlinear.py", line 137, in forward output = self.dequantize_activations_groupwise(output) File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\xor_test_bitlinear.py", line 20, in forward x = self.layer1(x) File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\xor_test_bitlinear.py", line 39, in outputs = model(inputs) # Forward pass RuntimeError: The size of tensor a (4) must match the size of tensor b (8) at non-singleton dimension 0 " I think the shapes of the self.gamma and self.beta shapes are wrong. Gamma is initialized based on # output neuron shape but is set based on batch size

I think so, but I am confused that since self.gamma is related to activations while self.beta is related to weights, should we explicitly broadcast these two matrices [quantization about activations ('group_size = x.shape[0] // self.num_groups') should be grouped in the dim=1(x.shape[1]) because of the batch_size?], thus 'x * self.gamma * self.beta' in the dequantization process can do hadamard product? If I make wrong, pls point out. Thanks.

I encountered the same problem. When passing a tensor of 4,2 int to a BitLinear(2,8), I get an error at the line return x * self.gamma * self.beta / self.Q_b Saying " Exception has occurred: RuntimeError The size of tensor a (4) must match the size of tensor b (8) at non-singleton dimension 0 File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\bitlinear.py", line 112, in dequantize_activations_groupwise return x * self.gamma * self.beta / self.Q_b File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\bitlinear.py", line 137, in forward output = self.dequantize_activations_groupwise(output) File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\xor_test_bitlinear.py", line 20, in forward x = self.layer1(x) File "C:\Users\Markus\OneDrive\phd\NYCU\research\bit_net\xor_test_bitlinear.py", line 39, in outputs = model(inputs) # Forward pass RuntimeError: The size of tensor a (4) must match the size of tensor b (8) at non-singleton dimension 0 " I think the shapes of the self.gamma and self.beta shapes are wrong. Gamma is initialized based on # output neuron shape but is set based on batch size

I think so, but I am confused that since self.gamma is related to activations while self.beta is related to weights, should we explicitly broadcast these two matrices [quantization about activations ('group_size = x.shape[0] // self.num_groups') should be grouped in the dim=1(x.shape[1]) because of the batch_size?], thus 'x * self.gamma * self.beta' in the dequantization process can do hadamard product? If I make wrong, pls point out. Thanks.

emmm, I see the owner update the new code. (without group quantization)

authors: Vipiao jayUyang kyegomez zouyingcao

repo: kyegomez/BitNet


text:
Bug:

There is a bad var usage in the task server_keys.yml.
fatal: [vpn-test.mylab.com]: FAILED! => {"msg": "The conditional check 'file_result.state == 'absent'' failed. The error was: error while evaluating conditional (file_result.state == 'absent'): 'dict object' has no attribute 'state'\n\nThe error appears to be in '/home/lmaurice/ws/infra/ansible-infrastructure/galaxy_roles/openvpn/tasks/server_keys.yml': line 137, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create certificate revocation list database if required\n  ^ here\n"}

I solved the problem replacing in tasks/server_keys.yml line 137 :
This
- name: create certificate revocation list database if required
  file:
    path: "{{openvpn_key_dir}}/index.txt"
    state: touch
  when: file_result.state == 'absent'

By this
- name: create certificate revocation list database if required
  file:
    path: "{{openvpn_key_dir}}/index.txt"
    state: touch
  when: '"absent" in file_result'

Please merge is @kyl191 because the current HEAD of the master branch doesn't work

Fixed in https://github.com/kyl191/ansible-role-openvpn/commit/5cea19481ef73c3c6e528b5292827d7848dec602

authors: kyl191 lucasmaurice robvadai


text:
Update will be needed for undefined type: ast.PatternLikeExpr

Version
1.17.2
What happened?
It looks like an update to pingcap/tidb, https://github.com/pingcap/tidb/issues/40943, removed the ast.PatternLikeExpr type in favor of ast.PatternLikeOrIlikeExpr. internal/engine/dolphin/convert.go will need to be updated if this dependency is updated.
Relevant log output
../../go/pkg/mod/github.com/kyleconroy/sqlc@v1.17.2/internal/engine/dolphin/convert.go:1066:46: undefined: ast.PatternLikeExpr
../../go/pkg/mod/github.com/kyleconroy/sqlc@v1.17.2/internal/engine/dolphin/convert.go:1623:14: undefined: ast.PatternLikeExpr

Database schema
No response
SQL queries
No response
Configuration
No response
Playground URL
No response
What operating system are you using?
macOS
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

I think I figured out what happened to me.  I used go get -u ./... to update all dependencies. This also updated the indirect dependencies, where tidb was in that list. So tidb was set to a version that is not compatible with sqlc.
I found that the version of tidb that was listed as an indirect dependency in go.mod did not match what was specified in sqlc's go.mod file.
This fixed it for me:

uninstall sqlc and tidb
reinstall sqlc
tidy & vendor

go get github.com/kyleconroy/sqlc@none
go get github.com/pingcap/tidb/parser@none

go get github.com/kyleconroy/sqlc@v1.18.0
go mod tidy && go mod vendor

tldr: This does not appear to be a bug with sqlc but a side effect of blindly upgrading all dependencies.
This issue should be closed.

That's how I ran into this, with go get -u ./.... sqlc is currently fine with the tidb version it's using (at least it was when I opened this.) I tried to frame this issue as, "if you update tidb, you'll need to make changes", but if this just clutters the backlog it would make sense to close this issue.

Going to close this, but it is something we'll have to fix once we upgrade tidb, which will happen sometime this month.

authors: ericbock kyleconroy panthershark

repo: kyleconroy/sqlc


text:
Add option to include leading zero (hour) in times

[ ] Add toggle to unit settings for "Add leading zero to time" (below the "Use 24-hour format" setting)
[ ] Add property to UserPreferences (use BooleanPreference, see backtrackSaveCellHistory as an example)
[ ] Update FormatService.formatTime to use the leading zero preference
[ ] Default is false

Examples:

3:00 AM -> 03:00 AM
05:00 -> 05:00

Heyho, I will be on vacation soon-ish and am looking for things todo. Would be glad if you would describe the issue closer.

@Portagoras thank you, I have updated the description of this issue with more details

Many thanks!


text:
Provide AWS Service Broker bundle

Description
Provide AWS Service Broker installation at runtime.
Reasons
Allow Kyma users to integrate AWS Service Broker with Kyma in an easy way with well documented steps described in a documentation of the service class.
Acceptance Criteria

Make a bundle for AWS Service Broker

keep all naming conventions, like description etc synced with already existing Azure and GCP bundles
check if bundle requires some input parameters (for example Azure Broker has such one)

Create service class documentation for above bundle

Overview - how to acquire a secret
Details - describe what installation is doing

Make sure all AWS Service Broker classes are well documented.
Make sure all input parameters are displayed correctly in Service Catalog UI
release bundles repository and use new version in Kyma

Attachments

Documentation, see: https://github.com/awslabs/aws-servicebroker/tree/master/docs
Installation on Kubernetes, see: https://github.com/awslabs/aws-servicebroker/blob/master/docs/getting-started-k8s.md

Two issues needs to be created:

bundle itself implementation and doc
add documentation per every AWS class, use reference to AWS documentation

repo: kyma-project/bundles


text:
Handle HPAs in preferred version (v2beta2 -> v2)

Description
We should use preferred version of the resources all the time. In case of HPAs, that would be v2, while we are using v2beta2. Smooth upgrade is impossible, since in v2 the new one a field (metrics) was removed / made optional. Let's research if an upgrade is viable.

Bonus task - if upgrade is successful, remove HPAs if statement in core-ui/src/hooks/useVersionWarning.js, if upgrade is impossible remove the link to this issue from the codebase.

HPA v2 version was introduced in Kubernetes 1.23, so we should wait for this task until that version is the default one for Kyma.

repo: kyma-project/busola


text:
Adjust installer

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/test all

repo: kyma-project/control-plane


text:
core: Migrate to PGSQL

Fixes #357

What's with all the LGTM errors?

It's related to https://github.com/Semmle/ql/issues/2051, it hasn't been deployed yet so it's for now, haunting me all the time. @tech6hutch

repo: kyranet/Skyra


text:
64bit python evironment in visual studio does not recognize junit-xml

Hi
I develop python within visual studio and I make use of the 64bit python interpreter because it crashes less in visual studio. How can I make junit-xml available in 64bit python environment.
Thanks
Mudasir

Hi,
How is related? Why is it crashing only because you use 64 bit cpu?

Hi, let me elaborate.
I managed to resolve the issue but I will give some background and the solution.
My development IDE is Visual Studio. I have python 2.7.13 32bit installed on my C Drive. I have visual studio plugin for Python Language Integration. I am not sure of this but I think this plugin also installs the 64bit version of Python. Or I might have installed the 64bit version of python27 myself.
When I create a python project within visual studio, it detects both versions of python and organises them in these things called Environment. So I have IronPython installed then that would also be picked up as an environment. In visual studio I can switch the different Environments and run the same python source files.
I installed JunitXml using
pip install junit-xml in commandline
But when I switched to Python64 environment then import JunitXml returned an error the interpreter as an unknown package.
Here is the fix:
To have python 64bit in visual studio recognise junit-xml, you need to install it within visual studio. In devStudio, right click on the 64bit python environment and select Install python package.-> easy install and type in junit.xml and run as administrator
Please note in other packages I have pipped in commandline have installed the package for both 32bit and 64bit python.
Any how my issue has been resolved.
The only reason for me using 64bit python is that it crashes less in Visual Studio on simple functions like print, etc.

authors: mudasira sysradium

repo: kyrus/python-junit-xml


text:
🛑 clinicafabregat.com is down

In d6d592a, clinicafabregat.com (https://clinicafabregat.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: clinicafabregat.com is back up in 5e421c0 after 19 minutes.

repo: kyryl-bogach/upptime


text:
Action object has no attribute 'as_dict'

Hi,
Running the Noviflow Napp with Kytos 2022.2 gives us the following error:
Oct 26 17:46:08 8ba74f12c575 kytos.core.helpers:ERROR helpers:130:  listen_to handler: <function Main.on_flow_stats_check_consistency at 0x7f04e8241310>, args: (<Main(flow_manager, stopped 139655919937280)>, KytosEvent('kytos/of_core.flow_stats.received', {'switch': Switch('00:00:00:00:00:00:00:0c'), 'replies_flows': [<napps.kytos.of_core.v0x04.flow.Flow object at 0x7f041446b7c0>, <napps.kytos.of_core.v0x04.flow.Flow object at 0x7f041446bb50>, <napps.kytos.of_core.v0x04.flow.Flow object at 0x7f041446b430>, <napps.kytos.of_core.v0x04.flow.Flow object at 0x7f0414384820>, <napps.kytos.of_core.v0x04.flow.Flow object at 0x7f04143846a0>, <napps.kytos.of_core.v0x04.flow.Flow object at 0x7f0414384b20>, <napps.kytos.of_core.v0x04.flow.Flow object at 0x7f0414384640>]}, 0)) traceback: Traceback (most recent call last):,   File "/usr/local/lib/python3.9/dist-packages/kytos/core/helpers.py", line 126, in handler_context,     result = handler(*args),   File "//var/lib/kytos/napps/kytos/flow_manager/main.py", line 144, in on_flow_stats_check_consistency,     self.check_consistency(event.content["switch"]),   File "//var/lib/kytos/napps/kytos/flow_manager/main.py", line 328, in check_consistency,     self.check_alien_flows(switch),   File "//var/lib/kytos/napps/kytos/flow_manager/main.py", line 387, in check_alien_flows,     flows = self.switch_flows_by_id(switch, self.is_not_ignored_flow),   File "//var/lib/kytos/napps/kytos/flow_manager/main.py", line 344, in switch_flows_by_id,     return {flow.id: flow for flow in switch.flows if filter_flow(flow)},   File "//var/lib/kytos/napps/kytos/flow_manager/main.py", line 344, in <dictcomp>,     return {flow.id: flow for flow in switch.flows if filter_flow(flow)},   File "//var/lib/kytos/napps/../napps/kytos/of_core/flow.py", line 102, in id,     flow_str = self.as_json(sort_keys=True, include_id=False),   File "//var/lib/kytos/napps/../napps/kytos/of_core/flow.py", line 208, in as_json,     return json.dumps(self.as_dict(include_id), sort_keys=sort_keys),   File "//var/lib/kytos/napps/../napps/kytos/of_core/v0x04/flow.py", line 350, in as_dict,     flow_dict['instructions'] = [instruction.as_dict() for,   File "//var/lib/kytos/napps/../napps/kytos/of_core/v0x04/flow.py", line 350, in <listcomp>,     flow_dict['instructions'] = [instruction.as_dict() for,   File "//var/lib/kytos/napps/../napps/kytos/of_core/v0x04/flow.py", line 216, in as_dict,     instruction_dict['actions'] = [action.as_dict(),   File "//var/lib/kytos/napps/../napps/kytos/of_core/v0x04/flow.py", line 216, in <listcomp>,     instruction_dict['actions'] = [action.as_dict(), AttributeError: 'NoneType' object has no attribute 'as_dict',

Steps to reproduce:

Run Kytos docker container amlight/kytos:2022.2rc1
Install kytos/noviflow python3 -m pip install -e git+https://github.com/kytos-ng/noviflow@master#egg=kytos-noviflow
Create a flow for testing: curl http://127.0.0.1:8181/api/kytos/flow_manager/v2/flows/00:00:00:00:00:00:00:0c -H 'Content-type: application/json' -d '{"flows": [{"priority": 10, "match": {"in_port": 23}, "actions": [{"action_type": "push_int"}, {"action_type": "output", "port": 2}]}]}'

Expected result:
the flow should be created, and the Kytos server should stay stable along successive executions of the consistency check
Actual result:
the flow is installed, but kytos raise exceptions on each consistency check execution.

Hi @viniarck I've investigated this a little more and it looks like the kytos/noviflow Napp is missing the mapping from Python object classes to actual Action class (we only have the mapping from string to Action). The following patch fixes the issue above:
diff --git a/main.py b/main.py
index 955e155..8c6dbf7 100644
--- a/main.py
+++ b/main.py
@@ -10,6 +10,13 @@ from napps.amlight.noviflow.of_core.v0x04.action import (
     NoviActionSendReport,
     NoviActionSetBfdData,
 )
+from napps.amlight.noviflow.pyof.v0x04.action import (
+    NoviActionAddIntMetadata as OFNoviActionAddIntMetadata,
+    NoviActionPopInt as OFNoviActionPopInt,
+    NoviActionPushInt as OFNoviActionPushInt,
+    NoviActionSendReport as OFNoviActionSendReport,
+    NoviActionSetBfdData as OFNoviActionSetBfdData,
+)
 from napps.kytos.of_core.v0x04.flow import Action

 from kytos.core import KytosNApp
@@ -20,6 +27,11 @@ NOVIFLOW_ACTIONS = {
     "add_int_metadata": NoviActionAddIntMetadata,
     "pop_int": NoviActionPopInt,
     "send_report": NoviActionSendReport,
+    OFNoviActionSetBfdData: NoviActionSetBfdData,
+    OFNoviActionPushInt: NoviActionPushInt,
+    OFNoviActionAddIntMetadata: NoviActionAddIntMetadata,
+    OFNoviActionPopInt: NoviActionPopInt,
+    OFNoviActionSendReport: NoviActionSendReport,
 }

A similar approach is done at kytos/of_core: https://github.com/kytos-ng/of_core/blob/master/v0x04/flow.py#L182-L191

repo: kytos-ng/noviflow


text:
[Feature] Allow configuration of the deletion propagation policy

Problem Statement
Deletion propagation policy is set to orphan by default for a few types (unmanaged jobs for example).
This is probably not what users expected is most if not all cases, for this reason i forced the deletion propagation policy to Background in a recent PR.
Now it would be nice to be let users decide what they want.
Solution Description
A deletion propagation policy should be supported at the global, test, step, and operation levels.
Alternatives
No response
Additional Context
No response
Slack discussion
https://kubernetes.slack.com/archives/C067LUFL43U/p1715525488068409
Research

[X] I have searched other issues in this repository and mine is not recorded.

/assign

repo: kyverno/chainsaw


text:
[Enhancement]: Replace enforce/audit (deprecated) with Enforce/Audit on sample policies

Kyverno Version
1.12
Kubernetes Version
1.29
Kubernetes Platform
Minikube
Description
Currently, there are some policies where spec.validationFailureAction starts with a lowercase letter, i.e., audit and enforce. These are deprecated, and Audit and Enforce should be used instead.
Steps to Reproduce
Deprecated spec.validationFailureAction: audit
To find all YAML files with this deprecated action, use the following command in the root directory of the policies repo:
grep -rl "validationFailureAction: audit" --include \*.yaml .

Deprecated spec.validationFailureAction: enforce
To find all YAML files with this deprecated action, use the following command in the root directory of the policies repo:
grep -rl "validationFailureAction: enforce" --include \*.yaml .

When you apply any of these policies using kubectl, you will receive the following warning:
Warning: Validation failure actions enforce/audit are deprecated, use Enforce/Audit instead.

Expected Behavior
No warnings should be generated when applying these sample policies to a Kubernetes cluster. The policies should be consistent, using Enforce and Audit instead of the deprecated forms.
Solution

To replace the deprecated audit with Audit, use the following command:

for file in $(grep -rl "validationFailureAction: audit" --include \*.yaml .); do
  sed -i 's/validationFailureAction: audit/validationFailureAction: Audit/g' "$file"
done

To replace the deprecated enforce with Enforce, use the following command:

for file in $(grep -rl "validationFailureAction: enforce" --include \*.yaml .); do
  sed -i 's/validationFailureAction: enforce/validationFailureAction: Enforce/g' "$file"
done

Troubleshooting

[X] I have read and followed the documentation AND the troubleshooting guide.
[X] I have searched other issues in this repository and mine is not recorded.

Please let me know if this is a valid issue. I would be glad to submit a PR for this. 🙏

We're aware, we use annotations to state the minimum version of Kyverno and we don't always keep policies up to the bleeding edge because of compatibility.

authors: chipzoller mohamedawnallah

repo: kyverno/policies


text:
safe to evict policy fails on generated items without volumes

Signed-off-by: Jon Leemon jon.leemon@invitae.com
The policy throws an error when it meets a cronjob that does not have any volumes:
E0514 12:31:24.087776   57635 strategicMergePatch.go:69] EngineMutate "msg"="failed to apply patchStrategicMerge" "error"="failed to preProcess rule: wrong Node Kind for  expected: SequenceNode was MappingNode: value: {{\"containers\": [{\"envFrom\": [{\"configMapRef\": {\"name\": \"myconfigmap\"}}], \"image\": \"myimage\", \"imagePullPolicy\": \"Always\", \"name\": \"mycronjob\", \"resources\": {\"limits\": {\"cpu\": \"100m\", \"memory\": \"128Mi\"}, \"requests\": {\"cpu\": \"50m\", \"memory\": \"64Mi\"}}}], \"restartPolicy\": \"OnFailure\"}}" "kind"="CronJob" "name"="mycronjob" "namespace"="default" "policy"="add-safe-to-evict" "rule"="autogen-cronjob-annotate-empty-dir"
E0514 12:31:24.088916   57635 strategicMergePatch.go:69] EngineMutate "msg"="failed to apply patchStrategicMerge" "error"="failed to preProcess rule: wrong Node Kind for  expected: SequenceNode was MappingNode: value: {{\"containers\": [{\"envFrom\": [{\"configMapRef\": {\"name\": \"myconfigmap\"}}], \"image\": \"myimage\", \"imagePullPolicy\": \"Always\", \"name\": \"mycronjob\", \"resources\": {\"limits\": {\"cpu\": \"100m\", \"memory\": \"128Mi\"}, \"requests\": {\"cpu\": \"50m\", \"memory\": \"64Mi\"}}}], \"restartPolicy\": \"OnFailure\"}}" "kind"="CronJob" "name"="mycronjob" "namespace"="default" "policy"="add-safe-to-evict" "rule"="autogen-cronjob-annotate-host-path"

@nomeelnoj - this seems like a bug, can you please open an issue in kyverno/kyverno repo?

This policy doesn't seem to work anymore with patchStrategicMerge.  Relevant Slack discussion here.

@chipzoller @realshuting - is this ok to merge, or are other actions required?

Double check on your end, @JimBugwadia , but when I tested, even with this PR's fix, it doesn't work with the current version due to the anchor issue that's recently discussed. If that's the case, this policy either needs to have a disclaimer or just removed.

Looks like the issue hasn't been resolved yet, will need to test the changes with the fix.

@realshuting @kacejot I am confused what the status is with the ability to support this policy. Can someone please provide a current summary? If this policy is still "broken" in 1.4.2 and won't be addressed soon, this PR needs to be closed and the policy removed from the samples or else edited to state the last known version of Kyverno where it worked. We shouldn't have policies available to users which are known to be broken in current releases, so please advise here.

@realshuting @kacejot I am confused what the status is with the ability to support this policy. Can someone please provide a current summary? If this policy is still "broken" in 1.4.2 and won't be addressed soon, this PR needs to be closed and the policy removed from the samples or else edited to state the last known version of Kyverno where it worked. We shouldn't have policies available to users which are known to be broken in current releases, so please advise here.

@kacejot - since you are working on this issue, can you please update the current status?

@kacejot we really need your input here, please

This issue must be fixed in 1.4.2. Checking.

This PR is superseded by https://github.com/kyverno/policies/pull/111 and so closing. Thank you for raising this, however.

authors: JimBugwadia chipzoller kacejot nomeelnoj realshuting