[Usernetes] kube-apiserver fails to connect to etcd: dial tcp <IP_ADDRESS>:2379: connect: connection refused

I'm trying to run Usernetes (single-node w/o VXLAN, as a baby step) with bypass4netnsd, but kubeadm fails:
$ export CONTAINER_ENGINE=nerdctl
$ make up
$ make kubeadm-init
[...]
kubelet-start] Starting the kubelet
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.

Looks like kube-apiserver is failing to connect to the local etcd due to dial tcp <IP_ADDRESS>:2379: connect: connection refused,
although the etcd process is running with --listen-client-urls=https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379.
Version

nerdctl: v2.0.0-beta.3
bypass4netns: the current master 2794f7e015ee2179a8f0b2d84bb403cfc2d7c331
Usernetes: gen2-v20240404.1 + the following annotations

diff --git a/docker-compose.yaml b/docker-compose.yaml
index 2ae7291..a036d80 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -39,6 +39,11 @@ services:
       # In addition, `net.ipv4.conf.default.rp_filter`
       # has to be set to 0 (disabled) or 2 (loose)
       # in the daemon's network namespace.
+    annotations:
+      # bypass4netns annotations are recognized since nerdctl v2.0
+      # TODO: enable bypass4netns only when bypass4netnsd is running.
+      "nerdctl/bypass4netns": "true"
+      "nerdctl/bypass4netns-ignore-subnets": "[\"<IP_ADDRESS>/16\", \"${U7S_NODE_SUBNET}\"]"
 networks:
   default:
     ipam:

Logs
$ nerdctl exec usernetes-node-1 sh -euxc 'tail /var/log/containers/kube-apiserver*'
+ tail /var/log/containers/kube-apiserver-u7s-suda-ws01_kube-system_kube-apiserver-e3bb8e1d239fbd21df5a10150d7cf97cddf2ac60f255e7c95e0444372270a590.log
2024-04-04T10:33:23.014467147Z stderr F W0404 10:33:23.014061       1 logging.go:59] [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:23.525905133Z stderr F W0404 10:33:23.525525       1 logging.go:59] [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:23.650741563Z stderr F W0404 10:33:23.650270       1 logging.go:59] [core] [Channel #5 SubChannel #6] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:26.746781506Z stderr F W0404 10:33:26.746363       1 logging.go:59] [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:27.177688658Z stderr F W0404 10:33:27.177096       1 logging.go:59] [core] [Channel #5 SubChannel #6] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:27.255248965Z stderr F W0404 10:33:27.254843       1 logging.go:59] [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:32.660451075Z stderr F W0404 10:33:32.660277       1 logging.go:59] [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:32.928362209Z stderr F W0404 10:33:32.927956       1 logging.go:59] [core] [Channel #5 SubChannel #6] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:34.194906969Z stderr F W0404 10:33:34.194549       1 logging.go:59] [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:2379", ServerName: "<IP_ADDRESS>:2379", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused"
2024-04-04T10:33:38.191445386Z stderr F F0404 10:33:38.190882       1 instance.go:290] Error creating leases: error creating storage factory: context deadline exceeded

$ nerdctl exec usernetes-node-1 sh -euxc 'tail /var/log/containers/etcd*'
+ tail /var/log/containers/etcd-u7s-suda-ws01_kube-system_etcd-5e02fa990f84a688cc176a9c61737122ca6bcaa5545e3629ad824977f582365f.log
2024-04-04T10:32:16.394968121Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.394467Z","caller":"embed/serve.go:103","msg":"ready to serve client requests"}
2024-04-04T10:32:16.395555112Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.395204Z","caller":"embed/serve.go:103","msg":"ready to serve client requests"}
2024-04-04T10:32:16.395949052Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.395687Z","caller":"etcdmain/main.go:44","msg":"notifying init daemon"}
2024-04-04T10:32:16.395974454Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.39574Z","caller":"etcdmain/main.go:50","msg":"successfully notified init daemon"}
2024-04-04T10:32:16.397006609Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.394859Z","caller":"etcdserver/server.go:2571","msg":"setting up initial cluster version using v2 API","cluster-version":"3.5"}
2024-04-04T10:32:16.398486722Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.398168Z","caller":"membership/cluster.go:584","msg":"set initial cluster version","cluster-id":"3f59b4f74cf82b90","local-member-id":"f3b2aef06a662d72","cluster-version":"3.5"}
2024-04-04T10:32:16.399161396Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.398924Z","caller":"api/capability.go:75","msg":"enabled capabilities for version","cluster-version":"3.5"}
2024-04-04T10:32:16.399912362Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.399745Z","caller":"etcdserver/server.go:2595","msg":"cluster version is updated","cluster-version":"3.5"}
2024-04-04T10:32:16.403525952Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.403166Z","caller":"embed/serve.go:250","msg":"serving client traffic securely","traffic":"grpc+http","address":"<IP_ADDRESS>:2379"}
2024-04-04T10:32:16.405592265Z stderr F {"level":"info","ts":"2024-04-04T10:32:16.405178Z","caller":"embed/serve.go:250","msg":"serving client traffic securely","traffic":"grpc+http","address":"<IP_ADDRESS>:2379"}

$ nerdctl exec usernetes-node-1 ps -ef
UID          PID    PPID  C STIME TTY          TIME CMD
root           1       0  0 10:30 ?        00:00:01 /sbin/init
root         108       1  0 10:30 ?        00:00:00 /lib/systemd/systemd-journald
root         121       1  0 10:30 ?        00:00:00 /lib/systemd/systemd-udevd
root         129       1 10 10:30 ?        00:00:26 /usr/local/bin/containerd
root         149       0  1 10:30 pts/1    00:00:02 kubeadm init --config /tmp/kubeadm-config.yaml --skip-token-print
root         388       1  3 10:32 ?        00:00:04 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --container-runtime-endpoint=unix:///var/run/containerd/containerd.sock --pod-infra-container-image=registry.k8s.io/pause:3.9 --runtime-cgroups=/system.slice/containerd.service --cloud-provider=external --node-labels=usernetes/host-ip=<IP_ADDRESS>
root         443       1  0 10:32 ?        00:00:00 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id e0baeca2362cf60e66347e1bca8e1663b0bc33f173f049cc4c288cd31f0a021f -address /run/containerd/containerd.sock
root         453       1  0 10:32 ?        00:00:00 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id 4862c3b92124466a817f12e7ce4882e3602f01e73ff70c68157d758d26777122 -address /run/containerd/containerd.sock
root         487       1  0 10:32 ?        00:00:00 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id aaa4c48903c861beda8db0d2acc6ccddf7006032512d948df01a9d9009b97657 -address /run/containerd/containerd.sock
root         508       1  0 10:32 ?        00:00:00 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id e8179f9642fbd7b705a4c221d2efd167cebeabc47863b90f2966a16bee0f3ca0 -address /run/containerd/containerd.sock
65535        536     443  0 10:32 ?        00:00:00 /pause
65535        547     453  0 10:32 ?        00:00:00 /pause
65535        560     487  0 10:32 ?        00:00:00 /pause
65535        576     508  0 10:32 ?        00:00:00 /pause
root         680     443  0 10:32 ?        00:00:01 kube-controller-manager --allocate-node-cidrs=true --authentication-kubeconfig=/etc/kubernetes/controller-manager.conf --authorization-kubeconfig=/etc/kubernetes/controller-manager.conf --bind-address=<IP_ADDRESS> --client-ca-file=/etc/kubernetes/pki/ca.crt --cloud-provider=external --cluster-cidr=<IP_ADDRESS>/16 --cluster-name=kubernetes --cluster-signing-cert-file=/etc/kubernetes/pki/ca.crt --cluster-signing-key-file=/etc/kubernetes/pki/ca.key --controllers=*,bootstrapsigner,tokencleaner --kubeconfig=/etc/kubernetes/controller-manager.conf --leader-elect=true --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt --root-ca-file=/etc/kubernetes/pki/ca.crt --service-account-private-key-file=/etc/kubernetes/pki/sa.key --service-cluster-ip-range=<IP_ADDRESS>/16 --use-service-account-credentials=true
root         691     487  1 10:32 ?        00:00:02 kube-scheduler --authentication-kubeconfig=/etc/kubernetes/scheduler.conf --authorization-kubeconfig=/etc/kubernetes/scheduler.conf --bind-address=<IP_ADDRESS> --kubeconfig=/etc/kubernetes/scheduler.conf --leader-elect=true
root         815     508  1 10:32 ?        00:00:01 etcd --advertise-client-urls=https://<IP_ADDRESS>:2379 --cert-file=/etc/kubernetes/pki/etcd/server.crt --client-cert-auth=true --data-dir=/var/lib/etcd --experimental-initial-corrupt-check=true --experimental-watch-progress-notify-interval=5s --initial-advertise-peer-urls=https://<IP_ADDRESS>:2380 --initial-cluster=u7s-suda-ws01=https://<IP_ADDRESS>:2380 --key-file=/etc/kubernetes/pki/etcd/server.key --listen-client-urls=https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379 --listen-metrics-urls=http://<IP_ADDRESS>:2381 --listen-peer-urls=https://<IP_ADDRESS>:2380 --name=u7s-suda-ws01 --peer-cert-file=/etc/kubernetes/pki/etcd/peer.crt --peer-client-cert-auth=true --peer-key-file=/etc/kubernetes/pki/etcd/peer.key --peer-trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt --snapshot-count=10000 --trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt
root        1111       0  0 10:34 ?        00:00:00 ps -ef

