text:
Sega Genesis

Hi,
I’ve updated to the latest version. 1.5 ( 12182020 ). Since updating I cannot load any sega genesis games. By I am getting the error message, failed to extract content from archive.
All other systems seem to be working still.

I just tested Alien3 (.zip), Comix Zone (.zip), Flash Point (.bin) and Fix it Felix Jr(.bin.  All loaded fine on my end on my daily driver that's updated to 1.5 (12182020) and a 1.5 image I upgraded to 12182020.  I can't replicate this issue so far.  What format are your games in?

Thank you. They are in .zip format. It’s odd. If I backup my easyroms files and do a backup and copy that file off, then rebuilt, restore and copy my easyroms files back over what would I lose?

You should be ok to that.  For added insurance, you can take an image of your current sd card using USB IT (https://www.alexpage.de/usb-image-tool/download/) in case you lose something.  The issues you're describing leads me to believe something isn't quite right.  Make sure of the following:
You're using a good quality micro sd card such ad Sandisk or Samsung.  no name brand cards and other cheap brands like Netac will eventually lead to strange issues like what you're describing.
Make sure you're using a program like USB IT to image the card.  Balena Etcher is not recommended for imaging ArkOS as it leads to performance and usability issues like what you're describing.

Thank you.
yeah I have a good quality card. Everything else works perfectly, all of the other systems etc.
I didn’t use etcher.
Cheers.
it doesn’t seem to be related to ArkOS so I will close the ticket. Cheers

authors: christianhaitian marcosgeorgopoulos

repo: christianhaitian/arkos


text:
[4pt] Create routes

Add routes to different paths:

Log in page (Should be default)
Main page (Displays all courses)
Reserve form
Reservations
Add new Course
Delete

Closed with PR:
https://github.com/smunoz1988/vecs-school-frontend/pull/2

source: gharchive/issue

repo: christianonoh/vecs-school-backend

license: MIT

license_type: permissive

license_source: github-api


text:
IMX477 sensor configured as a sink

Hi @christianrauch,
We have two IMX477 HQ cameras connected to a Raspberry Pi 5. One is configured as a sink while the other one is configured as a source.
Using rpicam-vid I can receive frames at 30FPS from both cameras but I am interested in using your implementation as it solves issues we have today with h264-encoded streams. Below are the commands I use with rpicam-vid
For the sink:
LIBCAMERA_RPI_CONFIG_FILE=/etc/rpi_apps.yaml && rpicam-vid -t 0 -n --camera 0 --codec libav --libav-format h264 --libav-video-codec libx264 --libav-video-codec-opts "tune=zerolatency;preset=ultrafast;g=30" --width 2028 --height 1080 --denoise off --lens-position 0.0 --hdr off --framerate 30 -o udp://127.0.0.1:5555

For the source:
rpicam-vid -t 0 -n --camera 1 --codec libav --libav-format h264 --libav-video-codec libx264 --libav-video-codec-opts "tune=zerolatency;preset=ultrafast;g=30" --width 2028 --height 1080 --denoise off --lens-position 0.0 --hdr off --framerate 30 -o udp://127.0.0.1:5556

Using camera_ros with Raspberry Pi's libcamera, I can generate ROS2 compressed images, which is awesome but with some limitations. It only works with low FPS. For instance at 10 FPS, the following commands are used and works:
For the sink:
LIBCAMERA_RPI_CONFIG_FILE=/etc/rpi_apps.yaml && ros2 run  camera_ros camera_node --ros-args -p camera:=0 -p width:=2028 -p height:=1080 -p role:=still -r /camera/image_raw:=/left_cam/raw -r /camera/image_raw/compressed:=/left_cam/compressed -r /camera/camera_info:=/left_cam/camera_info -p FrameDurationLimits:="[100000,100000]" -p AeFlickerMode:="0" -p AeEnable:="false" -p HdrMode:="0" -p NoiseReductionMode:="0" -p format:="YUYV"

For the source:
ros2 run  camera_ros camera_node --ros-args -p camera:=1 -p width:=2028 -p height:=1080 -p role:=still -r /camera/image_raw:=/right_cam/raw -r /camera/image_raw/compressed:=/right_cam/compressed -r /camera/camera_info:=/right_cam/camera_info -p FrameDurationLimits:="[100000,100000]" -p AeFlickerMode:="0" -p AeEnable:="false" -p HdrMode:="0" -p NoiseReductionMode:="0" -p format:="YUYV"

I tried at 20 FPS, and it worked sometimes. I realized that it worked when the ambient brightness was significantly higher than in the no-working cases. So I think it has to do with the exposure time. I cannot fix the exposure time as I have the same problem as in #33. My gut feeling is that the program does not handle correctly when an external trigger is received while the camera is still under exposure, I can get few first frames with visible first rows, but then it loops over those frames forever (the publishing rate is correct, ~20 Hz).

Is it a misconfiguration on my side or does camera_ros not support such setup?

Alright, think I found the fix, I made a PR: https://github.com/christianrauch/camera_ros/pull/39
Inspired by https://github.com/raspberrypi/rpicam-apps/blob/414a7383464b98f21f5e5381a16cc73ae0350ba6/core/rpicam_app.cpp#L757C15-L757C32.
@christianrauch: I hope this is useful. Let me know if any changes are needed for the PR.


text:
ENH: (Issue #1234) add exception when user tries to create more than one persistent or ephemeral client.

ref: #1234
Description of changes
Summarize the changes made by this PR.

added @once decorator to PersistentClient() and EphemeralClient() in chromadb/init.py.
added once() in chromadb.utils that raises a RuntimeError when user tries to instantiate more than one persistent or ephemeral client.

Test plan
How are these changes tested?

added 4 tests in chromadb/test/test_client.py. Two tests to test if the error is raised, two tests to see if a client can be instantiated after a previous client had been instantiated, destroyed, and garbage collected.
[x] Tests pass locally with pytest for python

Documentation Changes
small change to usage-guide.md
https://github.com/vaughanlove/docs/tree/update
Side note:
This is my first open-source contribution. I want to learn and improve, any advice appreciated.

Hi! Thanks for doing this!
I think we are going to go with #1244 - which adds a mechanism which allows you to create multiple clients, rather than prevent it. As its a very common need.

Hi! Thanks for doing this!
I think we are going to go with #1244 - which adds a mechanism which allows you to create multiple clients, rather than prevent it. As its a very common need.

No worries!
Yeah, I agree that is a better way to go.

source: gharchive/pull-request

authors: HammadB vaughanlove

repo: chroma-core/chroma


text:
May I know how to send key combinations

Excuse me, I can't find the relevant documents.
I want to realize such a function:
sendKey: ctrl+a delete ,
To delete all text

Have you seen https://github.com/chromedp/examples?

If you want to just send the key in a sequence, as if the user had pressed it independently, build a string using chromedp/kb.Control, and use it with chromedp.SendKeys:
str := kb.Control+"a"
if err := chromedp.Run(ctx, chromedp.SendKeys(`#thing`, str); err != nil {
   panic(err
}

Note: SendKeys synthesizes a user "typing" the string. It doesn't try to do any kind of advanced logic such as holding down keys, as it would be impossible to model this in a single string.
If you need to send multiple pressed keys at the same time (ie, holding Control + Alt while also sending the A key), you'll need to use the direct API calls, which would be roughly:
KeyDown(Control)
KeyDown(Alt)
KeyPress(A)
KeyUp(Alt)
KeyUp(Control)

The Chrome API to send individual key events is in the github.com/chromedp/cdproto/input package:
if err := chromedp.Run(ctx, input.DispatchKeyEvent(input.KeyDown).WithKey(kb.Control)); err != nil {
    panic(err)
}

The above would need to be done for the sequence I described above. Additionally, since Alt is a modifier, you'd need to set it as correctly to the DispatchKeyEvent command. If in doubt about exactly which Chrome key events to send, and in what order, I would suggest using chromedp-proxy and recording a session from Chrome's DevTools and looking at the wireline protocol commands that DevTools sends.

authors: kenshaw mvdan sohaha

repo: chromedp/chromedp

license: mit

license_source: bigquery


text:
Install software.

FFMPEG
Wkhtmltoimage / Wkhtmltopdf - optional
ZopfliPNG
PngCrush
JPEGOptim
PNGOut
AdvPNG
MozJPEG
WebP

# ZopfliPNG
wget https://github.com/imagemin/zopflipng-bin/raw/master/vendor/linux/zopflipng -O /usr/local/bin/zopflipng
chmod 0755 /usr/local/bin/zopflipng

# PngCrush
wget https://github.com/imagemin/pngcrush-bin/raw/master/vendor/linux/pngcrush -O /usr/local/bin/pngcrush
chmod 0755 /usr/local/bin/pngcrush

# JPEGOptim
wget https://github.com/imagemin/jpegoptim-bin/raw/master/vendor/linux/jpegoptim -O /usr/local/bin/jpegoptim
chmod 0755 /usr/local/bin/jpegoptim

# PNGOut
wget https://github.com/imagemin/pngout-bin/raw/master/vendor/linux/x64/pngout -O /usr/local/bin/pngout
chmod 0755 /usr/local/bin/pngout

# AdvPNG
wget https://github.com/imagemin/advpng-bin/raw/master/vendor/linux/advpng -O /usr/local/bin/advpng
chmod 0755 /usr/local/bin/advpng

# MozJPEG
wget https://github.com/imagemin/mozjpeg-bin/raw/master/vendor/linux/cjpeg -O /usr/local/bin/cjpeg
chmod 0755 /usr/local/bin/cjpeg

WARNING! Only 'pngout' workable.

repo: chupikov/php-docker


text:
Fix parsing of amount with only an assertion

Fixes #187.

Just waiting for confirmation of the fix.

repo: chvp/NanoLedger


text:
🛑 WWW is down

In 013b7e6, WWW (https://chse.dev) was down:

HTTP code: 522
Response time: 15373 ms

Resolved: WWW is back up in eee9523.

repo: chxseh/upptime


text:
Could you help add git tag?

Hello @ciar4n I am the member of cdnjs project. We want to host this library. Git tag can help us to know your release version, and we can auto-update the version when you have new release. Could you please help us add git tag. Thanks for your help!
https://github.com/cdnjs/cdnjs/issues/10046

Hi @kennynaoh
Certainly. A git tag has been added as requested. Let me know if you need anything else.
Regards
Ciarán

@ciar4n Thanks for your help. I will host this library on CDNJS ASAP.


text:
CI: K8sCustomCalls Basic test with byte-counter Loads byte-counter and gets consistent values

Test fail did not produce any artifacts nor normal test fail reports, so the title is gobbled up from the test logs. The error message is:
timed out waiting for pod bytecounter-compiler in namespace default to be ready: 4m0s timeout expired

This was the first test in the job, which may be significant for reproduction, so the whole log is copied below:
11:04:41  + cd /home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test
11:04:41  + HOME=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next ginkgo --focus=K8s -v --failFast=false -- -cilium.provision=false -cilium.timeout=170m -cilium.kubeconfig=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/vagrant-kubeconfig -cilium.passCLIEnvironment=true -cilium.runQuarantined=false -cilium.image=quay.io/cilium/cilium-ci -cilium.tag=426bb86118a40ff9deeb036a7547d7286c3cf3df -cilium.operator-image=quay.io/cilium/operator -cilium.operator-tag=426bb86118a40ff9deeb036a7547d7286c3cf3df -cilium.hubble-relay-image=quay.io/cilium/hubble-relay-ci -cilium.hubble-relay-tag=426bb86118a40ff9deeb036a7547d7286c3cf3df -cilium.operator-suffix=-ci
11:05:23  Running Suite: Suite-k8s-1.16
11:05:23  =============================
11:05:23  Random Seed: 1627632280
11:05:23  Will run 154 of 451 specs
11:05:23
11:05:23  S
11:05:23  ------------------------------
11:05:23  K8sCustomCalls Basic test with byte-counter
11:05:23    Loads byte-counter and gets consistent values
11:05:23    /home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:518
11:05:23  08:05:21 STEP: Running BeforeAll block for EntireTestsuite
11:05:23  08:05:21 STEP: Starting tests: command line parameters: {Reprovision:false HoldEnvironment:false PassCLIEnvironment:true SSHConfig: ShowCommands:false TestScope: SkipLogGathering:false CiliumImage:quay.io/cilium/cilium-ci CiliumTag:426bb86118a40ff9deeb036a7547d7286c3cf3df CiliumOperatorImage:quay.io/cilium/operator CiliumOperatorTag:426bb86118a40ff9deeb036a7547d7286c3cf3df CiliumOperatorSuffix:-ci HubbleRelayImage:quay.io/cilium/hubble-relay-ci HubbleRelayTag:426bb86118a40ff9deeb036a7547d7286c3cf3df ProvisionK8s:true Timeout:2h50m0s Kubeconfig:/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/vagrant-kubeconfig KubectlPath:/tmp/kubectl RegistryCredentials: Benchmarks:false Multinode:true RunQuarantined:false Help:false} environment variables: [JENKINS_HOME=/var/jenkins_home ghprbSourceBranch=visibility-policy-fix-up ghprbTriggerAuthorEmail=jarno@isovalent.com VM_MEMORY=8192 MAIL=/var/mail/root KUBEPROXY=0 SSH_CLIENT=54.148.123.155 49670 22 ghprbPullAuthorEmail=jarno@isovalent.com USER=root PROJ_PATH=src/github.com/cilium/cilium RUN_CHANGES_DISPLAY_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/display/redirect?page=changes ghprbPullDescription=GitHub pull request #16258 of commit 426bb86118a40ff9deeb036a7547d7286c3cf3df, no merge conflicts. NETNEXT=1 ghprbActualCommit=426bb86118a40ff9deeb036a7547d7286c3cf3df SHLVL=1 CILIUM_TAG=426bb86118a40ff9deeb036a7547d7286c3cf3df NODE_LABELS=baremetal ginkgo nightly node-selected-gobbler vagrant HUDSON_URL=https://jenkins.cilium.io/ GIT_COMMIT=5a1178f7ab7288ec8993c6a33e9c9ef9f3ab670e OLDPWD=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next GINKGO_TIMEOUT=170m HOME=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next ghprbTriggerAuthorLoginMention=@jrajahalme BUILD_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/ ghprbPullAuthorLoginMention=@jrajahalme HUDSON_COOKIE=2d84d0ae-0aa1-44a4-bfe5-1efe1ba06345 JENKINS_SERVER_COOKIE=durable-566a7e299b40ade7629ede0388948e1f ghprbGhRepository=cilium/cilium DOCKER_TAG=426bb86118a40ff9deeb036a7547d7286c3cf3df JobKernelVersion=net-next KERNEL=net-next CONTAINER_RUNTIME=docker WORKSPACE=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next ghprbPullLongDescription=Adjust and expand eBPF policy map keys and values to redirect for\r\nvisibility on the port of the visibility annotation while still\r\ndenying traffic on this port for identities for which the traffic is\r\ndenied.\r\n\r\nDatapath lookup order is, from highest to lowest precedence:\r\n1. L3/L4\r\n2. L4-only (wildcard L3)\r\n3. L3-only (wildcard L4)\r\n4. Allow-all\r\n\r\nThis means that the L4-only allow visibility key can only be added if\r\nthere is an allow-all key, and all L3-only deny keys are expanded to\r\nL3/L4 keys. If no L4-only key is added then also the L3-only allow\r\nkeys need to be expanded to L3/L4 keys for visibility redirection. In\r\naddition the existing L3/L4 and L4-only allow keys need to be\r\nredirected to the proxy port, if not already redirected.\r\n\r\nThe above can be accomplished by:\r\n\r\n1. Change existing L4-only ALLOW key on matching port that does not already\r\n   redirect to redirect.\r\n   - e.g., 0:80=allow,0 -> 0:80=allow,<proxyport>\r\n2. If allow-all key exists, add L4-only visibility redirect key if the L4-only\r\n   key does not already exist.\r\n   - e.g., 0:0=allow,0 -> add 0:80=allow,<proxyport> if 0:80 key does not exist\r\n     - this allows all traffic on port 80, but see step 5 below.\r\n3. Change all L3/L4 ALLOW keys on matching port that do not already redirect to\r\n   redirect.\r\n   - e.g, <ID1>:80=allow,0 -> <ID1>:80=allow,<proxyport>\r\n4. For each L3-only ALLOW key add the corresponding L3/L4 ALLOW redirect if no\r\n   L3/L4 key already exists and no L4-only key already exists and one is not added.\r\n   - e.g., <ID2>:0=allow,0 -> add <ID2>:80=allow,<proxyport> if <ID2>:80\r\n     and 0:80 do not exist and 0:80 was not added\r\n5. If a new L4-only key was added: For each L3-only DENY key add the\r\n   corresponding L3/L4 DENY key if no L3/L4 key already exists\r\n   - e.g., <ID3>:0=deny,0 -> add <ID3>:80=deny,0 if <ID3>:80 does not exist.\r\n\r\nWith the above we only change/expand existing allow keys to redirect, and\r\nexpand existing drop keys to also drop on the port of interest, if a new\r\nL4-only key allowing the port is added.\r\n\r\nAdjust the unit test to mimic the real behavior a bit better by\r\nregenerating endpoint policy after updating visibility policy. This is\r\nneeded due to the test using same port for HTTP and Kafka, and without\r\nregenerating visibility redirects no longer overwrite existing\r\nredirects.\r\n\r\nVisibility redirects need to be re-applied after applying incremental\r\npolicy map changes. This is due to incremental changes possibly adding\r\nkeys for new identities that need visibility redirections or\r\nadditional deny keys as defined above.\r\n\r\nTesting: New unit tests in policy package cover all the cases\r\ndescribed above.\r\n\r\nFixes: #9088\r\n\r\n```release-note\r\nPod L7 visibility annotations are now supported also when policy enforcement is enabled.\r\n```\r\n K8S_NODES=3 TESTDIR=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test LOGNAME=root NODE_NAME=node-selected-gobbler ghprbCredentialsId=ciliumbot _=/usr/bin/java HUBBLE_RELAY_IMAGE=quay.io/cilium/hubble-relay-ci STAGE_NAME=BDD-Test-PR GIT_BRANCH=origin/pr/16258/merge EXECUTOR_NUMBER=0 NO_CILIUM_ON_NODE=k8s3 ghprbTriggerAuthorLogin=jrajahalme TERM=xterm XDG_SESSION_ID=7 HOST_FIREWALL=0 CILIUM_OPERATOR_TAG=426bb86118a40ff9deeb036a7547d7286c3cf3df BUILD_DISPLAY_NAME=policy: Adjust existing policy for visibility annotations  https://github.com/cilium/cilium/pull/16258  #1178 ghprbPullAuthorLogin=jrajahalme HUDSON_HOME=/var/jenkins_home ghprbTriggerAuthor=Jarno Rajahalme JOB_BASE_NAME=Cilium-PR-K8s-1.16-net-next PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin:/root/go/bin sha1=origin/pr/16258/merge KUBECONFIG=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/vagrant-kubeconfig FOCUS=K8s BUILD_ID=1178 XDG_RUNTIME_DIR=/run/user/0 BUILD_TAG=jenkins-Cilium-PR-K8s-1.16-net-next-1178 RUN_QUARANTINED=false CILIUM_IMAGE=quay.io/cilium/cilium-ci JENKINS_URL=https://jenkins.cilium.io/ LANG=en_US.UTF-8 ghprbCommentBody=test-me-please JOB_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/ ghprbPullTitle=policy: Adjust existing policy for visibility annotations GIT_URL=https://github.com/cilium/cilium ghprbPullLink=https://github.com/cilium/cilium/pull/16258 BUILD_NUMBER=1178 JENKINS_NODE_COOKIE=e5d0bff5-6a36-49f4-9e5c-5922ebcdd9c2 SHELL=/bin/bash GOPATH=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next RUN_DISPLAY_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/display/redirect ghprbAuthorRepoGitUrl=https://github.com/jrajahalme/cilium.git FAILFAST=false HUDSON_SERVER_COOKIE=693c250bfb7e85bf ghprbTargetBranch=master JOB_DISPLAY_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/display/redirect K8S_VERSION=1.16 JOB_NAME=Cilium-PR-K8s-1.16-net-next PWD=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test SSH_CONNECTION=54.148.123.155 49670 145.40.78.173 22 ghprbPullId=16258 CILIUM_OPERATOR_IMAGE=quay.io/cilium/operator HUBBLE_RELAY_TAG=426bb86118a40ff9deeb036a7547d7286c3cf3df JobK8sVersion=1.16 VM_CPUS=3 CILIUM_OPERATOR_SUFFIX=-ci]
11:05:23  08:05:22 STEP: Ensuring the namespace kube-system exists
11:05:23  08:05:22 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs")
11:05:25  08:05:24 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs") => <nil>
11:05:25  08:05:25 STEP: Preparing cluster
11:05:25  08:05:25 STEP: Labelling nodes
11:05:25  08:05:25 STEP: Cleaning up Cilium components
11:05:26  08:05:26 STEP: Running BeforeAll block for EntireTestsuite K8sCustomCalls
11:05:26  08:05:26 STEP: Ensuring the namespace kube-system exists
11:05:26  08:05:26 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs")
11:05:26  08:05:26 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs") => <nil>
11:05:26  08:05:26 STEP: Installing Cilium
11:05:28  08:05:27 STEP: Waiting for Cilium to become ready
11:06:54  08:06:40 STEP: Restarting unmanaged pods coredns-5495c8f48d-l8lwg in namespace kube-system
11:06:54  08:06:42 STEP: Validating if Kubernetes DNS is deployed
11:06:54  08:06:42 STEP: Checking if deployment is ready
11:06:54  08:06:42 STEP: Kubernetes DNS is not ready: only 0 of 1 replicas are available
11:06:54  08:06:42 STEP: Restarting Kubernetes DNS (-l k8s-app=kube-dns)
11:07:54  08:07:53 STEP: Waiting for Kubernetes DNS to become operational
11:07:54  08:07:53 STEP: Checking if deployment is ready
11:07:54  08:07:53 STEP: Checking if kube-dns service is plumbed correctly
11:07:54  08:07:53 STEP: Checking if pods have identity
11:07:54  08:07:53 STEP: Checking if DNS can resolve
11:07:54  08:07:54 STEP: Validating Cilium Installation
11:07:54  08:07:54 STEP: Performing Cilium controllers preflight check
11:07:54  08:07:54 STEP: Performing Cilium status preflight check
11:07:54  08:07:54 STEP: Performing Cilium health check
11:07:56  08:07:55 STEP: Performing Cilium service preflight check
11:07:56  08:07:55 STEP: Performing K8s service preflight check
11:07:57  08:07:56 STEP: Waiting for cilium-operator to be ready
11:07:57  08:07:56 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator")
11:07:57  08:07:56 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") => <nil>
11:07:57  08:07:56 STEP: Making sure all endpoints are in ready state
11:07:59  08:07:58 STEP: Compiling custom byte-counter program
11:07:59  08:07:58 STEP: WaitForSinglePod(namespace="default", podname="bytecounter-compiler")
11:12:12  08:11:58 STEP: waitForSinglePod(namespace="default", podname="bytecounter-compiler", minRequired=1) => timed out waiting for pod bytecounter-compiler in namespace default to be ready: 4m0s timeout expired
11:12:12  08:12:08 STEP: cmd: kubectl describe pods -n default bytecounter-compiler
11:12:12  Exitcode: -1
11:12:12  Err: signal: killed
11:12:12  Stdout:
11:12:12
11:12:12  Stderr:
11:12:12
11:12:12
11:12:12  FAIL: bytecounter-compiler pod not ready after timeout
11:12:12  Unexpected error:
11:12:12      <*errors.errorString | 0xc000b00020>: {
11:12:12          s: "timed out waiting for pod bytecounter-compiler in namespace default to be ready: 4m0s timeout expired",
11:12:12      }
11:12:12      timed out waiting for pod bytecounter-compiler in namespace default to be ready: 4m0s timeout expired
11:12:12  occurred
11:12:12  === Test Finished at 2021-07-30T08:12:08Z====
11:12:12  08:12:08 STEP: Running JustAfterEach block for EntireTestsuite K8sCustomCalls
11:13:12  ===================== TEST FAILED =====================
11:13:12  08:13:08 STEP: Running AfterFailed block for EntireTestsuite K8sCustomCalls
11:14:12  cmd: kubectl get pods -o wide --all-namespaces
11:14:12  Exitcode: -1
11:14:12  Err: signal: killed
11:14:12  Stdout:
11:14:12
11:14:12  Stderr:
11:14:12
11:14:12
11:14:12  Fetching command output from pods []
11:14:12  ===================== Exiting AfterFailed =====================
11:14:12  08:14:08 STEP: Running AfterEach for block EntireTestsuite K8sCustomCalls Basic test with byte-counter
11:18:26  FAIL: terminating containers are not deleted after timeout
11:18:26  Expected
11:18:26      <*errors.errorString | 0xc000b00820>: {
14:04:29          s: Sending interrupt signal to process
14:04:39  cleaning up VMs started for k8s tests
14:04:39
14:04:39  ---------------------------------------------------------
14:04:39  Received interrupt.  Running AfterSuite...
14:04:39  ^C again to terminate immediately
14:04:39
14:04:39  Ginkgo ran 1 suite in 2h59m48.627810181s
14:04:39  Test Suite Passed

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/execution/node/129/log/
No artifacts were generated, no indication what failed on the job: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/

Some related artifacts (missing the test-specific artifact as said above):
test_results_Cilium-PR-K8s-1.16-net-next_1178_BDD-Test-PR.zip
consoleText.txt

authors: jrajahalme pchaigno

repo: cilium/cilium


text:
IPsec enable failed on EKS: unable to replace state: invalid argument

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I'm failing to install Cilium with IPsec enabled on an EKS cluster. The installation of xfrm states apparently fails with invalid argument (see below).
Cilium Version
quay.io/cilium/cilium:v1.11.1@sha256:251ff274acf22fd2067b29a31e9fda94253d2961c061577203621583d7e85bd2
Kernel Version
5.4.176-91.338.amzn2.x86_64
Kubernetes Version
v1.20.11-eks-f17b81
Sysdump
cilium-sysdump-20220218-132258.zip
Relevant log output
level=error msg="IPsec enable failed" error="unable to replace remote state: invalid argument" local-ip=0.0.0.0/0 reason="CNI Out IPv4" remote-ip=192.168.0.0/16 spi=0 subsys=linux-datapath
level=error msg="IPsec enable failed" error="unable to replace local state: invalid argument" local-ip=192.168.147.13/19 reason="CNI In IPv4" remote-ip=0.0.0.0/0 spi=0 subsys=linux-datapath

Anything else?
Reproduction steps
export COST_REDUCTION=(--nodes 2 --instance-types "t3.medium,t3a.medium" --node-volume-type gp3 --node-volume-size 10 --managed --spot)
eksctl create cluster --name "${NAME}" --region "${REGION}" --tags "${TAGS}" --without-nodegroup
./cilium install --cluster-name "${NAME}" --wait=false --rollback=false --encryption=ipsec
eksctl create nodegroup --cluster "${NAME}" --region "${REGION}" --node-private-networking "${COST_REDUCTION[@]}"

Code of Conduct

[X] I agree to follow this project's Code of Conduct

It's also broken on k8s 1.18 and 1.19.

This is likely the same failure as #18500. The fix #18506 was backported to the v1.11 branch, but v1.11.1 (the version reported in this issue) does not contain that fix yet.

Thanks Tobias! I can confirm the issue is gone if I use the latest images.

authors: pchaigno tklauser


text:
DNS Requests Failing

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

CiliumNetworkPolicy
---
apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: "fqdn"
spec:
  endpointSelector:
    matchLabels:
      org: empire
      class: mediabot
  egress:
  - toFQDNs:
    - matchName: "api.twitter.com"
  - toEndpoints:
    - matchLabels:
        "k8s:io.kubernetes.pod.namespace": kube-system
        "k8s:k8s-app": kube-dns
    toPorts:
    - ports:
      - port: "53"
        protocol: ANY
      rules:
        dns:
        - matchPattern: "*"

When I add a dns matcher rule the dns traffic stalls at:
➜ hubble observe -f --namespace default
Sep 27 17:03:28.858: default/mediabot:55743 (ID:42395) -> kube-system/kube-dns-b8976dfcd-qx8bt:53 (ID:7394) policy-verdict:L3-L4 ALLOWED (UDP)
Sep 27 17:03:28.858: default/mediabot:55743 (ID:42395) -> kube-system/kube-dns-b8976dfcd-qx8bt:53 (ID:7394) to-proxy FORWARDED (UDP)

Before applying the CiliumNetworkPolicy ✅
➜ kubectl exec pod/mediabot -- curl -I -s https://api.twitter.com | head -1
HTTP/1.1 404 Not Found

➜ hubble observe -f --namespace default
Sep 27 16:58:39.732: default/mediabot:39680 (ID:42395) -> kube-system/kube-dns-b8976dfcd-qx8bt:53 (ID:7394) to-stack FORWARDED (UDP)
Sep 27 16:58:39.875: default/mediabot:39680 (ID:42395) -> kube-system/kube-dns-b8976dfcd-qx8bt:53 (ID:7394) to-endpoint FORWARDED (UDP)
Sep 27 16:58:39.886: default/mediabot:39680 (ID:42395) <- kube-system/kube-dns-b8976dfcd-qx8bt:53 (ID:7394) to-stack FORWARDED (UDP)
Sep 27 16:58:39.887: default/mediabot:39680 (ID:42395) <- kube-system/kube-dns-b8976dfcd-qx8bt:53 (ID:7394) to-endpoint FORWARDED (UDP)
Sep 27 16:58:40.017: default/mediabot:46096 (ID:42395) -> 104.244.42.130:80 (world) to-stack FORWARDED (TCP Flags: SYN)
Sep 27 16:58:40.191: default/mediabot:46096 (ID:42395) <- 104.244.42.130:80 (world) to-endpoint FORWARDED (TCP Flags: SYN, ACK)
Sep 27 16:58:40.191: default/mediabot:46096 (ID:42395) -> 104.244.42.130:80 (world) to-stack FORWARDED (TCP Flags: ACK)
Sep 27 16:58:40.481: default/mediabot:46096 (ID:42395) -> 104.244.42.130:80 (world) to-stack FORWARDED (TCP Flags: ACK, PSH)
Sep 27 16:58:40.481: default/mediabot:46096 (ID:42395) <- 104.244.42.130:80 (world) to-endpoint FORWARDED (TCP Flags: ACK, PSH)
Sep 27 16:58:40.767: default/mediabot:46096 (ID:42395) -> 104.244.42.130:80 (world) to-stack FORWARDED (TCP Flags: ACK, FIN)
Sep 27 16:58:40.821: default/mediabot:46096 (ID:42395) <- 104.244.42.130:80 (world) to-endpoint FORWARDED (TCP Flags: ACK, FIN)
Sep 27 16:58:40.822: default/mediabot:46096 (ID:42395) -> 104.244.42.130:80 (world) to-stack FORWARDED (TCP Flags: ACK)

➜ kubectl exec pod/cilium-qk7ps -n kube-system -- cilium monitor | grep 10.60.0.135
Listening for events on 2 CPUs with 64x4096 of shared memory
Press Ctrl-C to quit
level=info msg="Initializing dissection cache..." subsys=monitor
-> stack flow 0x0 , identity 42395->7394 state new ifindex 0 orig-ip 0.0.0.0: 10.60.0.135:39680 -> 10.60.1.85:53 udp
-> endpoint 3359 flow 0x0 , identity 7394->42395 state reply ifindex 0 orig-ip 10.60.1.85: 10.64.0.10:53 -> 10.60.0.135:39680 udp
-> stack flow 0xe543d10a , identity 42395->world state new ifindex 0 orig-ip 0.0.0.0: 10.60.0.135:46096 -> 104.244.42.130:80 tcp SYN
-> endpoint 3359 flow 0x0 , identity world->42395 state reply ifindex 0 orig-ip 104.244.42.130: 104.244.42.130:80 -> 10.60.0.135:46096 tcp SYN, ACK
-> stack flow 0xe543d10a , identity 42395->world state established ifindex 0 orig-ip 0.0.0.0: 10.60.0.135:46096 -> 104.244.42.130:80 tcp ACK
-> stack flow 0xe543d10a , identity 42395->world state established ifindex 0 orig-ip 0.0.0.0: 10.60.0.135:46096 -> 104.244.42.130:80 tcp ACK
-> endpoint 3359 flow 0x0 , identity world->42395 state reply ifindex 0 orig-ip 104.244.42.130: 104.244.42.130:80 -> 10.60.0.135:46096 tcp ACK
-> stack flow 0xe543d10a , identity 42395->world state established ifindex 0 orig-ip 0.0.0.0: 10.60.0.135:46096 -> 104.244.42.130:80 tcp ACK, FIN
-> endpoint 3359 flow 0x0 , identity world->42395 state reply ifindex 0 orig-ip 104.244.42.130: 104.244.42.130:80 -> 10.60.0.135:46096 tcp ACK, FIN
-> stack flow 0xe543d10a , identity 42395->world state established ifindex 0 orig-ip 0.0.0.0: 10.60.0.135:46096 -> 104.244.42.130:80 tcp ACK

After applying the CiliumNetworkPolicy 🔴
➜ kubectl exec pod/mediabot -- curl -I -s https://api.twitter.com | head -1
command terminated with exit code 6

➜ hubble observe -f --namespace default
Sep 27 17:03:28.858: default/mediabot:55743 (ID:42395) -> kube-system/kube-dns-b8976dfcd-qx8bt:53 (ID:7394) policy-verdict:L3-L4 ALLOWED (UDP)
Sep 27 17:03:28.858: default/mediabot:55743 (ID:42395) -> kube-system/kube-dns-b8976dfcd-qx8bt:53 (ID:7394) to-proxy FORWARDED (UDP)

➜ kubectl exec pod/cilium-qk7ps -n kube-system -- cilium monitor | grep 10.60.0.135
Defaulted container "cilium-agent" out of: cilium-agent, mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), wait-for-node-init (init), clean-cilium-state (init)
Listening for events on 2 CPUs with 64x4096 of shared memory
Press Ctrl-C to quit
level=info msg="Initializing dissection cache..." subsys=monitor
Policy verdict log: flow 0x0 local EP ID 3359, remote ID 7394, proto 17, egress, action redirect, match L3-L4, 10.60.0.135:55743 -> 10.60.1.85:53 udp
-> proxy port 44795 flow 0x0 , identity 42395->unknown state new ifindex 0 orig-ip 0.0.0.0: 10.60.0.135:55743 -> 10.60.1.85:53 udp

We installed cilium by running cilium install
➜  cilium install
level=warning msg="WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead." subsys=klog
level=warning msg="To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke" subsys=klog
🔮 Auto-detected Kubernetes kind: GKE
ℹ  Using Cilium version 1.12.2
🔮 Auto-detected cluster name: gke-emp-miles-0db2-europe-west1-b-miles-test
🔮 Auto-detected datapath mode: gke
🔮 Auto-detected kube-proxy has been installed
✅ Detected GKE native routing CIDR: 10.60.0.0/14
ℹ  helm template --namespace kube-system cilium cilium/cilium --version 1.12.2 --set cluster.id=0,cluster.name=gke-emp-miles-0db2-europe-west1-b-miles-test,cni.binPath=/home/kubernetes/bin,encryption.nodeEncryption=false,gke.disableDefaultSnat=true,gke.enabled=true,ipam.mode=kubernetes,ipv4NativeRoutingCIDR=10.60.0.0/14,kubeProxyReplacement=disabled,nodeinit.enabled=true,nodeinit.reconfigureKubelet=true,nodeinit.removeCbrBridge=true,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator
ℹ  Storing helm values file in kube-system/cilium-cli-helm-values Secret
🚀 Creating Resource quotas...
🔑 Created CA in secret cilium-ca
🔑 Generating certificates for Hubble...
🚀 Creating Service accounts...
🚀 Creating Cluster roles...
🚀 Creating ConfigMap for Cilium version 1.12.2...
🚀 Creating GKE Node Init DaemonSet...
🚀 Creating Agent DaemonSet...
🚀 Creating Operator Deployment...
⌛ Waiting for Cilium to be installed and ready...

Toggle to see how we created our cluster in GCP
gcloud beta container \
	clusters create "test-cluster" \
	--zone "europe-west1-b" \
	--no-enable-basic-auth \
	--cluster-version "1.23.8-gke.1900" \
	--release-channel "regular" \
	--machine-type "e2-standard-2" \
	--image-type "COS_CONTAINERD" \
	--disk-type "pd-standard" \
	--disk-size "100" \
	--metadata disable-legacy-endpoints=true \
	--scopes "https://www.googleapis.com/auth/devstorage.read_only","https://www.googleapis.com/auth/logging.write","https://www.googleapis.com/auth/monitoring","https://www.googleapis.com/auth/servicecontrol","https://www.googleapis.com/auth/service.management.readonly","https://www.googleapis.com/auth/trace.append" \
	--max-pods-per-node "110" \
	--num-nodes "3" \
	--logging=SYSTEM,WORKLOAD \
	--monitoring=SYSTEM \
	--enable-private-nodes \
	--master-ipv4-cidr "172.16.0.0/28" \
	--enable-ip-alias \
	--network "projects/emp-miles-0db2/global/networks/default" \
	--subnetwork "projects/emp-miles-0db2/regions/europe-west1/subnetworks/default" \
	--no-enable-intra-node-visibility \
	--default-max-pods-per-node "110" \
	--enable-network-policy \
	--no-enable-master-authorized-networks \
	--addons HorizontalPodAutoscaling,HttpLoadBalancing,GcePersistentDiskCsiDriver \
	--enable-autoupgrade \
	--enable-autorepair \
	--max-surge-upgrade 1 \
	--max-unavailable-upgrade 0 \
	--enable-shielded-nodes \
	--node-locations "europe-west1-b"

NOTE:

I originally thought that this was related to https://github.com/cilium/cilium/issues/21367
I've also messaged the #kubernetes channel in Cilium & eBPF's Slack: https://cilium.slack.com/archives/C53TG4J4R/p1664289703439699

Cilium Version
1.12.2 (v1.12.2-c7516b9)
Kernel Version
Linux/x86_64 5.10.127
Kubernetes Version
1.23 (v1.23.8-gke.1900) [linux/amd64]
Sysdump
cilium-sysdump-20220927-153534.zip
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I believe this is affecting all L7 proxying.
I've followed https://docs.cilium.io/en/latest/observability/visibility/ (and not created any CiliumNetworkPolicy).
If I create a Pod annotated with io.cilium.proxy-visibility: <Egress/53/UDP/DNS>, then DNS resolution fails:
bash-4.3# curl -4 -vvv --max-time 10 http://neverssl.com/
* getaddrinfo(3) failed for neverssl.com:80
* Couldn't resolve host 'neverssl.com'
* Closing connection 0
curl: (6) Couldn't resolve host 'neverssl.com'

➜  hubble observe -f --pod default/mediabot
Sep 28 16:20:49.130: default/mediabot:43257 (ID:5826) -> kube-system/kube-dns-b99c7865d-msfb2:53 (ID:47700) to-proxy FORWARDED (UDP)

If I create a Pod annotated with io.cilium.proxy-visibility: <Egress/80/TCP/HTTP> then DNS succeeds but HTTP fails:
bash-4.3# curl -4 -vvv --max-time 10 http://neverssl.com/
*   Trying 34.223.124.45...
* TCP_NODELAY set
* Connection timed out after 10001 milliseconds
* Curl_http_done: called premature == 1
* Closing connection 0
curl: (28) Connection timed out after 10001 milliseconds

➜  hubble observe -f --pod default/mediabot
Sep 28 16:17:03.630: default/mediabot:39794 (ID:5826) -> kube-system/kube-dns-b99c7865d-2kw5g:53 (ID:47700) to-stack FORWARDED (UDP)
Sep 28 16:17:03.631: default/mediabot:39794 (ID:5824) -> kube-system/kube-dns-b99c7865d-2kw5g:53 (ID:47700) to-endpoint FORWARDED (UDP)
Sep 28 16:17:03.631: default/mediabot:39794 (ID:5826) <- kube-system/kube-dns-b99c7865d-2kw5g:53 (ID:47700) to-stack FORWARDED (UDP)
Sep 28 16:17:03.631: default/mediabot:39794 (ID:5826) <- kube-system/kube-dns-b99c7865d-2kw5g:53 (ID:47696) to-endpoint FORWARDED (UDP)
Sep 28 16:17:03.631: default/mediabot:42146 (ID:5826) -> 34.223.124.45:80 (world) to-proxy FORWARDED (TCP Flags: SYN)
Sep 28 16:17:10.750: default/mediabot:42146 (ID:5826) -> 34.223.124.45:80 (world) to-proxy FORWARDED (TCP Flags: SYN)

In both cases I see nothing in the visibility column:
➜  kubectl get cep
NAME       ENDPOINT ID   IDENTITY ID   INGRESS ENFORCEMENT   EGRESS ENFORCEMENT   VISIBILITY POLICY   ENDPOINT STATE   IPV4          IPV6
mediabot   1083          5826                                                                         ready            10.40.0.223

It sounds pretty similar to this thread from the Cilium Slack https://cilium.slack.com/archives/C1MATJ5U5/p1663843092429399

Observing the same but with cilium installed via helm and the following values.yaml

In both cases I see nothing in the visibility column:

You'll need to have --endpoint-status=policy for that. In my case (and with that flag) the visibility policy was OK

In both cases I see nothing in the visibility column:

You'll need to have --endpoint-status=policy for that. In my case (and with that flag) the visibility policy was OK

Thanks, yep running cilium config set endpoint-status policy sorts that for me.

In our particular case we seem to have narrowed it down to kubernetes/gke version.
We started with the cluster created by the conformance tests and incrementally added differences with our not working cluster.

conformance + private cluster :arrow_right: working :white_check_mark:

gcloud container clusters create test-1 \
                   --zone europe-west1-d \
                   --image-type COS_CONTAINERD \
                   --num-nodes 2 \
                   --machine-type e2-custom-2-4096 \
                   --disk-type pd-standard \
                   --disk-size 10GB \
                   --node-taints node.cilium.io/agent-not-ready=true:NoSchedule \
                   --preemptible \
                   --enable-ip-alias \
                   --enable-private-nodes \
                   --master-ipv4-cidr "172.16.0.0/28" \
	           --no-enable-master-authorized-networks

cilium-sysdump-1-working.zip

conformance + private cluster + network policy :arrow_right: working :white_check_mark:

gcloud container clusters create test-2 \
                   --zone europe-west1-d \
                   --image-type COS_CONTAINERD \
                   --num-nodes 2 \
                   --machine-type e2-custom-2-4096 \
                   --disk-type pd-standard \
                   --disk-size 10GB \
                   --node-taints node.cilium.io/agent-not-ready=true:NoSchedule \
                   --preemptible \
                   --enable-ip-alias \
                   --enable-private-nodes \
                   --master-ipv4-cidr "172.17.0.0/28" \
	           --no-enable-master-authorized-networks \
                   --enable-network-policy

cilium-sysdump-2-working.zip

conformance + private cluster + network policy + newer k8s/gke version  :arrow_right: not working (we see the issue @waltfy described above) :x:

gcloud container clusters create test-3 \
                   --zone europe-west1-d \
                   --image-type COS_CONTAINERD \
                   --num-nodes 2 \
                   --machine-type e2-custom-2-4096 \
                   --disk-type pd-standard \
                   --disk-size 10GB \
                   --node-taints node.cilium.io/agent-not-ready=true:NoSchedule \
                   --preemptible \
                   --enable-ip-alias \
                   --enable-private-nodes \
                   --master-ipv4-cidr "172.18.0.0/28" \
	           --no-enable-master-authorized-networks \
                   --enable-network-policy \
	           --cluster-version "1.23.8-gke.1900" \
                   --release-channel "regular"

cilium-sysdump-3-not-working.zip

Is your "older" version 1.22?

@farcaller yes 1.22.12-gke.300! We're now trying to establish what is different between these K8S+GKE versions.

@farcaller the conformance tests don't specify a version with --cluster version, so they'll get the default, i.e.

I was facing the same issue with "EKS version 1.22". I was not able to curl the service by its name but I was getting response when I curl the service with its IP address.
Service and its IP address.
NAME               TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE
service/frontend   ClusterIP   172.20.83.232   <none>        80/TCP          28h

Response of curl Request
root@helloworld-one-5546d8c74d-bmvjv:/# curl -I -m 3 frontend.kube-system
curl: (28) Resolving timed out after 3000 milliseconds

Response when I was using the IP address of the same service.
root@helloworld-one-5546d8c74d-bmvjv:/# curl -I -m 3 172.20.83.232:80
HTTP/1.1 200 OK
Date: Tue, 18 Oct 2022 12:14:56 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Wed, 24 Aug 2022 04:56:51 GMT
ETag: "29af-5e6f5824ccac0"
Accept-Ranges: bytes
Content-Length: 10671
Vary: Accept-Encoding
Content-Type: text/html

To resolve this issue I upgraded the EKS version to 1.23 and the curl started working with the service name.
root@helloworld-one-5546d8c74d-s5cmk:/# curl -I -m 2 frontend.kube-system
HTTP/1.1 200 OK
Date: Tue, 18 Oct 2022 15:34:45 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Wed, 24 Aug 2022 04:56:51 GMT
ETag: "29af-5e6f5824ccac0"
Accept-Ranges: bytes
Content-Length: 10671
Vary: Accept-Encoding
Content-Type: text/html

Today I have faced with this problem.
I have bare-metal k8s clusters with host based firewall and cilium firewall.
The behavior of Hubble observe was one to one with this issue.
Problem was solved after allowing lxc interface on INPUT chain in iptables on host.
iptables -I INPUT -i lxc+ -p udp -m udp --dport 53 -j RETURN

That got me digging and I ended up finding a host iptables rule that indeed prevented the traffic. FWIW those packets won't pass rpfilter loose validmark.

authors: azalio farcaller milesarmstrong sagar0419 waltfy


text:
ci-e2e-upgrade: Add minor / patch upgrades

The same as implemented in ci-ipsec-upgrade - https://github.com/cilium/cilium/blob/a429bf313fad3180738847221c6ddec0caa484aa/.github/workflows/tests-ipsec-upgrade.yaml#L201-L209.
The vsn derivation steps could be moved to a separate GH action to avoid repetition.

@brb mind adding some more labels so this disappears from the triage queue? help-wanted?

authors: brb lmb


text:
images/runtime: update ubuntu base image

Signed-off-by: André Martins andre@cilium.io

@michi-covalent I was just following the steps here https://docs.cilium.io/en/latest/contributing/development/images/#update-cilium-builder-and-cilium-runtime-images

test-me-please

test-gke

test-1.20-4.18

test-1.20-4.19

test-1.20-4.19

test-1.20-4.19

authors: aanm tklauser


text:
ci: fix missing sysdump as separate workflow in L4LB tests for stable branches

Follow up to https://github.com/cilium/cilium/pull/18380.
Signed-off-by: Ondrej Blazek ondrej.blazek@firma.seznam.cz

All team review requests are covered. Merging.

authors: oblazek pchaigno


text:
images/builder: update proto dependencies

See commits for details.

Marking as ready to merge given there is no functional changes in the generated code.


text:
workflows/push charts: Checkout main branch before set-env-variables

set-env-variables may not exist on older branches, so like other github actions, checkout the default branch before calling set-env-variables.
CI run on a branch testing this change: https://github.com/cilium/cilium/actions/runs/4898128686/jobs/8746928466

/test

/mlh new-flake Cilium-PR-K8s-1.25-kernel-4.19

/test-1.25-4.19

authors: chancez michi-covalent


text:
bpf: egressgw: refactor unit tests

These changes were originally part of https://github.com/cilium/cilium/pull/26215 (to make it easier to add a new test) but I'm splitting them into a separate PR so that they can get backported without the fib_lookup changes, as it's always good to keep CI as much in sync as possible across all branches.
See individual commits for more context.

/test


text:
CNI Changes

New logs to be able to read and correlate with CNI ADD.
Return error on rename.

all related with #4541 issue.

This change is

test-me-please

test-me-please


text:
bpf: Replace join_ep.sh with Golang code

Revive #2411.
Discussions on two recent issues have proposed optimizing out the
compile step for particular aspects of regeneration, by creating a new
map with the desired contents in the canonical location for the map,
then invoking the loader directly to update references to the new
versions of the map without recompiling the datapath code: #3897, #5303.
We have also recently been investigating exporting metrics for
compilation times to optimize the performance of Cilium: #5329.
The current join_ep.sh script doesn't support only compiling or only
loading, and furthermore unless we split this into two different bash
scripts, it will be difficult for proper measurement of the compilation
time vs. load time.
To provide a path to support the above optimization, and also to help
with measuring different parts of endpoint regeneration, refactor the
join_ep.sh script to instead directly invoke each foreign binary
directly from Golang code.
Related: #1600, #1711, #2411, #3897, #5303, #5329

This change is

test-me-please

test-me-please

@tgraf I don't have numbers. But wouldn't bash run exec for each command anyway? This way we remove one exec for calling bash, and one for creating the qdisc.

I don't have numbers. But wouldn't bash run exec for each command anyway? This way we remove one exec for calling bash, and one for creating the qdisc.

Yes, bash might be better at it though ;-)
master now has a detailed breakdown of endpoint regeneration cost so it should be trivial to compare the cost of each

@tgraf seems pretty close, latest code with pipe between clang/llc:
$ git co test/bash-loader && GOCACHE=off GOMAXPROCS=1 sudo -E go test -bench=. -benchtime=60s github.com/cilium/cilium/pkg/datapath/loader && echo "-----" && git co sub
mit/golang-loader && GOCACHE=off GOMAXPROCS=1 sudo -E go test -bench=. -benchtime=60s github.com/cilium/ci
lium/pkg/datapath/loader
Switched to branch 'test/bash-loader'
OK: 1 passed
goos: linux
goarch: amd64
pkg: github.com/cilium/cilium/pkg/datapath/loader
BenchmarkCompileAndLoad              100         943550423 ns/op
BenchmarkReplaceDatapath            2000          55523954 ns/op
PASS
ok      github.com/cilium/cilium/pkg/datapath/loader    215.838s
-----
Switched to branch 'submit/golang-loader'
OK: 1 passed
goos: linux
goarch: amd64
pkg: github.com/cilium/cilium/pkg/datapath/loader
BenchmarkCompileAndLoad              100         974263664 ns/op
BenchmarkReplaceDatapath            2000          54110271 ns/op
PASS
ok      github.com/cilium/cilium/pkg/datapath/loader    216.082s

test-me-please

test-me-please

@aanm what are you interested in benchmarking? The results I posted above hacked in 'compile skip' support to join_ep.sh for the first numbers then used this branch for the second numbers. Those benchmark teats are still in the branch.

@joestringer I've missed the https://github.com/cilium/cilium/pull/5408#issuecomment-417443279 looks good to me

Green build, Need one minor update for cilium-map-migrate:
diff --git a/pkg/datapath/loader/netlink.go b/pkg/datapath/loader/netlink.go
index 7eab014a44a8..1087300c7188 100644
--- a/pkg/datapath/loader/netlink.go
+++ b/pkg/datapath/loader/netlink.go
@@ -22,6 +22,8 @@ import (
        "os/exec"
        "strings"

+       "github.com/cilium/cilium/pkg/bpf"
+
        "github.com/vishvananda/netlink"
 )

@@ -67,7 +69,9 @@ func replaceDatapath(ctx context.Context, ifName string, objPath string, progSec
        }

        // FIXME: Replace cilium-map-migrate with Golang map migration
-       out, err := exec.CommandContext(ctx, "cilium-map-migrate", "-s", objPath).CombinedOutput()
+       cmd := exec.CommandContext(ctx, "cilium-map-migrate", "-s", objPath)
+       cmd.Env = bpf.Environment()
+       out, err := cmd.CombinedOutput()
        if ctx.Err() == context.DeadlineExceeded {
                err = fmt.Errorf("Command execution failed: Timeout")
        }
@@ -82,7 +86,9 @@ func replaceDatapath(ctx context.Context, ifName string, objPath string, progSec
                } else {
                        retCode = "1"
                }
-               out2, err2 := exec.CommandContext(ctx, "cilium-map-migrate", "-e", objPath, "-r", retCode).CombinedOutput()
+               cmd := exec.CommandContext(ctx, "cilium-map-migrate", "-e", objPath, "-r", retCode)
+               cmd.Env = bpf.Environment()
+               out2, err2 := cmd.CombinedOutput()
                if ctx.Err() == context.DeadlineExceeded {
                        err = fmt.Errorf("Command execution failed: Timeout")
                }

test-me-please

test-me-please

authors: aanm joestringer tgraf


text:
Test 67 - hub aaa has no business key relation 'ttt'

Hub 'rtjj_67_aaa_hub' has no business key mapping for relation 'ttt' needed for link 'rtjj_67_aaa_bbb_lnk'
Should not happen, since F1XX_AAA_BK1F_TTT is mapped to the hub for the ttt relation.

Solved


text:
Won't work with ISO-2022-JP

When running Cinch with encoding = "iso-2022-jp", Ruby rises Encoding::CompatibilityError.  The cause is probably because ISO-2022-JP is not compatible with ASCII.  (ISO-2022-JP is commonly used by Japanese in IRCNet.)
(Error message)
/Users/yasu/devel/cinch/lib/cinch/message_queue.rb:68:in `process!': incompatible character encodings: ISO-2022-JP and UTF-8 (Encoding::CompatibilityError)
(Quick fix)
It works, but I'm not sure whether if it is suitable fix.
force_encoding("binary") is required for ASCII incompatible encoding to work.
https://gist.github.com/1528729

Okay, I just pushed the second part of your patch.
The way to deal with ISO-2022-JP in Cinch as of now is the following:

Specify Encoding.default_internal = "utf-8" (or whatever encoding you are using internally/in your source)
Specify `c.encoding = "iso-2022-jp"

This way, Cinch will treat incoming messages as ISO-2022-JP and convert them to UTF-8 (or whatever target encoding you specified) and drop characters it cannot encode.
Note, however, that it will not be possible to use "ISO-2022-JP" as the target encoding.

I have checked current master branch, and it works fine.
So I'm closing this issue.
Thanks.

authors: dominikh hirataya

repo: cinchrb/cinch


text:
Last updates doesn't makes effect on existing installation

Updating on new installation doesn't change last commit done on this package. I think should be a better approach release 2.1.1 version.

@ithustle are you updating via npm or GitHub?

npm. To be more specific, yarn

I think it hasn't been updated on npm yet, I may be wrong though.

@ithustle please use git repo instead npm

@cinder92, roger that. Thanks.

authors: Drazail cinder92 ithustle


text:
🛑 Cioos National CKAN Sitemap is down

In 2000f90, Cioos National CKAN Sitemap (https://catalogue.cioos.ca/sitemap/sitemap-1.xml) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cioos National CKAN Sitemap is back up in b804356 after 3 minutes.

repo: cioos-siooc/cwatch-upptime


text:
🛑 St. Lawrence Global Observatory CKAN is down

In cdd41a0, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: St. Lawrence Global Observatory CKAN is back up in c235f8e after 10 minutes.


text:
⚠ Cioos National CKAN has degraded performance

In 432cc30, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 7532 ms

Resolved: Cioos National CKAN performance has improved in bdc1478 after 5 minutes.


text:
⚠ SmartAtlantic ERDDAP has degraded performance

In e2b1c04, SmartAtlantic ERDDAP (https://www.smartatlantic.ca/erddap/index.html) experienced degraded performance:

HTTP code: 503
Response time: 15408 ms

Resolved: SmartAtlantic ERDDAP performance has improved in ecb1fed after 5 minutes.


text:
Update scalafmt-core to 3.7.13

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.5.9 to 3.7.13
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #406.

repo: circe/circe-jackson


text:
WIP: added documentation for circe-derivation

adds documentation for circe-derivation
closes https://github.com/circe/circe-derivation/issues/188

Thanks! The content looks good to me. The CI failure is because we'll need to add circe-derivation to the docs build (since they're compiled). I can look at that this weekend, unless you want to take a shot at it sooner.

yes i am waiting for the new release of circe-derivation to link to as old will give errors
will update this once after release

@shrynx Ah, got it, makes sense. I'll try to get around to publishing an M4 today.

@travisbrown i added circe-derivation to deps but not sure why is one failing

@shrynx It says the build was stalled, so probably just Travis CI being Travis CI. I restarted the job.

@travisbrown looks like it is getting stuck only on scala 2.12.10

Closed due to age.
Please notify maintainers if this is done in error.

authors: hamnis shrynx travisbrown

repo: circe/circe


text:
Cleanup outdated referencing

As time has passed comparisons to libraries prior have become less and less relevant to the user base.  This attempts to do a very minimal cleanup of this in a first quick pass.
This improves: https://github.com/circe/circe/issues/1937

Codecov Report

Merging #1939 (083343d) into main (a015255) will increase coverage by 0.03%.
The diff coverage is n/a.

:exclamation: Current head 083343d differs from pull request most recent head f23a300. Consider uploading reports for the commit f23a300 to get more accurate results

@@            Coverage Diff             @@
##             main    #1939      +/-   ##
==========================================
+ Coverage   86.13%   86.17%   +0.03%
==========================================
  Files          73       73
  Lines        2532     2532
  Branches      129      129
==========================================
+ Hits         2181     2182       +1
+ Misses        351      350       -1

Flag
Coverage Δ

2.12.15
86.05% <ø> (+0.04%)
:arrow_up:

2.13.8
86.25% <ø> (+0.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
88.88% <0.00%> (+0.58%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-commenter zmccoy


text:
Cache tools And Other stuff

Checklist

[x] I've run make from the root directory to see all Dockerfiles are created successfully.
[x] I've updated the documentation if necessary.

Motivation and Context
A bit of a giant PR in order to get circleci-images green.
Lots of failures are due to hitting the GitHub/BitBucket API rate limits.  Instead of relying on that to download latest, let's cache them in S3 and download from there.  Notice that I'm using latest here instead of a concrete version.  I have considered using concrete versions so it's easy for us to switch back.  However, given that we don't pin versions now and always use latest, and users desiring to pin can always lookup the actual github url and insert it.
Also, fix SBT again :(.  SBT 0.13.6 was released and updated in GitHub without the zipfiles in https://github.com/sbt/sbt/releases - as of yet.  Therefore let's just download it from the SBT website link.
Lastly, noticed that OpenJDK dockerfile inserts the building container PATH!  Fixing that with better escaping behavior.

LGTM. Thanks

authors: marcomorain notnoopci

repo: circleci/circleci-images


text:
Returning files from load function does not work

[x] Before posting an issue, read the FAQ and search the previous issues.

Description
I want to load some default data from a database to initially populate the form. This includes some files.
This seems to work server-side. However, the client does not receive the files. This is inside my load function:
// an example of a file that would come from s3 or whatever
const data = {
  files: [
    new File(['hello'], 'hello.txt', { type: 'text/plain' })
  ]
}

// we validate
const form = await superValidate(data, zod(schema))

console.log('valid on server', form.valid)  // true
console.log('files on server', form.data.files)  // [<the file object we created above>]

return withFiles({ form });

On the client:
$: console.log('files in client', $form.files) // []

If I have more fields in my schema/initial data, those pass through just fine. There are no validation errors anywhere, but the files array never gets to the client.
If applicable, a MRE
Use this template project to create a minimal reproducible example that you can link to here: https://sveltelab.dev/github.com/ciscoheat/superforms-examples/tree/zod (right click to open in a new tab)
See the console logs in the repro. The file is validated fine in the server, but the client does not receive it.
https://www.sveltelab.dev/zqpke6y03pcgu3s

just saw the implementation of withFiles, turns out it actually just removes the files.
is there another way of sending files as initial values?
my use case is a form that is submitted with some attachments, and then can be edited again.
the attachments would be sent from the server to the client such that the attachments can be edited.
i can do this with an api route that i fetch from the client but i was hoping there was an "intended" (superforms-wise) way to do it.

SvelteKit cannot serialize File objects, so you need to handle it yourself, base64-encode the data for example and send it as a string in the load function data, then create the File object on the client before calling superForm.

authors: ciscoheat szethh

repo: ciscoheat/sveltekit-superforms


text:
Publish to Open VSX

Hey, could you maybe publish this extension to https://open-vsx.org/ in addition to Microsoft's VSCode marketplace?
Thanks for your efforts!

Thanks for your suggestion! Just published at https://open-vsx.org/extension/citreae535/sparse-crates

Would it be possible to link both the Microsoft marketplace one and Open VSX one in the README? =D I wasn't able to see them there. It was pretty easy to find when searching in the extensions menu for me, but I find it's usually standard to have a link to it in the README too, which can help make sure it's the official published version
(Thanks for the tool! I've been struggling with an outdated indexes issue with the original crates, which this is already helping with)

Just installed, works. Thanks!


text:
Stopped receiving i3 events after a log out then back in

Today it stopped receiving i3 events. Since I have logging turned off, no clue as to what happened. This only happened once during the course of using it for 6 hours.
Need to figure out what caused it and fix it.

can repro this by doing $mod+shift+r to reload i3. After doing that, the applet stops receiving i3 events.

This should be fixed by now listening to ipc_shutdown and reconnecting.


text:
403 forbidden

Hello!
I set everything up, now that appears:
https://prnt.sc/10qqgn8
I used the Nginx Guide with gunicorn to set it up. Any ideas?

Fixed it by adding
CSRF_TRUSTED_ORIGINS = ['yourdomain']
if anyone faces this issue.

repo: ciur/papermerge


text:
inbox Loop

Description
Can anyone help me? I got Papermerge running in Docker and also edit the papermerge.conf.py under the worker container as described in the Doc to import PDF´s via IMPORTER_DIR = "/path/to/folder"
Whenever i put a Document into the mapped folder, Papermerge starts to scan it but doesn´t stop anymore. As a result: After 20 min. i got the same Document in the inbox at least 20 times and it doesnt stop..
What am i´m missing or doing wrong?
Info:

Papermerge Version [e.g. 3.0.1]
-Papermerge 2.0
OS Ubuntu
via Docker

Got it working now! The mapped folder didn´t had rw permissions so the document couldn´t be deleted or moved after processing it!


text:
Share the CTI page: implement "Don’t forget to star our repository"

closes #817

Added package react-github-btn
Displays star count of the repository.
On click takes the user to the repository.
For reference
https://www.npmjs.com/package/react-github-btn
https://buttons.github.io/

Hi Nandana On checking on my local machine , on  clicking on Star Button It is not going to the repo.

Hi Nandana On checking on my local machine , on clicking on Star Button It is not going to the repo.

Did you do npm install? Because a new react-github-btn package is added.

Hi Nandana On checking on my local machine , on clicking on Star Button It is not going to the repo.

Did you do npm install? Because a new react-github-btn package is added.

Yes I did but it is not working on my side. Can you check with someone else and see if it is working for them

The star button works well. Some suggestions for minor updates. Could any inline component styling be moved to makeStyles (or styles.js if the makeStyles section is getting too large) ?

The inline styles are not from this PR.Do you want me to address the styling for the whole page?

authors: bhaggya nrrao

repo: civictechindex/CTI-website-frontend


text:
Add styling for "My Applications" section

Blocked on mocks in #7988

Closing as duplicate of #7814.

authors: melanie-exygy ssandbekkhaug

repo: civiform/civiform


text:
In cases where the user profile cannot be fetched, or the user is unauthorized, redirect the user to the home page.

Description
In cases where the user profile cannot be extracted from the session or the user is not authorized to access a resource, redirect user to the home page.
Release notes
In cases where the user profile cannot be extracted from the session or the user is not authorized to access a resource, redirect user to the home page.
This can happen if the browser session expires (say, a tab is left open overnight).
Before this PR, we return HTTP error codes to the browser that give no information to the user. It doesn't make sense to create a guest session at this point, because the new account would not be able to access applications of a previous applicant. There is really no reasonable action we can take under these circumstances, so we redirect the user to the home page.
Checklist
General
Read the full guidelines for PRs here

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release | database >
[x] Created unit and/or browser tests which fail without the change (if possible)
[x] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[ ] Extended the README / documentation, if necessary

User visible changes

[ ] Followed steps to internationalize new strings
[ ] Wrote browser tests using the validateAccessibility method
[ ] Tested on mobile view. See mobile device mode
[ ] Manually tested at 200% size
[ ] Manually evaluated tab order

New Features

[ ] Add new FeatureFlag env vars to server/conf/helper/feature-flags.conf
[ ] Conditioned new functionality on a FeatureFlag
[ ] Wrote browser tests with the feature flag off and on, etc.

Issue(s) this completes
Fixes #4944

Current dependencies on/for this PR:

main

PR #5316   👈

This comment was auto-generated by Graphite.


text:
update webtorrent version for iojs support

Solves:
make: Leaving directory '/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:199:12)
gyp ERR! System Linux 3.16.0-38-generic
gyp ERR! command "/usr/local/bin/iojs" "/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/build/wrtc/v0.0.55/Release/node-v44-linux-x64/wrtc.node" "--module_name=wrtc" "--module_path=/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/build/wrtc/v0.0.55/Release/node-v44-linux-x64"
gyp ERR! cwd /home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc
gyp ERR! node -v v2.2.1
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/iojs /home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/build/wrtc/v0.0.55/Release/node-v44-linux-x64/wrtc.node --module_name=wrtc --module_path=/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/build/wrtc/v0.0.55/Release/node-v44-linux-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/node_modules/node-pre-gyp/lib/util/compile.js:73:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:763:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:210:5)
node-pre-gyp ERR! System Linux 3.16.0-38-generic
node-pre-gyp ERR! command "/usr/local/bin/iojs" "/home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/lms/src/GitTorrent/node_modules/webtorrent/node_modules/torrent-discovery/node_modules/bittorrent-tracker/node_modules/wrtc
node-pre-gyp ERR! node -v v2.2.1
node-pre-gyp ERR! node-pre-gyp -v v0.6.4
node-pre-gyp ERR! not ok

@ralphtheninja Thanks, merged!  Feel free to merge these yourself in future, no need to wait for me.

@cjb Gotcha! I'll still leave PRs open a day or two for others to review before merging.

authors: cjb ralphtheninja

repo: cjb/GitTorrent


text:
🛑 GitLab is down

In 7f9b779, GitLab ($GIT) was down:

HTTP code: 502
Response time: 102 ms

Resolved: GitLab is back up in 7c897ab.


text:
Maybe we need to add states for data

Data doesn't exists when being loaded from block chain is too weird to understand for freash developers. I think we need to provide some states to distinguish. I think maybe like as follow.
enum LoadingStates {
  Fresh = 0;
  Loading;
  Loaded;
  NotExist;
}

Do you mean for the first load of the model, we'd wait for some time then the data would be okay?
It's a good idea to tell the developer the model sync status, and it will be better to add a variable for the store model that stores the current sync block number.

Do you mean for the first load of the model, we'd wait for some time then the data would be okay? It's a good idea to tell the developer the model sync status, and it will be better to add a variable for the store model that stores the current sync block number.

Yes, that's what I mean~

authors: Daryl-L yanguoyu

repo: ckb-js/kuai


text:
Feasibility study for the merkle-like solution

Cell model is UTxO-like, and it is hard for us as application developers to get working with it because of shared state, capacity management, and script combination.
An initial idea is that the Kuai framework provides a runtime that is used to help developers write CRUD-style programs that manage off-chain state and generate proofs to update the merkle roots on-chain, i.e., state is stored off-chain and only one merkle root is stored on-chain.
To implement the feature mentioned above, we first need to do some feasibility study, like

dApp user identity via P2SH instead of P2PK(H)
off-chain state transition replayed in the contract without a vm
cross-dApp (contract) communication without a global sequencer
and other...

I think this consideration should be enriched and added to the proposal(General aggregation service section)

I think this consideration should be enriched and added to the proposal

Does it mean that the info in the current proposal is not detailed enough, and we can add the description in this issue to the proposal?

I think this consideration should be enriched and added to the proposal

Does it mean that the info in the current proposal is not detailed enough, and we can add the description in this issue to the proposal?

I think it's not detailed enough in the proposal, there's just a sentence briefly mentioning that SMT-based aggregation service will be provided, with no more direction or schedule of it.
We can grain the strategy and then add them to the proposal

i see, we will make the merkle-like solution part of the proposal more detailed

How is it going

user: specifically, the user of a dApp
developer: developer who will use Kuai
1 Process
flowchart TB
  Actions["Action(s)"]
  Storage["MerkleXStorage"]

  subgraph Transaction
    direction LR
    subgraph Inputs
      MerkleRoot
    end

    subgraph Outputs
      MerkleRoot'
    end

    Inputs -.transition replay.-> Outputs
  end

  subgraph ActionExecutor
    Storage --> State
    State --> State'
    State' --> TransitionProof
    State' --> Storage
  end

  Actions -.-> Sequencer
  Sequencer --> ActionExecutor
  TransitionProof --> Transaction

Action - A request from a user. Users only need to sign the calling method and parameters, rather than transaction. Because users may not know the state before and after the transaction.

Sequencer - It is a pool of temporary actions similar to mempool in the blockchain. It will process the actions sequentially to avoid the UTxO concurrency issue.

ActionExecutor - Execute the action to generate a new state. The state dependency graph will be recorded to ensure that proof can be generated when the transaction is initiated.
An example of a state dependency diagram is as follows:
graph TD;
	action1 -.r.-> state1
  action1 -.w.-> state2
  action2 -.r.-> state2
  action2 -.w.-> state3

In the figure above, action1 reads state1 and generates state2. Action2 reads state2 and generates state3. These dependent states will be used to generate merkle proof.

MerkleXStorage - It is equivalent to a KV large table with infinite space (2 ** 256), and can quickly prove whether a certain state exists. Multiple actions occurred in a short time will share the same proof after the actions being processed by the ActionExecutor.

To Be Determined -  Interaction between contracts. It may also need to ensure the atomicity of transaction across contracts. A clear design cannot be given for now. A fallback scheme is to use a global sequencer for cross contract scheduling, or to work with OpenTx protocol to construct transaction interactions across Kuai dApps.

2 Use case
Take the register of domain names as an example to describe how developers use the kuai.
For example, at the same time, multiple users send requests(or actions) to register domain names:
action1:
{
	"method": "registerDomain",
  "params": {
    "domain": "kuai.bit",
    "_lock": {. "code_hash": "0x.1..." },
    "_signature": "0x.1..."
  }
}

action2:
{
	"method": "registerDomain",
  "params": {
    "domain": "kuai.bit",
    "_lock": {. "code_hash": "0x.2..." },
    "_signature": "0x.2..."
  }
}

action3:
{
	"method": "registerDomain",
  "params": {
    "domain": "kuai-new.bit",
    "_lock": {. "code_hash": "0x.3..." },
    "_signature": "0x.3..."
  }
}

Multiple actions will be processed by the sequencer sequentially. And action1 and action3 will go to the ActionExecutor. However, action2 will be rejected by the sequencer because it conflicts with action1.
Developers develop the ActionExecutor by Kuai to process actions. The process is roughly as follows:
/*
	off-chain
*/

interface BuyDomainPayload {
  domain: string;
}

interface Context {
  requestFrom: LockLike;
  store: MerkleXStorage;
}

// call this method will auto generate the proof
// for replaying state transition in the contract
// should be atomic
@transaction
async function registerDomain(context: Context, payload: BuyDomainPayload) {
  const user = context.requestFrom
  const holder = await context.store.get(["domain_holders", payload.domain])

  if (holder != null) throw new Error("the domain is in use")
  // ...

  await context.store.put(["domain_holders", context.requestFrom], payload.domain)
}

After action1 and action3 are processed by registerDomain, the state dependency graph will be recorded, and finally a transaction will be generated, which will include the proof of the state transition.
The state dependency diagram is as follows:
graph LR;
	state1["state1(lock1,null)"] -.r.-> action1
  action1 -.w.-> state2["state2(lock1, kuai.bit)"]
  action2["<del>action2(rejected)</del>"]
  state3["state3(lock2, null)"] -.r.-> action3
  action3 -.w.-> state4["state4(lock2, kuai-dev.bit)"]

After the transaction is sent to the chain, it will be verified by the contract. The rough description is as follows:

The merkle-like solution stores all the states directly as SMT to avoid the capacity management problem, but in last week's meeting, there was a requirement to let the state be stored directly in the cell, and let the developers choose which solution to use.
This is really a challenging requirement, and I tried to translate this requirement into another question: what kind of state is suitable to be split and stored directly on the chain? Perhaps we can classify states into two categories, one for contract states and one for rights and interests.
Most contracts are stateful, and most of the states within contracts are shared states, which are probably familiar to most developers, such as the current issuance of tokens and the issuance limit, which are used to control the issuance of tokens. Interests can be divided into qualitative interests and quantitative interests, which are often referred to as NFT and FT
When the state is categorized in this way, the transaction structure of action execution is as follows
inputs:
  action_cell:
    type:
      args:
        # only the owner of the lock can generatge an action_cell
        lock_hash
    lock: <empty>
    data:
      contract_id
      call_method
      call_params
      approved_assets
        - approved_capacity
        - approved_udt_and_amount(s)
        - approved_nft(s)
  user_udt_cell:
    lock: # KuaiAssetLock
      args:
        lock_hash # hash of action_cell's change_or_redeem_lock
    type: udt_type_script
    data: udt_data
  user_nft_cell:
    lock:
      args:
        lock_hash # hash of action_cell's change_or_redeem_lock
    type: nft_type_script
    data: nft_data
  user_capacity_cell:
    lock: # KuaiAssetLock
      args:
        lock_hash
    contract_udt_cell:
      lock: kuai_contract_lock
    contract_nft_cell:
      lock: kuai_contract_lock
    contract_cell:
      lock: kuai_contract_lock # KuaiContractLock, config for upgrade policy
      data:
        ascii("Kuai/contract")
        contract_id
        smt_root
      witness:
        transition_proof
    action_cell2: # calls from another user
    action_cell3: # calls from another user
    ...
outputs:
  udt_change_cell
  nft_change_cell
  capacity_change_cell
  contract_cell
  lock: kuai_contract_lock
  data:
    ascii("Kuai/contract")
    contract_id
    new_smt_root

We need to discuss whether such a way is feasible, and if it is a feasible, then we are doing the continued refining of the design

Define action cells is really a good idea to replay actions on the contract. But I think the state can be stored in the cell or witness, we can provide a simple solution to store it in the cell.

After discussion, we think this solution is complicated, so we will suspend it.

authors: Keith-CY felicityin homura yanguoyu


text:
Website not showing signed CLA agreements.

Trying to browse my signed CLA agreements. I've signed at least one or two, but nothing is showing here: https://cla-assistant.io/my-cla

i have the same issue

Did you login at https://cla-assistant.io/ first and then go to that link?

Encountering the same issue here, Signed CLAs page is a blank list.
Replicated it so far on:

Firefox Developer Build (Daily Driver, Privacy extensions enabled and disabled)
Thorium (Stock, no extensions)
Chrome (Stock, no extensions)
Thorium (Stock, no extensions)
All browsers are kept updated to the latest release.

Same issue, please take a look at my conversations with the open source project maintainers: https://github.com/bufbuild/protobuf-es/pull/1001#issuecomment-2447373950

authors: Alexejhero Minothor externl locene srl295

repo: cla-assistant/cla-assistant


text:
Only Works In Live Preview

I am not sure if this is the intended function or if its required as I didn't see it in the documentation; button, hotkey, right-click and command palette all only work if in LE mode.

Thanks for raising this! Confirmed this is a bug and will address

Fixed in version 1.0.3  (commit)

authors: Jnolcox clairefro


text:
🛑 CLAMS Sierra REST API is down

In ee33227, CLAMS Sierra REST API (https://clamsnet.org/iii/sierra-api/about) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CLAMS Sierra REST API is back up in d0a6d1c.

repo: clamsnet/upptime-reports


text:
Problem Compiling from Source

I'm running Solus and trying to compile from source.  It builds "taglib" but fails soon after.
[  4%] Completed 'taglib'
[  4%] Built target taglib
Scanning dependencies of target musikcore
[  4%] Building CXX object src/core/CMakeFiles/musikcore.dir/debug.cpp.o
clang-4.0: error: no input files
/bin/sh: -std=c++14: command not found
make[2]: *** [src/core/CMakeFiles/musikcore.dir/build.make:63: src/core/CMakeFiles/musikcore.dir
/debug.cpp.o] Error 127
make[1]: *** [CMakeFiles/Makefile2:123: src/core/CMakeFiles/musikcore.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

I believe I have all the necessary dependencies installed... Do you have any hints on what my issue might be? Thank you!

This looks similar to what I tried to fix with #129, you might want to try that.

FYI, I just merged @geier's change into master. @cmiles74 try to pull and rebuild.

Yep, that took care of it. Many thanks! :-D

authors: clangen cmiles74 geier

repo: clangen/musikcube


text:
IE11 on Windows 10 change playback url using javascript not working

Browser:  IE 11.162.10586.0
OS*: Windows 10
Clappr Version: 0.2.47
Steps to reproduce:
Step 1: Create javascript function as follows:
function changeurl(url){
player.stop();
player.load(url);
player.play();
}

Step 2: call javascript function to change url:
When a user clicks a button on the page, the javascript is executed with the url present, e.g:
onclick="changeurl(http://example.com/index.m3u8)"

This works in all browsers (including on iOS and Android (well done guys! :+1: ) but sadly not IE11.
The console in IE11 logs the following message after a user clicks:

Confirmed. Great username by the way you've lived up to it :P

Thanks - i do try :) Any ideas how long it might take to resolve?

Can i just check i've understood correctly, we can only use the stop() and pause() events when using html5 playback, load() isn't supported?

@ibreakstuff93 load() is still supported and should work.

@tjenkinson thank you for clarifying! I've just tried it again, but i'm still getting an error message in IE11. It's moved a few lines however this time...

@ibreakstuff93 have you built master containing the fix?
Try this: https://cdn.rawgit.com/tjenkinson/215c450e27f2dc99efaf3d9e53fe1406/raw/756fdbf6f06744714a03456a08926db502a20fb7/clappr.js

Thanks working now :+1:

Sorry for my stupid question, but will this fix get rolled up into the next release? (sorry, i'm still a newbie to github)
Otherwise, I have AES128 encrypted HLS playing back reliably accross all modern browsers, apple, and android! :+1: You guys are the greatest.

@leandromoreira did a release earlier so it should be there now. It's not updated on the cdn yet but that should happen at some point soon.

repo: clappr/clappr


text:
🛑 Applications is down

In 118d955, Applications (https://apps.nsercresnet.ca/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Applications is back up in d4fcc86 after 5 minutes.

repo: clarkwrks/resnet-status


text:
Support for RuntimeClasses

Describe the feature
With the new tenant v1beta2 tenants we can assign RuntimeClasses to Tenants. capsule-proxy should intercept RuntimeClasses and grant privileges according to tenant/proxysettings.
The RuntimeClass feature is documented here (should work like all the other cluster scoped class objects):
What would the new user story look like?
As Enduser I would like to be able to list the RuntimeClasses which are assignable in my tenant.

Closes via #702.

authors: oliverbaehler prometherion

repo: clastix/capsule-proxy


text:
Sortable Container not detecting Sortable Item when it is dragged over unless it is dragged to the lower bottom quadrant of the container

I'm trying to use the Multiple Containers example for creating a drag and drop component with multiple columns with cards that can be dropped into any column. I want every column to have fixed height and width, so I'm setting it in the style.
Running into an issue where if I drag a Sortable Item (a card) over a Sortable Container (a column) which has a fixed height and width, it does not register the drag over event until I drag the card to the lower quadrant of the column. However, if a card exists, it seems to work fine.
This video shows the issue clearly:
https://user-images.githubusercontent.com/9031145/196030726-ee78c224-868f-47c9-83d3-b581298247c7.mp4
The code is:
https://codesandbox.io/s/dnd-kit-multi-containers-forked-sr63b5?file=/src/container.js
Any idea how to fix it and make it so the column always detects a drag over event when a card is dragged into its area so I don't have to drag it all the way to the bottom to drop it?

Did you ever find a solution?

Same issue for me. Anyone found a solution?

Solution Found:
I was able to resolve the issue by implementing a custom collision detection function that combines pointer-based detection with proximity-based detection. Here’s the function I used:
const customCollisionDetection: CollisionDetection = (args) => {
  // Detects collisions based on the pointer position
  const pointerCollisions = pointerWithin(args);

  if (pointerCollisions.length > 0) {
    return pointerCollisions;
  }

  // Falls back to detecting collisions based on closest corners
  return closestCorners(args);
};

To use this in the DndContext, you can set up your component like this:
<DndContext
  {/* other props*/}
  collisionDetection={customCollisionDetection}
>
  {/* Your draggable and droppable components */}
</DndContext>

authors: bramireza imsanchez manuelMoraYolo srahimeen

repo: clauderic/dnd-kit


text:
Initial draft of chapter on approximate solvers for shallow water.

I decided to go ahead and draft the SW chapter first; Euler will be next.  I think this is fleshed out enough that I'd like feedback on it.  Some notes:

There is a lot of code in the notebook.  Some of the boilerplate code that is repeated for each example can, of course, be put in a function and hidden away.  I think we should leave the Riemann solver implementations in the notebook; alternatively we could put each in a file and use the magic command to insert the contents of the file in a cell so readers can easily peruse it.
There are probably too many examples, but I figured I'd include them all and then we could pare it down after discussing what is most important.
I wrote numerical solvers specifically for this chapter even though similar Python solvers exist in clawpack/riemann.  This is partly because the way we're dealing with entropy fixes in the book is not a practical way to do it in a numerical code, and partly because the solvers in Riemann are vectorized and I think it's a lot more natural to include pointwise solvers in the book.

A note about useful Jupyter notebook extensions:  To more easily navigate around the notebook when there is so much code, I've found it very helpful to use the "table of contents (2)" and "collapsible headings" notebook extensions.  I'm trying to use lots of subsections in order to make this even more useful.  I've also found the scratchpad extension to be nice, in general.

Also, my superscripts and subscripts are a mess because I changed my mind about which was better while writing this chapter.  But I didn't go back to make it consistent because I wanted to wait for your feedback on that question.  In this chapter it actually seems nicer to use superscripts for the characteristic index, because when discussing the entropy fix we also want to use a subscript for left/right.

I just added a new final section to this chapter, in which the Roe averages for SW are derived purely from the requirement that the solver be conservative.  @rjleveque I have a couple of questions:

I worked this out because I remember hearing you state the connection between conservation and Roe averaging, but I wasn't sure (until I worked it out) that the Roe average was the only average that gives conservation.
Technically it turns out that there is a second "Roe average", that is a different velocity but is equivalent to the usual one when used in the solver (i.e., the resulting waves and states are the same).  This is of course just a curiosity, but I hadn't heard of it before and wondered whether it was known?

@ketch: I knew that if you use an average other than the Roe average then in general the wave-propagation form won't be conservative, but I never tried deriving the Roe average by this means, and wasn't aware of the second possible choice.  This seems like a simpler derivation that the parameter vector approach introduced by Roe and that I followed in FVMHP.  I wonder if this approach makes it easier to derive Roe averages for other, more complicated, systems.  Have you tried it for Euler?

@rjleveque Thanks for taking a look.  This seems rather interesting now.  It does work for the Euler equations -- and you get two possibilities for the "average" there, too.  I'll add an Euler notebook with the derivation soon.
I also think it is a simpler derivation, but what I especially like is that everything follows from the requirement that $f'(\hat{q}) \delta q = f(q_r)-f(q_l)$ (sorry that this isn't typeset on Github).  There is no magical step of guessing a nice parameterization.  It's also very natural; what we're imposing is almost just requirement (iii) from p. 359 of Roe's original paper.  The only difference is that we additionally assume that $\hat{A}$ is just $f'(q)$ evaluated at some state $\hat{q}$.
It seems like it would be very surprising if nobody had done this before.  But you of all people would probably know about it if they had.  I will see if it works for more complicated systems; do you have any suggestions for one to start with?

By the way, it was just today (while working this out for Euler) that I realized all I was doing was imposing $f'(\hat{q}) \delta q = f(q_r)-f(q_l)$.  Using this directly avoids a bunch of (silly, in retrospect) algebraic manipulation; I've updated the derivation in this PR and now it's extremely simple.

Oh, and for Euler there are also two choices of Roe "average"; they look very similar to the two for shallow water.

After a bit of looking, I found that people have worked this approach out before for the Euler equations.  This is mentioned for instance in Section 3.1 of this paper:
https://doi.org/10.1006/jcph.1997.5838
which in fact says that "several authors" have noticed this.  What seems to be the best extension to more complicate equations of state is in this paper:
https://doi.org/10.1006/jcph.2001.6915
They impose the same condition I'm using and find that for general equations of state you get the same Roe averages for u and H.  You also need a particular average of rho (unlike in the polytropic ideal gas case, where the average of rho does not come into play); this average is determined by an equation that depends on the particular equation of state.

Update: This PR also includes two Euler notebooks now:

One introducing a Roe solver and an HLL solver, and showing what they give for a few Riemann problems.  This follows the same outline as the shallow water chapter on approximate solvers.  It still needs work and is missing some things (including discussion and implementation of an entropy fix).
A second chapter showing results of a shocktube problem obtained by running PyClaw with the Roe and HLL solvers.  This may be outside the scope of the book; I'm open to suggestions in this regard.

In the last commit I've addressed almost all the comments of @rjleveque .  There are probably too many / too large legends now, but we can keep refining that.
The one outstanding comment is about whether to plot u or hu.  In the earlier notebooks on SW and Euler we focused on primitive variables.  If you agree, I can change the approximate notebooks to do the same (plotting u rather than hu).

We should discuss u vs. hu.  Each version is useful for certain things.  The phase plane plots look very different since u blows up while hu goes to zero as h --> 0.
I've always used hu in the past, mostly because [h, hu] are the variables in which the eigenvectors are naturally defined, and these vectors are tangent to the integral curves in the h-hu plane, so this version fits better when describing the differences between linear and nonlinear Riemann problems, I think.
On the other hand, for problems with dry states appearing in the middle, the h-u plane shows what's going on much better.

authors: ketch rjleveque


text:
Add tests to rich object params functionality, and fix tests which were failing on iOS 8

As discussed here and here.

Hey, sorry about that. For some reason I thought your fork was private when I looked for it. I'd probably feel more comfortable doing this as a fork of your work, especially if I'm going to squash the commits, as then your name would be gone from the commit messages.
I'll do this tonight if I get the chance. :)

Closing pull request, since I re-forked from @NorthStar to preserve their commit history..

repo: clayallsopp/routable-ios


text:
🛑 livevault is down

In 17de430, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in fd1fb98.

repo: claytonplong/backup-uptime


text:
🛑 livevault is down

In 0b602c8, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 31f1d71.


text:
🛑 livevault is down

In 26db52b, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 47f3842.


text:
🛑 livevault is down

In 46c5cbf, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 589658b.


text:
🛑 livevault is down

In a652eb2, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 1c50fdd.


text:
RedisConnectionException

I have been trying to implement a Redis cache to allow me implement user password change from multiple client applications.  I think your package may help achieve my goal. However, I am having issue connecting to my Redis server, which is password protected.
I am getting this error message:
RedisConnectionException: It was not possible to connect to the redis server(s). UnableToConnect on 192.168.xx.xx:5900/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 1s ago, last-write: 1s ago, keep-alive: 60s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 6s ago
I changed the default port for my Redis server.
Here is what I have in my Setup.cs file:
services.AddIdentityServer()
// some code...
.AddDistributedRedisCache(options =>
{
var opts = new ConfigurationOptions
{
AbortOnConnectFail = false,
// AllowAdmin = true,
Password = "my-password-here",
Ssl = false
};
opts.EndPoints.Add("192.168.xx.xx", 5900);
options.ConfigurationOptions = opts;
options.Configuration = "{192.168.xx.xx:5900}";
}, options => options.CachingKeyPrefix = "my-identityserver-caching-prefix");
// more code....
Thank you.

Hi!
Did you try connecting to your redis cache with Stackexchange.Redis in a simple application before? I think the connection error has nothing to do with the package. It's part of Stackexchange.Redis, used as a peer dependency of Microsoft.Extensions.StackExchange.Redis

I think I found the issue and have fixed it. The build for version 1.0.1 is currently running. Please update the package as soon as it is available and let me know if it works!
Kind regards,
Sami

Okay, thank you Sami.

I think I found the issue and have fixed it. The build for version 1.0.1 is currently running. Please update the package as soon as it is available and let me know if it works!
Kind regards,
Sami

Sami, thank you so much.  It works now!

Happy to hear that! Enjoy

authors: alsami korlu


text:
Use one proxy per VM

Modify runtime to launch one proxy per VM. This will improve our HA story since there will no longer be a single point of failure on the system (the system-level instance of cc-proxy).
Plan (ordered steps)

[ ] Update the proxy to allow 1 proxy / pod, alongside the system-level systemd cc-proxy service (https://github.com/clearcontainers/proxy/issues/164).
At this point:

multiple instances of cc-proxy will be able to co-exist with the system-level cc-proxy systemd service.

[ ] Update virtcontainers to spawn 1 proxy / pod (https://github.com/containers/virtcontainers/issues/478).
[ ] Re-vendor the virtcontainers changes into the runtime (this issue).
At this point:

the system-level cc-proxy systemd instance won't be being used (although it can continue to run without interfering with the pod-specific cc-proxy instances).
we will lose the KSM feature of cc-proxy because since all the proxy requests will be handled by the pod-specific cc-proxy instances and since we don't want multiple proxies fighting over KSM kernel settings, the KSM code will never be run.

[ ] Create a daemon to replace the KSM functionality in cc-proxy.
[ ] Remove the following features from the proxy:

KSM.
socket activation.
handling code for >1 pods.

[ ] Update packaging for the proxy to do the following: $ sudo systemctl stop cc-proxy.socket
 $ sudo systemctl stop cc-proxy.service
 $ sudo rm /lib/systemd/system/cc-proxy.socket
 $ sudo rm /lib/systemd/system/cc-proxy.service
 $ sudo systemctl daemon-reload

[ ] Release updated packages for proxy, runtime and the new KSM daemon.
At this point, there will no longer be a system-level cc-proxy instance.

/cc @sameo, @grahamwhaley, @sboeuf, @dvoytik.

Hi @jodh-intel,
Overall IMHO this make sense.
Btw, I guess https://github.com/clearcontainers/proxy/pull/107 still make sense with the above plan. Although the PR should be refactored a bit.

@dvoytik yes this would still make sense, but with a lower priority. Having one proxy per VM would solve most of our issues. In case of a proxy crash we would only loose one pod.

authors: dvoytik jodh-intel sboeuf

repo: clearcontainers/runtime


text:
Curated declared license not updating on site

https://clearlydefined.io/definitions/nuget/nuget/-/gmock/1.11.0/1.11.0
This component has been curated as BSD-3-Clause for the declared, but it still shows the PR as pending and the declared is still NOASSERTION. The PR was merged back in December 2021.
https://github.com/clearlydefined/curated-data/pull/16239

After merging in PR #22395, the license seems to be updated on the website -> https://clearlydefined.io/definitions/nuget/nuget/-/gmock/1.11.0/1.11.0.

authors: JacobBovee capfei

repo: clearlydefined/website


text:
Collect search terms on clearlydefined.io/definitions

Sounds like we can get this data through Google Analytics pretty easily. I'd like us to keep logs of searches that return a result even if the user doesn't end up curating anything.

@fossygirl may I suggest to deploy GA via Google Tag Manager (https://tagmanager.google.com). having GTM on CD might be beneficial and allow to deploy multiple Analytics tool via the platform, without additional code changes.

@AlexWebYourmind Sure, that sounds good.

@AlexWebYourmind Is this done and we can close?

I'll close this for now, we may not need this anymore.

authors: AlexWebYourmind fossygirl