Skip to content

Add an API for starting upcoming quark-kube-talker#214

Merged
haesbaert merged 1 commit into
mainfrom
start-kube-talker
Aug 12, 2025
Merged

Add an API for starting upcoming quark-kube-talker#214
haesbaert merged 1 commit into
mainfrom
start-kube-talker

Conversation

@haesbaert
Copy link
Copy Markdown
Collaborator

This is more preparatory work for kubernetes support.

We have to be flexible, this means being able to run on an environment without multithreading, in an environment with multithreading, and in some gc runtime like golang.

The object is to have "something" that feeds a file descriptor with kubernetes events, this "something" is the upcoming quark-kube-talker.

We tell quark that kubernetes is active by setting up a quark-kube-talker (or whatever), and feeing quark_queue_open with the pipe to read from. For now, management of the filedescriptor is done by the caller, so it must start quark-kube-talker, get the fd, and close on its own.

This is more preparatory work for kubernetes support.

We have to be flexible, this means being able to run on an environment without
multithreading, in an environment with multithreading, and in some gc runtime
like golang.

The object is to have "something" that feeds a file descriptor with kubernetes
events, this "something" is the upcoming quark-kube-talker.

We tell quark that kubernetes is active by setting up a quark-kube-talker (or
whatever), and feeing quark_queue_open with the pipe to read from. For now,
management of the filedescriptor is done by the caller, so it must start
quark-kube-talker, get the fd, and close on its own.
@haesbaert haesbaert requested a review from a team as a code owner August 8, 2025 12:37
@haesbaert haesbaert merged commit fa17615 into main Aug 12, 2025
2 checks passed
Comment thread quark.c
qwarnx("not closing child descriptors");
}

snprintf(pidbuf, sizeof(pidbuf), "%d", pipefd[1]);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why named pidbuf? it's filled with a file descriptor, right?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoooooooooooooops, it used to be a pid, and the pipe was on another buffer, I changed and renamed the wrong one, I'll fix it, I also realized, that I had my tabs disabled in emacs and the whole function is not using tabs. :D

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#215
LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants