Commits
- Commit:
4429bcbe67c0f234de6abf709931d349bc46da36
- From:
- Thomas Adam <thomas@xteddy.org>
- Date:
portable: release 0.114
- Commit:
1873f8e9ab8f236494e7b497e3ff8bc5b8675adc
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
bump versio number
- Commit:
2ff12d2abc4cd7dfed5f0068579953e5907b4eb4
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
CHANGES for 0.114
- Commit:
f762ea1631dfa737f21c7d9a8036c95fddeae692
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
plug a file descriptor leak in the gotsysd libexec process
- Commit:
01b6b6f8d2c07fa268809963409885e9d224b346
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
avoid event_loopexit() in gotsysd libexec event handlers when flushing
It seems flushing our final message can fail if we forcefully exit
the event loop here. This would leave gotsysd's sysconf process stuck
in a state where it was waiting for a message which never arrived.
- Commit:
05a4f4a0af5e31da8e41dd543270f06d69049fec
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
use imsgbuf_flush() instead of gotsysd_imsg_flush() in libexec event handlers
The gotsysd_imsg_flush() wrapper enforces a sync write by polling the
file descriptor and writing data in a loop. Since libevent already does
polling for us we can simply use imsgbuf_flush() here instead.
- Commit:
50a30d2587f76dbcf46418eac2d2cd13142a824e
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
avoid flushing messages in got_imsg_ helper functions, just buffer them
- Commit:
326548fb2e3468c814229a7354f2cdc48b5a4676
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
make sure gotsysd libexec helpers flush all pending messages before exiting
- Commit:
4f6bf13c6b1b46b405a7f093a1bc52bf247afb9d
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
always consume authorized keys messages in gotsys-userkeys
THe main process will always send these messages so don't skip
parsing them even if we are going to ignore the current user.
- Commit:
8a03603b8f1458ba1e8c2f2ed9bd0363e8601603
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
add gotsys apply -w option which waits until sysconf has been run
- Commit:
40d558910d47a11daa7416ea386f16b67c9258b8
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
stop running ssh with -q by default
The -q option suppresses too many important errors, including the
warning printed when a host key has changed. Requiring users to
pass -v in order to see this message is too cumbersome.
- Commit:
89dafad3e9c76df8c7e59b991262efea9763be5b
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
build and install gotwebd in gotsysd regress VMs
- Commit:
13cfc96365853c01cc8457b33890eb86e2c2e019
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
remove an obvious comment; expected output already shows "+0000" i.e. UTC
- Commit:
dd1da84ce9969ee259bfe16d87d3f3359778409b
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
untangle committer and author_time parameters of got_worktree_commit()
Make the semantics of the author_time parameter self-contained by
treating author_time == 0 as the fallback case, instead of treating
committer == NULL as the fallback case. Having the semantics of one
parameter depend on the semantics of another might lead to subtle
bugs introduced during potential future refactoring of this code.
- Commit:
8acf3aa649625d9afcec49b78392fcfb76063bf8
- From:
- "Sven M. Hallberg" <pesco@khjk.org>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
cvg: add author_time argument to got_worktree_cvg_commit()
No functional change, but keeps the code in sync with got.
Patch by Sven M. Hallberg
- Commit:
e16f7949b860f4a94e2f18128f786ffafc64b0ee
- From:
- "Sven M. Hallberg" <pesco@khjk.org>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
got rebase: preserve author timestamps
Adds test_rebase_preserves_author_data to regress/cmdline/rebase.sh.
Patch by Sven M. Hallberg
- Commit:
4071bc439fdfba4df88f0a555367f987d4085491
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
relax repository path permission checks in gotsys-repo-create
Since gotwebd can now be given read access to gotd repositories
by making the directory readable for the _gotwebd group, these
checks are too strict. Stop requiring a specific GID, and allow
group rx bits to be set for group read access.
As before, keep rejecting world/other rwx bits for safety.
Read access to repositories is supposed to be managed by gotd.
- Commit:
ddb085b36df4a5358dbeb2299c813826f34d39be
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
fix gotsys-read-conf crash when ssh key comments are missing in gotsys.conf
Add test coverage for this issue.
- Commit:
9f4ec8bd2a1a84fd3e84353dcf6c047191966022
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
bump version number
- Commit:
d029e8951a426dc5aa9d4ee828eb431ac324e8c4
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
CHANGES for 0.113
- Commit:
41e722a1981bbd7e55fed6bdf1a258d2d53939ba
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
fix a race in gotd notification processing
Dequeue notifications from the list only once the notify process has
confirmed that the notification has been sent. This should be more
robust for the following reason:
In some spots were are checking the list head against NULL to see if
any notifications are still pending. By removing notifications from
this list too early, this check did not cover notifications which were
still in flight. We could thus end up deciding to shut down the session
process too early, and the last notification of several would fail.
Issue observed when sending a new commit on a branch and a new tag
which tags this commit to gotd in a single 'got send' operation.
Only the tag notification would make it, while the other notification
never arrived after an 'unexpected EOF' error in the notify process
while trying to send a confirmation to the session process.
ok op@
- Commit:
689eb4525dcbcd6868eee875279ca6173dc3e891
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
fix bogus "unexpected privsep message" from gotsh during "got send"
Ensure that gotsh receives its end of the pack file data pipe
before repo_write starts sending pack file status messages.
Messages of type GOTD_IMSG_PACKFILE_StATUS would end up being
received in gotsh's serve_write() function too early.
This race is similar to the one fixed for repo_read back in commit
c2274a511a7415078e2628f969b8459f69432411
Reported by martijn@, who pin-pointed the problematic case in the code, thanks!
- Commit:
8f10fdc5b06ffb0e756ba470ccbbe7f112829535
- From:
- Stefan Sperling <stsp@stsp.name>
- Via:
- Thomas Adam <thomas@xteddy.org>
- Date:
fix default access for root and _gotd when gotsysd runs without config file
- Commit:
818df7b50765ef5fa60fc39d18a90e70937c5248
- From:
- Thomas Adam <thomas@xteddy.org>
- Date:
portable: set next version
- Commit:
2d26ff5622d14a24c43d1ac83931a7168de7bc0a
- From:
- Thomas Adam <thomas@xteddy.org>
- Date:
portable: release 0.113