Trying to isolate the issue from Kubernetes, but apparently the issue can't be reproduced with a simple etcd-only container
$ nerdctl run -it --rm --annotation nerdctl/bypass4netns=1 ubuntu:24.04
root@f601efbaeb12:/# apt-get update && apt-get install -y etcd-server curl iproute2 jq
root@f601efbaeb12:/# ip --json route get 1 | jq -r .[0].prefsrc
root@f601efbaeb12:/# etcd --advertise-client-urls=http://${ip}:2379 --listen-client-urls=http://<IP_ADDRESS>:2379,http://${ip}:2379 &
root@f601efbaeb12:/# : 404 is expected here
root@f601efbaeb12:/# curl http://<IP_ADDRESS>:2379
404 page not found
root@f601efbaeb12:/# curl http://${ip}:2379
404 page not found

I've never tried bypass4netns with nested containers.
This problem seems interesting.
bypass4netns may wrongly hook syscalls and bypass sockets.
I'll investigate this issue.

Workaround: disable bind (it is already fast without bypassing)

https://github.com/rootless-containers/bypass4netns/pull/68

I confirmed the issue.
bypass4netns handles sockets created in nested netns in the container's netns.
This behavior is not expected and bypass4netns should handle only processes with container's netns, not other nested netns.
The below log shows the situation then I created netns and executed iperf3 in a container with bypass4netns.
$ nerdctl run --label nerdctl/bypass4netns=true -p 5201:5202 --privileged -it --rm nested /bin/bash
root@672835bf4c5d:/# ip netns add nested
root@672835bf4c5d:/# mkdir /sys2
root@672835bf4c5d:/# mount -t sysfs --make-private /sys2
root@672835bf4c5d:/# ip netns exec nested iperf3 -s -p 5202
-----------------------------------------------------------
Server listening on 5202
-----------------------------------------------------------
Accepted connection from <IP_ADDRESS>, port 57020
[  5] local <IP_ADDRESS> port 5201 connected to <IP_ADDRESS> port 57036
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  2.49 GBytes  21.4 Gbits/sec
[  5]   1.00-2.00   sec  2.44 GBytes  21.0 Gbits/sec
[  5]   2.00-3.00   sec  2.47 GBytes  21.2 Gbits/sec
[  5]   3.00-4.00   sec  2.50 GBytes  21.4 Gbits/sec
[  5]   3.00-4.00   sec  2.50 GBytes  21.4 Gbits/sec

bypass4netns wrongly bypasses the iperf3 socket.
time="2024-04-06T22:27:04+09:00" level=info msg="socket is registered (state=NotBypassed)" pid=160514 sockfd=3 syscall=setsockopt
time="2024-04-06T22:27:04+09:00" level=info msg="handle port=5202, ip=::" pid=160514 sockfd=3
time="2024-04-06T22:27:04+09:00" level=info msg="bypassed bind socket for 5201:5202 is done" pid=160514 sockfd=3


kdeApplications attribute is not defined

Describe the bug
When building system with configuration that installs KDE applications using kdeApplications.<appname> build fails with
error: --- UndefinedVarError ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- nix
at: (17:5) in file: /nix/store/k8arnxqi994qk5klsvyrkhvflmg82mkf-source/users/alapshin/apps.nix

    16|     libreoffice-fresh
    17|     kdeApplications.ark
      |     ^
    18|     dolphin

undefined variable 'kdeApplications'
(use '--show-trace' to show detailed location information)

