aboutsummaryrefslogtreecommitdiffstatshomepage
Commit message (Collapse)AuthorAge
* signal: remove the stupid add_to_event_loop wrapperEgor Tensin2023-06-13
|
* server: handle disconnected workers gracefullyEgor Tensin2023-06-13
|
* event_loop: support more event typesEgor Tensin2023-06-13
|
* event_loop: add event_loop_add_onceEgor Tensin2023-06-13
|
* README: updateEgor Tensin2023-06-13
|
* signal: sigprocmask -> pthread_sigmaskEgor Tensin2023-06-13
|
* signal: refactoringEgor Tensin2023-06-13
|
* sanitize #include-sEgor Tensin2023-06-13
|
* signal: remove unused APIsEgor Tensin2023-06-13
|
* event_loop: hide the API detailsEgor Tensin2023-06-13
|
* use signalfd to stop on SIGTERMEgor Tensin2023-06-13
| | | | | | | | | | | | | | | | | | Is this an overkill? I don't know. The thing is, correctly intercepting SIGTERM (also SIGINT, etc.) is incredibly tricky. For example, before this commit, my I/O loops in server.c and worker.c were inherently racy. This was immediately obvious if you tried to run the tests. The tests (especially the Valgrind flavour) would run a worker, wait until it prints a "Waiting for a new command" line, and try to kill it using SIGTERM. The problem is, the global_stop_flag check could have already been executed by the worker, and it would hang forever in recv(). The solution seems to be to use signalfd and select()/poll(). I've never used either before, but it seems to work well enough - at least the very same tests pass and don't hang now.
* log: refactoringEgor Tensin2023-06-12
|
* log: thread-safe loggingEgor Tensin2023-06-12
|
* log: prefix with thread IDEgor Tensin2023-06-12
|
* command: fix a race conditionEgor Tensin2023-06-12
| | | | | Modifying cmd_dispatcher fields like that make it inherently unsafe to call cmd_dispatcher_handle_conn concurrently.
* sqlite: fix generate-sql-header.pyEgor Tensin2023-06-12
|
* msg: rework some APIsEgor Tensin2023-06-11
|
* worker_queue: fix worker_queue_add_lastEgor Tensin2023-06-09
|
* STAILQ -> SIMPLEQEgor Tensin2023-06-09
|
* msg: add msg_send_from_argv shortcutEgor Tensin2023-06-09
|
* add {file,net}_close as a wrapper to close(2)Egor Tensin2023-06-09
|
* docker: bump base imageEgor Tensin2023-05-29
|
* fix realloc usageEgor Tensin2023-05-29
| | | | | | | | Remember, this is always a mistake: ptr = realloc(ptr, size); You still need to free() the original ptr if realloc fails.
* file: rework file_readEgor Tensin2023-05-17
| | | | | It now increases the buffer size exponentially until it finishes reading the file.
* signal: refactoringEgor Tensin2023-05-15
|
* net: drop the _all suffixEgor Tensin2023-05-15
|
* msg: strings, not wordsEgor Tensin2023-05-15
|
* minor refactoringEgor Tensin2023-05-15
|
* test/lib: refactoringEgor Tensin2023-05-15
|
* signal: refactoring, add comments in tcp_server, etc.Egor Tensin2023-05-15
|
* docker: fix failing valgrind runsEgor Tensin2023-05-15
| | | | | | | | | | | Unless ulimit -n is set, I get errors such as this from valgrind: Assertion 'newfd >= VG_(fd_hard_limit)' failed. I don't know and don't care what this is about; settings ulimit -n to something else seems to do the trick. For reference, this can be used: https://www.mail-archive.com/kde-bugs-dist@kde.org/msg778326.html
* valgrind: track open file descriptorsEgor Tensin2023-05-15
|
* EINVAL means EINTR also?Egor Tensin2023-05-15
|
* worker_queue: forgot to close file descriptors in worker_destroyEgor Tensin2023-05-15
|
* cmake: disable -Werror for debug buildsEgor Tensin2023-05-15
|
* rework server-worker communicationEgor Tensin2023-05-15
| | | | | | | | | | | | | | | | | | OK, this is a major rework. * tcp_server: connection threads are not detached anymore, the caller has to clean them up. This was done so that the server can clean up the threads cleanly. * run_queue: simple refactoring, run_queue_entry is called just run now. * server: worker threads are now killed when a run is assigned to a worker. * worker: the connection to server is no longer persistent. A worker sends "new-worker", waits for a task, closes the connection, and when it's done, sends the "complete" message and waits for a new task. This is supposed to improve resilience, since the worker-server connections don't have to be maintained while the worker is doing a CI run.
* command: adjust order of parameters to handlersEgor Tensin2023-05-14
|
* process: add process_output_dumpEgor Tensin2023-05-14
|
* msg: add functions for one-off communicationEgor Tensin2023-05-14
|
* msg: enforce at least one wordEgor Tensin2023-05-14
| | | | Also, move some stuff to net.c where it belongs.
* fix unnecessary #include-sEgor Tensin2023-05-13
|
* rename Makefile parameters & update READMEEgor Tensin2023-05-13
|
* ctest: don't use the -C parameterEgor Tensin2023-05-13
| | | | | We only build using "Unix Makefiles" anyway, which is a single-configuration build system.
* ci_queue -> run_queueEgor Tensin2023-05-13
| | | | Also, some minor refactoring.
* cmake: document _GNU_SOURCE usageEgor Tensin2023-05-13
|
* use -std=c17 -WpedanticEgor Tensin2023-05-13
|
* command: refactoringEgor Tensin2023-05-13
|
* best practices & coding style fixesEgor Tensin2023-05-13
| | | | | | | | * I don't really need to declare all variables at the top of the function anymore. * Default-initialize variables more. * Don't set the output parameter until the object is completely constructed.
* add command module to handle request-response communicationsEgor Tensin2023-05-13
|
* ci_queue: fix a broken getterEgor Tensin2023-05-13
| | | | | | Everything was broken starting from the "making struct ci_queue_entry opaque" commit. Damn, I really wish I'd have some kind of automated testing to catch errors like this...
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-20 04:42:44 +0000