alpha
Login
or
Join now
dunkirk.sh
/
core
forked from
tangled.org/core
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
This repository has no description
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
core
/
knotserver
/
at
master
3 folders
9 files
Anirudh Oppiliappan
knotserver: add missing perms to forked repo
1y ago
834db587
config
knotserver: make jetstream endpoint configurable
1 year ago
db
add in-memory jetstream did filter
1 year ago
git
knotserver: use common ancestor to calculate diffs the existing diff calculation approach directly compares branches, this forces linear history for merge. this patch updates the diff logic to use the common ancestor commit to calculate diffs. ``` P Q o---o topic / / o---o---o---o master A X Y ``` when diffing topic and master directly with difftree (Q and Y), the commits introduced in master since the creation of the branch, namely, X and Y, are considered "removed" from the generated patch. however, when diffing with the common ancestor A, only changes introduced by P and Q are included in the produced patch. this calculation can be retired in favor of format-patch soon enough (i think).
1 year ago
file.go
knotserver: add missing perms to forked repo Thanks @dvjn.dev!
1 year ago
git.go
knotserver: git: fix upload-pack handling Fix stdin piping to git-upload-pack. I think we were closing the pipe too soon previously, resulting in the 'fatal: remote end hung up unexpectedly' error. Probably went unnoticed for smaller repos. Also fix a bunch of misc. bugs in with superfluous http header writes and the gzip reader being shadowed.
1 year ago
handler.go
knotserver: git: track a hidden ref
1 year ago
http_util.go
knotserver: implement /merge and /merge/check endpoints /:did/:repo/merge is only ever used when actually performing the merge, so by this point all conflicts should've been rectified and the merge *should* succeed. This is the appview's responsibility. /:did/:repo/merge/check checks for mergeability, and can be used to repeatedly check as the supplied patch is updated by the submitter.
1 year ago
internal.go
all: rename module to tangled.sh/tangled.sh/core
1 year ago
jetstream.go
add in-memory jetstream did filter
1 year ago
middleware.go
defer last event time in appview ingester
1 year ago
routes.go
knotserver: add missing perms to forked repo Thanks @dvjn.dev!
1 year ago
util.go
all: use securejoin
1 year ago