alpha
Login
or
Join now
tangled.org
/
core
Star
10
Fork
67
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Monorepo for Tangled
tangled.org
Star
10
Fork
67
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
16
Pulls
27
Pipelines
core
/
knotserver
/
at
cfbb567c9c0e5baf23773e4e4afc7bb1797fdca3
5 folders
10 files
kppcn.tngl.sh
knotserver/xrpc: defer plc submission until repo setup succeeds
2mo ago
b907bf93
config
knotserver/git: add comprehensive tag tests, improve parseTagRecord coverage Signed-off-by: Matías Insaurralde <matias@insaurral.de>
3 months ago
db
appview, knotserver: add didAssign event and PDS rewrite on login Signed-off-by: Lewis <lewis@tangled.org> Lewis: May this revision serve well! <lewis@tangled.org>
3 months ago
git
knotserver/git: add comprehensive tag tests, improve parseTagRecord coverage Signed-off-by: Matías Insaurralde <matias@insaurral.de>
3 months ago
repodid
knotserver: add repodid package, db migrations, and go-didplc dep Signed-off-by: Lewis <lewis@tangled.org> Lewis: May this revision serve well! <lewis@tangled.org>
3 months ago
xrpc
knotserver/xrpc: defer plc submission until repo setup succeeds Previously, CreateRepo submitted the PLC DID before the remaining local setup steps had completed. If RBAC setup or hook installation failed after that point, the handler cleaned up local state but still left behind a published DID with no corresponding repo on disk. Move PLC submission to the end of the create flow so the DID is only published after local repo setup succeeds. Also roll back repo RBAC state during cleanup, and treat hook setup failure as fatal instead of silently continuing.
2 months ago
events.go
appview/ingester: harden event processing and cursor This is more of a practical proposal than solving a direct problem. We fire-and-forget our cursor updates even if an event fails. Instead, we should have it in the same thread as the record ingestion and not be silent about errors. Also for verification I think a little retry-backoff would be in order. Lewis: May this revision serve well! <lewis@tangled.org>
2 months ago
git.go
appview, knotserver: add didAssign event and PDS rewrite on login Signed-off-by: Lewis <lewis@tangled.org> Lewis: May this revision serve well! <lewis@tangled.org>
3 months ago
http_util.go
knotserver: remove unused functions Signed-off-by: noClaps <git@zerolimits.dev>
9 months ago
ingester.go
appview/ingester: harden event processing and cursor This is more of a practical proposal than solving a direct problem. We fire-and-forget our cursor updates even if an event fails. Instead, we should have it in the same thread as the record ingestion and not be silent about errors. Also for verification I think a little retry-backoff would be in order. Lewis: May this revision serve well! <lewis@tangled.org>
2 months ago
internal.go
knotserver: support legacy owner/repo paths in PostReceiveHook Lewis: May this revision serve well! <lewis@tangled.org>
2 months ago
middleware.go
knotserver: add cors headers as a middleware function Signed-off-by: @nekomimi.pet <ana@nekoimimi.pet>
7 months ago
migrate.go
knotserver: add repo DID migration on startup Signed-off-by: Lewis <lewis@tangled.org>
3 months ago
router.go
knotserver: DID-based repo resolution in internal, ingester, git, and router Signed-off-by: Lewis <lewis@tangled.org>
3 months ago
server.go
knotserver: add repo DID migration on startup Signed-off-by: Lewis <lewis@tangled.org>
3 months ago
util.go
lexicons: remove sh.tangled.repo::owner Signed-off-by: oppiliappan <me@oppi.li>
9 months ago