But if same application is specified without using kdeApplication prefix then build succeeds, however not every application is available directly from top-level scope.
Expected behavior
Applications should be available via kdeApplications scope
Additional context
It was working fine with nixpkgs at revision at b3616bd96400ce0252c241d76fcafb64389defc6.
If there is some way to bisect nixpkgs revisions when they are specified in flake.lock I would appreciate it. Then I can try to find commit that broke this using bisect.
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.9, NixOS, 21.03.20210122.b60a6af (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4pre20201205_a5d85d0`
 - channels(root): `"nixos-21.03pre259923.c958c1b6b2f"`
 - channels(alapshin): `""`
 - nixpkgs: `/nix/store/d8rbyy2cprgx9v8iyjrak1hznpjjaqdq-source`

I was able to pinpoint this issue to commit b209617ff0a8f26ea1d1fe3716a7fa717a50dd95
There new set plasma5Packages is introduced. Using this set applications can be installed as plasma5Packages.ark instead of kdeApplications.ark.
@FRidh Could you confirm if this is expected behavior or not?

I was able to pinpoint this issue to commit b209617ff0a8f26ea1d1fe3716a7fa717a50dd95
There new set plasma5Packages is introduced. Using this set applications can be installed as plasma5Packages.ark instead of kdeApplications.ark.
@FRidh Could you confirm if this is expected behavior or not?

It's also possible there's a scoping mistake. plasma5Packages.kdeApplications.ark will also work.

It's also possible there's a scoping mistake. plasma5Packages.kdeApplications.ark will also work.

Moving kdeApplications was on purpose. I am not sure whether we should keep the subset kdeApplications, because it may be harder to override.
plasma5Packages is an alias to the libsForQt5 used to build the Plasma desktop.

Moving kdeApplications was on purpose. I am not sure whether we should keep the subset kdeApplications, because it may be harder to override.
plasma5Packages is an alias to the libsForQt5 used to build the Plasma desktop.

There is still the task to link individual applications from top-level.

There is still the task to link individual applications from top-level.

Believe we also need to update Qt docs for nixpkgs?

Believe we also need to update Qt docs for nixpkgs?


Social Media Sharing

Hi,
May I know if there's a feature for social media sharing like disqus? This would be amazing.

No that's not available yet. Might also not be part of comments-ui, as it doesn't relate to commenting.


Missing "Updateable" property on filter descriptor in NEST

NEST/Elasticsearch.Net version 7.4.1:
Elasticsearch version 7.4.1:
Add Updateable property to filter definitions in NEST:
I am using NEST to setup a synonym_graph filter, but I am not able to define the filter as updateable so I can reload it through the "_reload_search_analyzers" endpoint (for reloadig synonym files).
Example:
...SynonymGraph("synonym_graph", sg => sg.SynonymsPath("synonym_en.txt"))
As this does not have a "Updateable" property I cannot reload the synonyms as recommended here: https://www.elastic.co/blog/boosting-the-power-of-elasticsearch-with-synonyms

Thanks @johanandrel, I've opened https://github.com/elastic/elasticsearch-net/pull/4257

Thanks @johanandrel, I've opened #4257

Great, thank you! Any hints on when version 7.5 of NEST will released? This is the only missing piece for a client solution :)

This is something I'm interested in as well!

We're aiming to have a 7.5.0 release out early next week. There's a few items on the 7.5 meta ticket https://github.com/elastic/elasticsearch-net/issues/4232 to tackle, and some other issues raised that we'd like to address for this release.


Question: upgrade from Pop OS 20.04 to 22.04

I have a setup of 20.04 according to instructions at https://mutschler.eu/linux/install-guides/pop-os-btrfs-raid1-20-04/ . What is the best practice on upgrading to 22.04?

Backup all data on separate drive, fresh install of 22.04, and restore the data?
Live update on top of existing system?  Any precautions?

Usually, you can just do a live update.
Step 1: MAKE A BTRFS SNAPSHOT!
Step 2: MAKE AN ADDITIONAL OFFSIDE BACKUP!
Step 3: Follow the steps outlined here.
I will do it now on my server and report back :-)

Okay, it hangs at reboot while doing
/scripts/init-bottom
/scripts/local-bottom

I need to investigate this further.

Okay, the issue was that my system drive had no space left. So I booted into recovery, mounted the system drive and deleted a huge folder to have a couple of gigs available again. Restart and boom I am running Pop!_OS 22.04.
So before running the upgrade, make sure you have enough free space available, e.g. looking at
sudo btrfs fi usage /

Long story short: Live update works!


Added Git for Professionals Tutorial at free-courses-en.md

What does this PR do?
Add resource
For resources
Description
A git tutorial from freeCodeCamp's YouTube channel
How do we know it's really free?
It's available free on YouTube
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

For youtube, we prefer "playlist" links and the name of the producer/creator.


Top navbar display is broken on older crates

Example on chrono:

I think this regression comes from https://github.com/rust-lang/docs.rs/pull/1597.
cc @jsha

Thanks for flagging. I'll take a look.


Issue when running the main script

Hey, I'm getting the following error after running python3 tenbis-report.py, seems like the script was able to find 2 vouchers, and then at some point, it collapsed.

My email<EMAIL_ADDRESS>10x for your help

Hi,
A good start would be changing "DEBUG = False" to "DEBUG = True" and then running and sharing more information.

To obtain more accurate information for your situation, you can make a less elegant adjustment by modifying line 182 as follows:
if (not DEBUG):
This will result in fewer irrelevant debug details being displayed.

Alright I manipulate line 182 as you suggested and till 10-2022 we only get a successful status code (200).

Error raised with specific bar code 'תקלה בהבאת הברקוד' Data object was returned with empty Vouchers list [] which probably;y cause for the issue since resp_json['Data']['Vouchers'][0] don't exist we got empty list instead.

I've pushed a change to handle better this kind of backend error coming from 10Bis.
You can try it.

Hey @Dvirus89 I pull all the changes but now it falls on another part.
Adding here a print screen of the case, 10x in advance.
Generally said the tool is really cool, kudos on that !

Oh, I've left a test I made and didn't delete it.
I removed it now.
You can try it now if you like.

@Nirsisr, I had to remove your comment as it exposed your barcode.
putting it here again (censored):
Hey @Dvirus89 I pull all the changes but now it falls on another part.
Adding here a print screen of the case, 10x in advance.
Generally said the tool is really cool, kudos on that !

@Dvirus89 the fix work perfectly.
10x, you can close the issue reported.


Feature items order and position

I've added a fourth feature item to the homepage (the one about the new site). I'd expect it to appear first because it's the newest (or be able to control the order on the homepage through the order on in the tree) but the item is currently appearing fourth and in an odd place on the page. See screen grab. Please could you fix? Thanks.

This is the Isotope.JS and the default sorting. The design lends itself to content of varying heights, can this be handled in content @CatherineIles?

Ordering is now also resolved.


Adding Custom Mousepad Layout and Edited OpenRGB

Fixed Cooler Logo and Mainboard Logo, now beeing controllable as well and not pheripheral anymore

failed

failed

Fixed Cooler Logo and Mainboard Logo, now beeing controllable as well and not pheripheral anymore

Fixed Cooler Logo and Mainboard Logo, now beeing controllable as well and not pheripheral anymore


Add support for DNU

PR already created. See #533.

FYI that the whole DNU stack will be changing at somepoint between now and AspNet RTM.

Yeah, we know :smile: We'll just update it or deprecate it if it's
completely useless by then. Thanks for pointing this out though :+1:
On Dec 7, 2015 17:07, "Richard Simpson"<EMAIL_ADDRESS>wrote:

FYI that the whole DNU stack will be changing at somepoint between now and
AspNet RTM.
—
Reply to this email directly or view it on GitHub
https://github.com/cake-build/cake/issues/540#issuecomment-162569985.


Sending Headers?

Hello.
I've tried various ways to send a header and I get errors.  What is the preferred way to send a header?
This is the error I get:
   EXCEPTION: header is not defined
Here is what I'm trying to do.
<?
var http  = require('http');
var fs    = require('fs');

fs.readFile('/home/userName/var/lib/images/image.jpg', function(err, data) {
  if (err) throw err; // Fail if the file can't be read.
  header('Content-Type', 'image/jpeg');
  write(data);
});
?>

It may be because your header() is inside a function, so it doesn't have access to cgi-node's scope. I would try to bind it to this.
fs.readFile('/home/userName/var/lib/images/image.jpg', function(err, data) {
if (err) throw err; // Fail if the file can't be read.
header('Content-Type', 'image/jpeg');
write(data);
}.bind(this));
or move it out of the function.

I moved the response.headers outside of the function and added header for 'Content-Length'.
I got a little bit further.  Any suggestions on how to get passed this error?
Now it is returning the error:
The image "https://www.iqaat.com/testScripts/image1.jss" cannot be displayed because it contains errors.

<?
  var fs      = require('fs');

  var stats = fs.statSync('/home/userName/var/lib/images/image.jpg');
  var fileSizeInBytes = stats["size"];

  response.headers = {'Content-Type': 'image/jpeg'};
  response.headers['Content-Length'] = fileSizeInBytes;
  response.sendHeaders();

  fs.readFile('/home/userName/var/lib/images/image.jpg', function(err, data) {
    if (err) throw err; // Fail if the file can't be read.

    response.write(data);
  });
?>

  response.headers['Content-Length'] = fileSizeInBytes;

response.headers is just an object {}, so I would add all of your headers in one assignment.
response.headers = {'Content-Type': 'image/jpeg', 'Content-Length': fileSizeInBytes};

I tried loading that image, and it returned this.
^Q?t
95{[
xV-C
Oird
\F=I

EXCEPTION: undefined is not a function
TypeError: undefined is not a function
    at CgiHttpResponse.end (/home1/iqaatcom/public_html/cgi-bin/cgi-node.js:493:11)
    at /home1/iqaatcom/public_html/testScripts/image1.jss:15:14
    at fs.js:340:14
    at FSReqWrap.oncomplete (fs.js:101:15)

That gives you a line number. Also try moving response.sendHeaders(); to the end of your script and moving everything but the headers to a separate file using include('file.js').

How did you get all of the extra return text?  That would be helpful with trying to get this to work.

I used cURL, but can't reproduce the error. I suspect your headers are wrong. Try changing your content-type to text/html. Use the log function I pasted to debug the code. Good luck!

The only thing I can think of, is that CgiHttpRequest and CgiHttpResponse are not ready yet so something is not working on sending the data and ending the request.  :-(

No, the author isn't maintaining this repo. That you can see an error from cgi-node in curl would suggest its your code, not the cgi wrapper. Undefined means one of your variables are not returning the value they are supposed to. Look through your code again.


Add tint to menu bar icon to indicate mute status

Hi there! Many thanks for this great app. It even works with bluetooth headphones output and a different input in macOS Monterey.
Could you make the status bar icon red when the app is muting audio input? This would make it stand out a lot more, specially in high-res displays.
Thanks!
Edit: or even better, instead of red when muted, add an orange tint when the mic is unmuted, to keep color and UX in line with the native audio capture indicator.

hi, the dot just indicated if an app uses the microphone/camera. as this app just sets the system settings and don't use the microphone itself, the dot would be the wrong way.
I've added an option to set the background of the menubar icon to red if the mic is muted.

I know, I didn't mean to add a dot.
I mean to tint the unmute icon in the menu bar with the same color as the orange icon. This way the UX leverages the meanings already learned by users, but applied to the system level instead of to the app level.
No orange color (equivalent to no orange dot) = mic is closed to the system
Orange color (equivalent to orange dot) = mic is open to the system
I imagine there must be a way to tint the image template you use for the unmute icon, instead of filling the whole background. I found this. I'm sorry I can't be of more help, thanks anyway for the great work!


[DISCUSSION] 2024 Q4 / 2025 Q1 Roadmap

Is your feature request related to a problem or challenge?
The last roadmap discussion we had seems to have worked out well to galvanize and get us organized around some common goals

https://github.com/apache/datafusion/issues/11442

Describe the solution you'd like
Let's collect any projects that people think they are likely to spend time on or projects that the broader community would really like to see done and write them down!
Describe alternatives you've considered
No response
Additional context
No response

BTW my personal plans over the next few months are likely going to be focus on consolidating some of the gains / improvements we have made recently. That includes:

External communication / documentation
with @SamSynnada like  https://github.com/apache/datafusion/discussions/13049
https://github.com/apache/datafusion/issues/11631

Improve the project's documentation

https://github.com/apache/datafusion/issues/11172
https://github.com/apache/datafusion/issues/12393
https://github.com/apache/datafusion/issues/7013

Performance wise I plan to

help work on more advanced parquet predicate pushdown with @XiangpengHao https://github.com/apache/datafusion/issues/3463
Continue to flesh out the grouping code: https://github.com/apache/datafusion/issues/12680

I am not sure if this is the place for it but I have been putting a lot of work into dft and plan on doing a release before end of year.

For anyone else following along, dft is https://github.com/datafusion-contrib/datafusion-dft

I am not sure if this is the place for it but I have been putting a lot of work into dft and plan on doing a release before end of year.

I may want to help delta / iceberg integration, I think they are quite important

I may want to help delta / iceberg integration, I think they are quite important. But I will work on performance task first

@jayzhan211 I agree, they are very important. Unfortunately, we have been held up because of the crates using different versions of datafusion.  The idea was to converge on 42 - which iceberg and hudi currently use but deltalake (which we already have an integration for) is on 41 and hasnt been able to upgrade yet.  It looks like they are skipping version 42 now and will use 43 - so hopefully this is resolved soon.
Here is some relevant work

Integrate Hudi
Implement TableProviderFactory for Iceberg

@jayzhan211 and to be more explicit on my release plans, i did not plan on releasing until iceberg and hudi were added.

LogicalType is important too https://github.com/apache/datafusion/issues/12622

I may want to help delta / iceberg integration, I think they are quite important. But I will work on performance task first

@jayzhan211 I agree, they are very important. Unfortunately, we have been held up because of the crates using different versions of datafusion.

I think another potentially very interesting approach here will be to use the FFI bindings from @timsaucer:

https://github.com/apache/datafusion/pull/12920
https://github.com/apache/datafusion/pull/13183

The idea there would be to wrap the delta / iceberge in a stable ABI (aka the FFI bindings) so we could call delta.rs / iceberg which used a different version of DataFusion from dft.

I think as soon as DataFusion 43.0.0 is released we'll be able to test it out:

Update dft to DataFusion 43
Implement a crate binding (in dft to delta-rs with older datafusion version)

It should be quite sweet

I don't know if this discussion is the place we want to track work in the other related projects, but my top goals for 2024 Q4 are:

Get the datafusion-python and delta-rs integration over the line using FFI https://github.com/apache/datafusion-python/pull/921
Adding a user tutorial for datafusion-python https://github.com/apache/datafusion-python/issues/842
Evaluating cuDF integration either in datafusion-python or datafusion https://github.com/apache/datafusion-python/issues/936 - this might be Q1 2025
Adding QueryPlanner to datafusion-python and implementing a custom query planner in datafusion-ray so that we can run all datafusion commands that perform execute() on the dataframe and it just knows to how to run them distributed
Probably looking to expose more of the SessionContext via FFI

One thing thats not clear to me with the FFI approach is who the intended owner of the bindings are - should it be dft as i dont want to worry about my deps being on different datafusion versions or is it more for the table providers crates (iceberg, deltalake, hudi, etc)?
Of course in the short term it could be prototyped in dft and contributed back to those repos but im asking more in the target state where the appropriate home would be.

One thing thats not clear to me with the FFI approach is who the intended owner of the bindings are - should it be dft as i dont want to worry about my deps being on different datafusion versions or is it more for the table providers crates (iceberg, deltalake, hudi, etc)?
Of course in the short term it could be prototyped in dft and contributed back to those repos but im asking more in the target state where the appropriate home would be.

The version of DataFusion used in the bindings has to match the client program (dft in this case) so I don't think they can go in the delta/iceberg crates
One thing we might be able to do is have a separate crate like datafusion-delta-table-provider that has different feature flags for different DataFusion versions 🤔  -- but I am now more or less wildly speculating

@matthewmturner Do you have anything in mind moving forward for integrating the rest of the data lakes? (such as a list of what needs to be done moving forward)

@matthewmturner Do you have anything in mind moving forward for integrating the rest of the data lakes? (such as a list of what needs to be done moving forward)

Yes, now that DataFusion v43 has been released I am hoping that the rust implementations of the three main data lake formats (Deltalake / Iceberg / Hudi) update to that version.  Then I will:

Update the existing Deltalake integration
Refresh the current Hudi PR
Add Iceberg integration which should be pretty easy now that it implements TableProviderFactory

I am interested in the FFI bindings but I don't anticipate working on that prior to the current release I am planning.

I have had a few days to reflect , and I personally think making it easy to integrate DataFusion into the "open data lake" stack might be my top priority over the coming months
@julienledem wrote up a very nice piece descsribing this The advent of the Open Data Lake
In my mind, the specific work this entails stuff like

Making it easier to use iceberg/delta/hudi with DataFusion
Document different tokio runtimes
Make parquet reader in arrow-rs faster/better on remote object stores

More to come

@alamb can you expand on the different runtimes point? Are referring to having a dedicated tokio runtime for CPU bound work? I actually have a ticket open for that - if that is a very important item for you I can add it to the list to do before releasing.

@alamb can you expand on the different runtimes point? Are referring to having a dedicated tokio runtime for CPU bound work? I actually have a ticket open for that - if that is a very important item for you I can add it to the list to do before releasing.

This is what I had in mind:

https://github.com/apache/datafusion/issues/12393

Thanks for the link to the dft one. That is a good one

@alamb i will work on that next. will ping you when ready for review.

More to come

I filed

https://github.com/apache/datafusion/issues/13456

to try and organize my thoughts here better

Cross Posting:

Discussion about making it easier to use DataFusion https://github.com/apache/datafusion/issues/13525


LB: Modernize registration

LGTM but I agree with @Wingpad that we should add explicit deprecation if we can. Anything that helps us move towards actual removal of that old code.
I also feel like the usage of lambdas and the templated function is a bit funky, just in that it feels like we are adding yet another piece on top of an already kinda long function call stack just to register an LB. But I think this is definitely a step in the right direction.

I agree it's a bit complex, but I think it's worth doing this for the added flexibility and to remove the reliance on macros.

LGTM but I agree with @Wingpad that we should add explicit deprecation if we can. Anything that helps us move towards actual removal of that old code.
I also feel like the usage of lambdas and the templated function is a bit funky, just in that it feels like we are adding yet another piece on top of an already kinda long function call stack just to register an LB. But I think this is definitely a step in the right direction.

I agree it's a bit complex, but I think it's worth doing this for the added flexibility and to remove the reliance on macros.


Revert "Revert "allow self signed certs with insecureSkipVerify""

Reverts heptio/velero#1776, which is a revert of #1769
I'd like to bring this code up, as it'd be great if we could have this feature. I don't think I can put in the time to support support custom CA bundles per https://github.com/heptio/velero/issues/1027#issuecomment-523119113 now. I understand that insecureSkipVerify is insecure--hence the warnings. If I can get the code in, awesome. Otherwise, our team will live with our fork until we move away from self-signed certs.
Can we discuss about this topic on this PR?
relates to #1027

@s12chung based on all of the discussions, we've decided that we'll go ahead with getting this PR merged. I'll take a look at the code later today and provide any feedback. We may want to tweak the messages/documentation to make it super-clear that this is an insecure option.
cc @nrb @carlisia @prydonius

We talked about potentially removing the insecure option from the server, and only allowing insecure connections from the client. This way, you would have to use a self-signed cert for the server -> object store connection, but in the client you can use --insecure-skip-tls-verify for debugging purposes. Would that work for you @s12chung?

@prydonius I believe the server would need access to a secret that contains the cert. I'm good with that :) I just don't have the time to implement/test it on our end right now.

@s12chung yeah, we would need a separate PR to accept a self-signed cert and add that to the certificate chain. Good to hear that would work for you, I think that will mitigate the attack surface of this change.

@prydonius without the insecure option on the server, I think the server would run into the same error the client does. unless

I believe the server would need access to a secret that contains the cert.

rebased. changed the changelog and added the suggested changes.

@nrb @carlisia @prydonius PTAL.


feat(fares): add fare limit

Reviewing this now after conveyal/r5#453. This appears to contain some hacks that made the new R5 useable before we did a proper merge. We are probably ready to merge this soon though - we should discuss how and when to get this into a backend release.

Closing in favor of #185, which cherry picks the relevant commits and avoids the hacks needed for a build before the R5 changes were merged.


Deleting entries from bulk upload & better msg on error

Example of new message (fix for #941):

Error: Error saving data to the database: UNIQUE constraint failed: workshops_person.username (for "Piotrek Banaszkiewicz banaszkiewicz_piotr<EMAIL_ADDRESS>host at 2015-02-21-Krakow"). Please make sure to fix all errors listed below.

#942 was fixed by adding a view responsible for removing entries from the session.

@narayanaditya95 I'm going to wait for #989 and then rebase.

Travis build can't download Python3.5 to conduct testing, but here's the passing build for my branch: https://travis-ci.org/pbanaszkiewicz/amy/builds/157407148


DarkMode

I would like to propose the addition of a Dark Mode feature to improve accessibility and user experience. Many users prefer dark interfaces, especially when working in low-light environments, as they reduce eye strain and improve readability.

please assign me this task...


HIVE-27798: Corrected wrong hive-site.xml

hive.metastore.warehouse.dir, this configuration item is configured incorrectly, causing the configuration item to not take effect.
bug image:

fix image：

What changes were proposed in this pull request?
I changed the packaging/src/docker/conf/hive-site.xml file.

Why are the changes needed?
I discovered this bug when I was using it. Since there is no default directory for non-root users in the container, error messages appear when creating databases and data tables without permission. I corrected hive.metastore.warehouse.dir configuration. This error has been resolved.
The correct related configuration items are in the picture below.

Does this PR introduce any user-facing change?
Now there will be no errors when creating databases and tables in docker containers, and the data and directories will appear in the specified directory.

Is the change a dependency upgrade?
No

How was this patch tested?
UT

Sorry, this is my first time submitting Pull Requests. https://github.com/apache/hive/pull/4796 jira number was wrong, so I resubmit.
This is my issue jira: https://issues.apache.org/jira/browse/HIVE-27792

Please don't create duplicate PR，one is enough.


[AEM CS Deployment] Suppress false positives during SonarQube scan

User does not control the tempfile name creation

Not to jinx it... so far so good


implement trace_continuation_strategy

What does this pull request do?
Implements https://github.com/elastic/apm/blob/main/specs/agents/trace-continuation.md
Related issues
closes #1472

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-06-02T08:03:56.865+0000

Duration: 14 min 27 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
2068

Skipped
1993

Total
4061

Steps errors
Expand to view the steps failures

Show only the first 10 steps failures

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.6-pymysql-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.6-mysqlclient-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.6-pymemcache-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.6-graphene-2

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.6-httpx-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.6-httplib2-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.6-prometheus_client-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.6-kafka-python-newest

Archive the artifacts

Took 0 min 0 sec . View more details here
Description: [2022-06-02T08:18:21.092Z] Archiving artifacts
Python-python-3.6-django-1.11 tests failed : hudson.

Error signal

Took 0 min 0 sec . View more details here
Description: Python-python-3.6-none tests failed : hudson.AbortException: script returned exit code 2

:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

:globe_with_meridians: Coverage report

Name
Metrics % (covered/total)
Diff

Packages
100.0% (68/68)
:green_heart:

Files
100.0% (227/227)
:green_heart:

Classes
100.0% (227/227)
:green_heart:

Lines
88.946% (16987/19098)
:-1: -0.567

Conditionals
75.16% (3056/4066)
:-1: -1.428


Frozen Map stuck at an old location

No matter where i reboot the app and log in, i am brought back to an old location and the map is frozen, cant see any stops or pokemon on the app, nor can I zoom out/go to another location.
Anyone know what might have caused this/how to resolve this issue?
Thanks in advance

I'm having similar problems, expect I can move the marker around. Doesn't show stops, gyms or pokemon. Not even when I put the marker downtown.


README.md: correct book name and link to it

Plus minor grammar fixups.

These examples accompany the "Raspberry Pi Pico Python SDK" book which forms part of the technical documentation published by Raspberry Pi Trading, not "Get Started with MicroPython on Raspberry Pi Pico" by Raspberry Pi Press.

These examples accompany the "Raspberry Pi Pico Python SDK" book which forms part of the technical documentation published by Raspberry Pi Trading, not "Get Started with MicroPython on Raspberry Pi Pico" by Raspberry Pi Press.


Fix GPUReduceBankConflictsPass for zero rank memref.alloc

-- This commit fixes GPUReduceBankConflictsPass for zero rank
memref.alloc op.
Fixes this dispatch which we get during int8 quantization of a LLM.
Repro command :
iree-compile --iree-input-type=tm_tensor --iree-vm-bytecode-module-output-format=flatbuffer-binary --iree-hal-target-backends=cuda --mlir-print-debuginfo --mlir-print-op-on-diagnostic=false --iree-llvmcpu-target-cpu-features=host --iree-hal-cuda-llvm-target-arch=sm_80 --iree-stream-resource-index-bits=64 --iree-vm-target-index-bits=64 --iree-vm-bytecode-module-strip-source-map=true --iree-util-zero-fill-elided-attrs --iree-hal-dump-executable-sources-to=ies --iree-vm-target-truncate-unsupported-floats --iree-codegen-check-ir-before-llvm-conversion=false --iree-vm-bytecode-module-output-format=flatbuffer-binary

Signed-off-by: Abhishek Varma<EMAIL_ADDRESS>

So the canonicalization suggested in #14314 should avoid the problem as well, although this is still worth guarding in this pass. The other part of the problem is that this pass shouldn't be padding allocations other than the ones for the batch_matmul calculation but that's harder to fix without going to something like transform dialect.

Hi @qedawkins
So, I just checked - I was indeed using that patch while testing in another iree clone (from which I extracted the IR).
The updated fix will soon be pushed I guess. Referring to this comment.
I've addressed your comments in this PR since you've rightly pointed out that we'd anyway be needing this guard.
You may re-review/approve. :)


Rhmap 7473 [WIP]

@maleck13 The hook to build the docker image here is working again, so if you say the magic words (or update the PR), bob will kick off a new build.
Note that because this is going back to fh-master, the fh-openshift-templates and fhcap PRs will be wrong: they'll have fh-master as the base branch rather than master. We can change that by updating this repo to start using master (should probably also update the chef cookbook, given that the branch is referenced there).

omg I didn't even say the magic words, it just started.

Pull Request Quality Guidelines
As we continue to focus on quality, here are a few things to keep in mind:

The code changes conform to the contributing & code style guides for this component (if they exist)
A component owner should review your change (we've tagged these above)
Automated testing has been added or updated for this change (e.g. UART, Unit/Acceptance tests)
If updating server component this PR should be deployed to a grid somewhere (via fhcap-cli) - please provide a link to this
Ensure JIRA is up to date before & after merge (e.g. deployment notes, tester notes, release notes, fix version)
Any SonarQube issues should be addressed where applicable (use your own judgement)

Please ping a component owner (see fh contrib) when your builds are complete, changes are deployed and you're ready for a review.
Fhcap PR will be generated automatically.
To deploy your changes to a cluster place comment in this PR with pattern [x][y] where x=deploy and y=clustername you wish to deploy.
You can also deploy your change manually using fhcap-cli

This PR should be closed and created against the master branch instead.

https://github.com/feedhenry/gitlab-shell/pull/11


Public Path option

Would it be possible to add the public path option from vue directly to this plugin? I do not think there is another way to set this. When using the vue.config.js it will disable all the other options set in workspace.json.

Absolutely! I'd ask if you're interested in working on this, but I'm actually already working on it. My work will make a number of vue.config.js options available in workspace.json. I think it'll be included in our next release, which will probably be this coming weekend.


Ice & Fire Mob Spawn Eggs Don't Work With Apotheosis Spawners / Nothing Spawns

Essentially, the mob shows up in the spawner but no matter what block I place beneath it or what light level I make it the mob just spins and spins.
Max Upgraded Spawner, with 5 Min to 10 Max Spawn Delay. On a skyblock, way under mob cap.
Minecraft: 1.16.5
Latest Version

You might need to use the Dragon Egg(?) to disable all spawn conditions. The mob just spinning usually means one of the spawn conditions isn't being met.

I literally could not provide that if I wanted to.
Anyway, its probably just the spawn conditions of the entity, as thats how the spawner works.


Add api to list usages of Azure SignalR resources

Add a new API for customers to list the usages of Azure SignalR resources in specific region.
Quality of Swagger
following the instructions on  https://github.com/Azure/adx-documentation-pr/wiki/Azure-Swagger-Tools and passed all the validations listed.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

This is a small enough change, I don't believe it need ARM review.

Can one of the admins verify this patch?

Ready for me to merge? What's the status of this PR from your side, @juniwang?

@marstr Yes, please help merge this PR.


Enhancement of Dark Mode

I will improve the dark mode button. In dark mode, the buttons '+' or '-' are not clear. If there any other issues in dark mode I will address them and fix it.
In the screenshot below, you can see that the dark mode button is not centered, and the buttons are not visible in dark mode.

Please assign me this issue, and I will fix it.

While adding and removing from the favorite list, the message is also not visible in dark mode.

I will identify and fix all the dark mode issues.

@Pinaka-Pani-18 The dark mode feature got rolled back because it needs to be applied consistently throughout the entire web app. It's a tough nut to crack – you can even see that the empty cart image doesn't look great in dark mode. The cart page, fonts, about page, and especially item cards all need to be styled in dark mode, which is why I pulled the plug on it for now. Feel free to pick any other issue or feature you'd like to tackle!

@Pinaka-Pani-18 will you able to develop a good dark mode ? if so i will re create a feature issue for it

sure creating the issue


Parameters not valid for older Redis in config

Config from version 1.2.3 doesn't start Redis service successfully anymore

Second this, had to revert to 1.2.2.
On ubuntu 14.04:
# redis-server --version
Redis server v=2.8.4 sha=00000000:0 malloc=jemalloc-3.4.1 bits=64 build=a44a05d76f06a5d9
# service redis-server start
Starting redis-server:
*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 33
>>> 'tcp-backlog 0'
Bad directive or wrong number of arguments
failed

Same issue here...
It appears that the template file to create the redis.conf has been upgraded to support features only in redis 3.x and doesn't cater for installs like Ubuntu 14.04/redis 2.8.4

@flyinbutrs Can you give a list of which parameters are specific to v2 vs v3 of redis? Is it just tcp-backlog?

#136 is part of the full solution for this (see my blog post about the final pattern: https://petersouter.co.uk/puppet-pattern-version-specific/

FWIW - I ran into this today as well while testing EPEL provided redis on CentOS 6 where tcp-backlog doesnt' work with redis 2.4.10 (which comes from EPEL).  However, newer versions of redis are avaiable via the REMI repo and that is most likely what my team will be using.

Ok, I figured it out... This is the commit that changed the parameter from backlog to tcp-backlog:
https://github.com/antirez/redis/commit/917b851491415466368430dd2b450ce431c88081
cloned the repo and described:
$ git describe 917b851491415466368430dd2b450ce431c88081
2.8.4-11-g917b851

So if redis version is >2.8.4, the parameter it tcp-backlog, if <=2.8.4, use backlog.

Yes, I'm working on a fix to detect the version in #145
In the mean time, you can either use the older version or fork and make a change to that template manually

any progress on this?

Turns out neither work with the version available in Ubuntu:
*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 258
>>> 'backlog 511'
Bad directive or wrong number of arguments

root@271ac462d565:/# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS
Release:	14.04
Codename:	trusty
root@271ac462d565:/# redis-server --version
Redis server v=2.8.4 sha=00000000:0 malloc=jemalloc-3.4.1 bits=64 build=a44a05d76f06a5d9

So I'm just going to put a "Must be newer than 2.8.5" around that logic

@nvtkaszpir I've got a working version for CentOS 6, is that the one you've been having issues with? Should have a PR soon

I switched to Centos 7.3 and bumped redis to 2.8.21 using openstack-kilo repo.
puppet manifest:
node default {

  include ::redis
  include ::firewall

  case $::osfamily {

    'Redhat': {

      include ::yum
      create_resources(yumrepo, hiera('yumrepo', {}))
      create_resources(yum::plugin, hiera('yum::plugin', {}))
      create_resources(yum::gpgkey, hiera('yum::gpgkey', {}))
      create_resources(yum::versionlock, hiera('yum::versionlock', {}))

      Yum::Gpgkey <||> -> Yumrepo <||>
      Yum::Versionlock <||> -> Package<| provider == 'yum' |>
      Yumrepo <||> -> Class['redis::install']
      Yum::Versionlock <||> -> Class['redis::install']
    }

    default: {
      fail ("Operating system ${::operatingsystem} is not supported yet.")
    }
  }

}

hiera:
---
# redis 2.8
# watch out for older redis versions, puppet module is not compatible with them

# centos 7.3

# redis 2.8 requires packages in repo openstack-kilo
yumrepo:
  'openstack-kilo':
    baseurl: 'http://mirror.centos.org/centos/$releasever/cloud/$basearch/openstack-kilo/'
    descr: 'openstack-kilo'
    enabled: 1
    gpgcheck: true

yum::gpgkey:
  '/etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud':
    ensure: 'present'
    content: |
      -----BEGIN PGP PUBLIC KEY BLOCK-----
      Version: GnuPG v2.0.22 (GNU/Linux)

      mQENBFVWcCcBCACfm3eQ0526/I0/p7HpR0NjK7K307XHhnbcbZv1sDUjQABDaqh0
      N4gnZcovf+3fj6pcdOmeOpGI0cKE7Fh68RbEIqyjB7l7+j1grjewR0oCFFZ38KGm
      j+DWQrj1IJW7JU5fH/G0Cu66ix+dJPcuTB3PJTqXN3ce+4TuG09D+epgwfbHlqaT
      pH2qHCu2uiGj/AaRSM/ZZzcInMaeleHSB+NChvaQ0W/m+kK5d/20d7sfkaTfI/pY
      SrodCfVTYxfKAd0TLW03kimHs5/Rdz+iZWecVKv6aFxzaywbrOjmOsy2q0kEWIwX
      MTZrq6cBRRuWyiXsI2zT2YHQ4UK44IxINiaJABEBAAG0WkNlbnRPUyBDbG91ZCBT
      SUcgKGh0dHA6Ly93aWtpLmNlbnRvcy5vcmcvU3BlY2lhbEludGVyZXN0R3JvdXAv
      Q2xvdWQpIDxzZWN1cml0eUBjZW50b3Mub3JnPokBOQQTAQIAIwUCVVZwJwIbAwcL
      CQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEPm5/ud2RCnmATUH/3HDtWxpFkmy
      FiA3VGkMt5dp3bgCRSd84X6Orfx1LARowpI4LomCGglGBGXVJePBacwcclorbLaz
      uWrW/wU0efz0aDB5c4NPg/yXfNvujvlda8ADJwZXVBQphzvaIKwl4PqBsEnxC10I
      93T/0iyphAhfMRJ5R8AbEHMj7uF+TWTX/JoyQagllMqWTwoP4DFRutPdOmmjwvSV
      kWItH7hq6z9+M4dhlqeoOvPbL5oCxX7TVmLck02Q5gI4syULOa7sqntzUQKFkhWp
      9U0+5KrBQBKezrurrrkq/WZR3WNE1KQfNQ77f7S2JcXJdOaKgJ7xe7Y2flPq98Aq
      wKXK7l1c3dc=
      =W6yF
      -----END PGP PUBLIC KEY BLOCK-----

# install specific redis version on centos
yum::versionlock:
  '0:redis-2.8.21-1.el7.x86_64':
    ensure: 'present'

# the rest of the redis configuration
redis::manage_repo: false # needed to use packages from openstack-kilo
redis::unixsocket: false # required to disable socket creation
redis::bind: '<IP_ADDRESS>'

redis::maxmemory: '1gb'
redis::syslog_enabled: true
redis::tcp_keepalive: 60
redis::timeout: 3600
redis::appendonly: true

# centos 7.x compatible
redis::config_owner: 'redis'
redis::config_group: 'root'

firewall:
  '100 allow redis access from local networks':
    source: '<IP_ADDRESS>/8'
    dport: 6379
    proto: 'tcp'
    action: 'accept'

I was also using Debian.Ubuntu but switched to Centos 7.3.
Also discovered the issue when running redis upgrade, they unfortunately broke configuration compatibility between patch versions.
Knowing that redis 3.x is a superset of redis 2.8 I'm rahter going to move to redis 3.2 in the future.


nixos/test-driver: Fix passing passthru attribute

Apparently this looks like it was forgotten when doing commit 3884ff70badca0c93c717e6190946a9a2846e948, which refactored the test runner and driver a bit.
The passthru argument actually was correctly reintroduced in setupDriverForTest, but the actual makeTest function didn't use it.
This fixes the nixpkgs tarball job, which previously failed with:
attribute 'elkPackages' missing, at /build/source/pkgs/tools/misc/logstash/6.x.nix:58:30

Fixes: https://github.com/NixOS/nixpkgs/issues/127274

Merged in bc0997489b0dba52d0c23bf7f9ea6ceb74c7f666.


Prevent buffer overflow

The major fix for this should be taken care of in https://github.com/hdmf-dev/hdmf/pull/780
Replaced #194

I guess the cycle of HDMF is too slow to wait for the stable version?

It's something to consider.. If this is merged here we will lock ourselves out of another NeuroConv release until it is, but it's also just a bug fix so maybe we could ask them to do a small release for that

I would like to have a release for neuroconv after the Murthy project. But that probably would be in December if Ben Cowley manages to get the sleap data by then. I have some small fix to add to the sleap interface here.

This and #238 are failing due to a new release of packaging yesterday (after our daily scheduled run no less...) introducing a breaking change to version parsing down at the neo level: https://github.com/pypa/packaging/issues/631
I'll try to get a fix here quickly

OK that fix is going to take a little bit, handed it off to SI team: https://github.com/SpikeInterface/probeinterface/issues/147
and trying to skip the tests here

Can we just specify an older version for packaging for now and fix it in a separate PR?


Tension with values less than zero

Please look at this example:

In 2.1.4 chart wasn't rendered under x-axis, but now in 2.1.5 with enabled tension I have that small area below. Of course there was no "history" of changes between 0 in e.g. monday and 0 in tuesday, but on my chart it looks like something happened with value.
Is it possible to disable this behaviour?

Hi!
I used this code:
options: {
    scales: {
        xAxes: [{
            ticks: {
                beginAtZero: true,
                min: 0,
                suggestedMax: 1
             }
         }]
     }
}

I hope that works for you

I'm guessing this was related to remove the forcing of the Bézier control points inside the canvas. This was needed because it adversely affects zoom and pan.

There is a fix here https://github.com/chartjs/Chart.js/issues/424 but the code has chaged dramatically, I don't know if the same method can be used... I have had a try myself with no luck.

I am guessing that this is a result of #2758

Any update on this?

I'm experiencing the same problem on 2.1.6


Problem writing arrays to ControlLogix PLC

Hi!
I am doing a project that requires reading and writing tags to Allen Bradley PLCs, so PyComm comes in very handy. I am having an issue writing arrays to the PLC however:
testarray = [12, 13, 14]
driver = clx()

if driver.open('<IP_ADDRESS>'):
   driver.write_array('Name.Space.Tag', 'INT', testarray)
   driver.read_array('Name.Space.Tag', 3)
   driver.close()

Running this, I get this rather cryptic error:
File "C:\Python27\lib\site-packages\pycomm\ab_comm\clx.py", line 453, in read_array
    addr_data=self._target_cid,
  File "C:\Python27\lib\site-packages\pycomm\cip\cip_base.py", line 591, in send_unit_data
    return self._check_reply()
  File "C:\Python27\lib\site-packages\pycomm\ab_comm\clx.py", line 337, in _check_reply
    raise DataError(e)
pycomm.cip.cip_base.DataError: unpack requires a string argument of length 2

I can do the write to the PLC, but the value in the PLC tag does not change. When I try to read it back, I get the error above.
I can read and write simple tags without any issues - but array operations seem to fail - can you point me in the direction of a fix or a workaraound for this?
Thank you!
Sincerely,
Lars Stoustrup

Lars,
Could you try to move the array out of the UDT and execute the read and write again? Maybe there is a problem when the array is inside the structure. I don't have a PLC handy to run the test at the moment

Thanks a lot! I figured it out it was a naming thing, more or less:
Apparently, when a tag is present in the PLC but not made remotely accessible, the error returned by the PLC is different from the one you get if the tag is not present at all. Making the tag remotely accessible resolved the issue.
Thanks for taking the time to respond - and PyComm works great :-)


STUKED WITHOUT RESPONSE

I'm having no response when I'm running the Ctrader (from ejtraderCT import Ctrader). i tried to put a wrong password and the same...
Any suggestion?

I'm having no response when I'm running the Ctrader (from ejtraderCT import Ctrader). i tried to put a wrong password and the same...
Any suggestion?

please share your code and log error

Same here. No Logs are provided with debug logging. Here is where it is stuck:
File "/opt/miniconda3/lib/python3.8/site-packages/ejtraderCT/api/ctrader.py", line 48, in init
self.fix = FIX(
File "/opt/miniconda3/lib/python3.8/site-packages/ejtraderCT/api/fix.py", line 212, in init
self.qs.connect((server, 5201))
KeyboardInterrupt

I'm using the example test:
from ejtraderCT import Ctrader
server="<IP_ADDRESS>" # - Host name: (Current IP address <IP_ADDRESS> can be changed without notice)
account="demo.icmarkets.MY_ACCOUNT" #  - SenderCompID: live.icmarkets.1104926
password="MY_Pswd" # - The password you configured
api = Ctrader(server,account,password)
print(api.isconnected())


Create "switch" for collateral

Instead of separate buttons there should be a switch.

Switch in Midas:

Switch exists, but it needs to send a transaction to enable collateral on an asset that's already supplied, without supplying more.


isc_dhcp vs. isc_dhcpd

What is the sc4s version ?
3.22.5
Which operating system (including its version) are you using for hosting SC4S?
does not matter
Which runtime (Docker, Podman, Docker Swarm, BYOE, MicroK8s) are you using for SC4S?
does not matter
Is there a pcap available? If so, would you prefer to attach it to this issue or send it to Splunk support?
does not matter
Is the issue related to the environment of the customer or Software related issue?
no
Is it related to Data loss, please explain ?
Protocol? Hardware specs?
no
Last chance index/Fallback index?
no
Is the issue related to local customization?
no
Do we have all the default indexes created?
does not matter
Describe the bug
Current state:

The documentation states a key of isc_dhcp while in fact you need to use isc_dhcpd with the current parser
It seems this has a history:

https://github.com/splunk/splunk-connect-for-syslog/issues/1769

https://github.com/splunk/splunk-connect-for-syslog/issues/2003

I assume something went wrong at a certain point of time.

Hey @ehlo550
Thanks for pointing it out, we will update the documentation.


A docker image for the standalone openwhisk

Description

This PR builds a docker image for standalone supports and adds a few properties to allow to pass the required parameters to run the standalone in a docker image
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)
Discussed in ML

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[x] Deployment
[ ] CLI
[ ] General tooling
[x] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[x] I updated the documentation where necessary.

Codecov Report

Merging #4782 into master will decrease coverage by 6.58%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #4782      +/-   ##
=========================================
- Coverage   84.89%   78.3%   -6.59%
=========================================
  Files         198     198
  Lines        8836    8836
  Branches      602     602
=========================================
- Hits         7501    6919     -582
- Misses       1335    1917     +582

Impacted Files
Coverage Δ

...core/database/cosmosdb/RxObservableImplicits.scala
0% <0%> (-100%)
:arrow_down:

...enwhisk/connector/kafka/KamonMetricsReporter.scala
0% <0%> (-100%)
:arrow_down:

...e/database/cosmosdb/cache/ChangeFeedConsumer.scala
0% <0%> (-100%)
:arrow_down:

...ore/database/cosmosdb/cache/CacheInvalidator.scala
0% <0%> (-100%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0% <0%> (-96.61%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0% <0%> (-93.85%)
:arrow_down:

...tabase/cosmosdb/cache/CacheInvalidatorConfig.scala
0% <0%> (-92.31%)
:arrow_down:

...e/database/cosmosdb/cache/KafkaEventProducer.scala
0% <0%> (-77.78%)
:arrow_down:

...whisk/core/database/cosmosdb/CosmosDBSupport.scala
0% <0%> (-74.08%)
:arrow_down:

...abase/cosmosdb/CosmosDBArtifactStoreProvider.scala
7.69% <0%> (-50%)
:arrow_down:

... and 8 more

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 8eb922f...8337973. Read the comment docs.

Note that some aspect like embedded Kafka support may not work as expected due to Docker networking. See #4628 and kafka listeners explanation for details. Which should be ok though as this mode (--kafka) would mostly be used by developers extending OpenWhisk and they would be better of using the java mode

It seems that in this mode upon starting openwhisk docker docker stop openwhisk the launched containers do not get removed. Have not dig further in the root cause

I think it is ready for merging. I added:

documentation
a start.sh script that also open the playground
the start script can be shortened to https://s.apache.org/openwhisk.sh (to do after merging)
tested the start.sh script in osx, linux, windows
a stop script that also cleans the other images created


Add a wiki: Pikmin Fanon

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://pikminfanon.fandom.com/wiki/
Link to destination (independent) wiki: https://pikminfanon.com/wiki/

This has been added in v3.10.1 (now available for Chrome, should be released for Firefox soon)


how can I import other html files, other layers or components into an html file?

Hello sir!
How to split html into layers or components, for example, connect header or footer from another html file? Which lines of code should be added to gulpfile.js and how to import other html files located in the created components folder into an html file? I need to connect a lot of individual html files. Task: Splitting one html file into several. Please write how this can be done, if it is not difficult for you to explain. Thank you in advance!

There is a gulp library https://github.com/zaharin/gulp-html-tag-include which can let you include other html into your main html, like adding common header and footer. You can find tutorial of how to do that https://dev.to/caiojhonny/html-includes-with-gulp-js-2def. Let me know if that solves your problem.


[FEATURE] Download multiple jobs at once as ZIP (mxliff)

Is your feature request related to a problem? Please describe.
My understanding is that the current "memsource file download" downloads jobs one by one.
However the standard way to download multiple files from Memsource is a bulk download in ZIP format at once.
The reason is that if the translation project has some folder structure, the only way to preserve it is with ZIP file on upload to Memsource and on download.
Also a typical download scenario for the output bilingual MXLIFF format is to download multiple jobs at once so that they can be open at once in one Editor screen.
Describe the solution you'd like
I'd like the parameter "job-id" to accept multiple values:
ex: memsource job file download --project-id SOMETHING --job-id ID,ID,ID,ID --type target
Additional context
Now getting this error on trying to pass multiple IDs:
{"errorCode":"Invalid parameters","errorDescription":"Job "1ItXs2W3pcRk1Q4CjB0SH7,o6bfVjyk2hXE39Y5zgXX33" not imported correctly or import is in progress"}

As of now I am not aware of API that would allow such thing. I am using https://cloud.memsource.com/web/docs/api#operation/completedFile that only takes only one job uid.

If there is no API we could workaround this by downloading one-by-one and compress locally.

@ludekjanda
Do you agree with this?
Reproducer:

Create a ZIP file:

 zip -r a.zip a/
  adding: a/ (stored 0%)
  adding: a/b.md (stored 0%)
  adding: a/c/ (stored 0%)
  adding: a/c/d.md (stored 0%)

Upload ZIP file to the memsource
memsource job create --project-id 3Bozqg0bJ0DJN4UZ8yh91p --filenames ~/a.zip --target-langs ja

Download job from memsource
memsource job download --project-id 3Bozqg0bJ0DJN4UZ8yh91p --job-id WiZ2gQfZreo9ahEqNrWHm

Actual results:
File is saved as 'a%2Fb-en-ja-C.md'
Expected results:

Create directory a
Create file b-en-ja-C.md in that directory

Agreed, @zerodayz this reproducer describes nicely the issue. Let's wait for Memsource if there is such API call now. I am afraid there must be some other way to get the original path from the downloaded document. In this project it's just a coincidence that it is in the filename because the File renaming options in this specific project include "path". See: "Rename completed files to: {path}/{fileName}_{targetLang}" there.

The download improved in https://github.com/unofficial-memsource/memsource-cli-client/commit/ce48bae272f390481fc878b26c810ba914f7197c


Prevent recursive thunks on heap

If it's gonna introduce too much complexity, we shouldn't add this feature probably.

The single Definition type works well in the current codebase.

It's very unlikely for thunk results to be stored into themselves.

Not doing for now due to the following reasons.

Definition needs to support normal functions and thunks because they cal be global.
Introducing a new let-thunk expression seems to be costly.


Win

Ping @msarahan I just updated PR #4 not sure if this will work.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Added to_transform() helper.

Added to_transform() helper function to work around the output parameter of tf2::fromMsg().
IMO, shows how much easier functions with return values are to use over functions with output parameters.
Will also allow me to refactor one of the manual for loops later.

Actually, isn't is specified here already?
http://docs.ros.org/en/melodic/api/tf2/html/namespacetf2.html#a66edbda6fa9127178de05ca185603b18

Actually, isn't is specified here already?
http://docs.ros.org/en/melodic/api/tf2/html/namespacetf2.html#a66edbda6fa9127178de05ca185603b18

I think that template doesn't have implementations for geometry_msgs::Pose because of the reason I listed

Aah, check!


⚠ Jenkins Plugins Artifactory has degraded performance

In 4c58126, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1266 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 3b2790f after 25 minutes.


Remove dead code in invoker (SetStage)

Just some cleanup, the StillAt method was used in a much earlier version of this code, but now it's just vestigial.

Going to go ahead and merge this since it's just some deletions and a rename.


Create Haystack Home overview pages

Move pages from haystack documentation website to haystack home.
TODO:

[ ] Make overview section haystack documentation more coherent since sections have been taken out

This looks good to me. In the 'intro' section in HH where we have that last list for 'Nodes' 'Pipelines' and 'Rest API' do you think it's worth giving a very brief/short description of them? And then point to docs for a detailed 'Levels of Haystack' explanation? WDYT?

Documentation moved to https://docs.haystack.deepset.ai


No JavaScript

The version 1.0 doesn't use JavaScript. This is mainly because of https://www.internet.org/ which delivers vutuv to it's users for free. This is actually a big deal because LinkedIn is not on that platform and internet.org delivers internet to many people who wouldn't have it otherwise. We do have quite a few vutuv users from internet.org
In version 2.x I'd like to integrate a non JavaScript version and a version which uses JavaScript to make a nicer GUI. But because we can not create both worlds in the 2.0 version we have to go with the non JavaScript version and implement the JavaScript version for 2.1.
We can use cookies. Just not JavaScript.
I remember that in version 1.0 this was easier said than done because the default Phoenix scaffolding uses JavaScript.
@riverrun and @hendri-tobing: Please share your thoughts.

The purpose of a non-JavaScript version is for the fast performance. The purpose of the JavaScript version is for a nicer GUI. Which one will give us more benefits/users? I agree in version 2.1, we can use JavaScript as optimum as possible to allow a nice GUI and also relatively still fast application.

The only javascript currently being used is from the Phoenix HTML application, and it is used with forms.
When removing this javascript, delete actions might not work properly, and there might be other issues related to form handling.

The problem with (and solution for) using the delete method in forms is outlined in this SO question.

The problem with (and solution for) using the delete method in forms is outlined in this SO question.
@wintermeyer do you know if this kind of workaround works with https://www.internet.org/?

I do not know. But <input name="_method" type="hidden" value="patch" /> seems to be really simple. This should AFAIK work. But please have a look into version 1 to see who it was solved in it.

@wintermeyer what is the best commit to look at for version 1? I looked at the commit before the initial work was started for v2. Is this the best one?

https://github.com/vutuv/vutuv/tree/v1.1

Fixed in #634