aboutsummaryrefslogtreecommitdiff
path: root/git_hooks_handle.go (unfollow)
Commit message (Collapse)AuthorFilesLines
9 days*: Typing fixesRunxi Yu1-1/+1
9 days*: Replace some := with varRunxi Yu1-34/+49
10 daysAdd SPDX license headers to all Go filesRunxi Yu1-0/+3
2025-02-20ssh/recv: Check hooksPath before receiving packsRunxi Yu1-20/+13
2025-02-20hooks, ssh: Indicate URL of newly-created MRsRunxi Yu1-3/+6
2025-02-20hooks: Clarify the last ACK/NAK being overallRunxi Yu1-4/+3
2025-02-20hooks: Use colorful SSH messagesRunxi Yu1-23/+32
2025-02-19hooks: Don't trim contrib/ when inserting MRsRunxi Yu1-2/+2
2025-02-19all: Use COALESCE to handle some nullable database fieldsRunxi Yu1-1/+6
2025-02-19ssh/recv, hooks: Create MRs on push, reject pushes to others' MRsRunxi Yu1-5/+32
2025-02-19hooks: Ignore error value of the last conn.Write()Runxi Yu1-1/+1
2025-02-19hooks: Use ssh stderr directly instead of going through hookRunxi Yu1-132/+99
2025-02-19hooks: Reject non-FF contrib pushes for nowRunxi Yu1-36/+68
We actually intend to create special refs for this in the future.
2025-02-19hooks: Add TODOs on where to create MRs and MR history pointsRunxi Yu1-0/+8
2025-02-19*.go: Use lowercase error valuesRunxi Yu1-2/+2
2025-02-18hooks: Check error on conn.WriteRunxi Yu1-12/+36
2025-02-18*.go: Add some comments for docsRunxi Yu1-0/+4
2025-02-18git_hooks_handle: Allow anonymous pushes to contrib/Runxi Yu1-2/+74
2025-02-18hooks: Fix the race condition that causes EPIPERunxi Yu1-0/+7
The hooks handler in the main daemon didn't wait for the hook client to write fully, and sometimes prematurely closes the connection, causing the hook client's splice to return EPIPE (or SIGPIPE if the signal handler wasn't installed). To remedy this, we call shutdown(sock, SHUT_WR) in the client, so that attempts to read on the server side return EOF. Then we can simply use io.Copy(&buf, conn) on the server side to fetch all of the data into a buffer.
2025-02-17hooks, etc.: Restructure concurrency and data flowRunxi Yu1-11/+16
Previously we accepted handler connections at hooks_handle and used a mess of channels and concurrent maps to let receive_pack handle the session. This doesn't work well because there are conditions where a push occurs but the hook is not called, e.g. when the destination branch is up to date. There is no reliable way of checking whether the subprocess is going to call the hook or not; it's technically possible to parse stderr but that interface is not guaranteed to be stable and IIRC has changed in the past). So receive_pack would be waiting on the channel to receive a hooks connection to handle but it'll never receive one, causing a deadlock. This entire thing was overengineered and was very prone to error. Here we let receive_pack put the cookie into the map, then start and wait for the subprocess to finish. When the hook actually runs and connects to its UNIX domain socket, the handler would check its cookie within the map. If the hook doesn't run, then nothing happens. The git-receive-pack subprocess blocks the execution of the SSH handler, and when git-receive-pack exists, the SSH handler (using a defer) deletes the cookie from the map. There may be caveats in signal handling or other cases that cause the cookie to be deleted from the map prematurely.
2025-02-17git_hooks_handle.go: Remove err_not_unixconnRunxi Yu1-1/+0
As this always suggests a programming mistake, we do not check the type assertion, causing it to panic if the types don't match.
2025-02-17hooks, etc.: Authenticate hooks, and handle them in the spawning threadRunxi Yu1-1/+23
2025-02-17git_hooks_handle.go: Read argv from hookRunxi Yu1-7/+33
2025-02-17git_hooks_handle.go: Refactor for clarityRunxi Yu1-14/+13
2025-02-17git_hooks_handle.go: Exit on UID mismatch, handle >1 connectionsRunxi Yu1-15/+21
2025-02-17git_hooks_handle.go, etc.: Listen for connections from hooksRunxi Yu1-1/+11
2025-02-17git_hooks_handle.go: Move from git_hooks.goRunxi Yu1-0/+0
2025-02-17git_hooks{.go,_client}: Add stub for git hook clientsRunxi Yu1-0/+45