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
c3a68445577eeb38faa66c874b35760419176f17
3 folders
9 files
Akshay
knotserver: last commit for each file
1y ago
c3a68445
config
knotserver: last commit for each file This is a super trivial implementation last commit for each file. It's slow and inefficient despite using ristretto for in-memory caching. We should move this to storing in sqlite in the future.
1 year ago
db
jetstream: fix reconnect logic and last time_us saving Reconnection is now handed by cancelling the connCtx context. This is a lot cleaner and the jetstream client package honors context cancellation. Saving of last time_us is also simplified now. We only save (update, rather) after the last seen event by incrementing the event's time_us by 1 (this is ok since it's a monotonic clock). We pick up from here upon reconnect and don't save last time_us for any other reason. Lastly, outside of first boot, we should only ever use UpdateLastTimeUs.
1 year ago
git
knotserver: last commit for each file This is a super trivial implementation last commit for each file. It's slow and inefficient despite using ristretto for in-memory caching. We should move this to storing in sqlite in the future.
1 year ago
file.go
appview: repo file content
1 year ago
git.go
all: use securejoin
1 year ago
handler.go
appview: implement a basic breadcrumb for files This needs another pass to fix the intermediate directory links etc.
1 year ago
http_util.go
knotserver: fix a bunch of things
1 year ago
internal.go
knotserver/internal: internal keys endpoint This is for keyfetch use.
1 year ago
jetstream.go
jetstream: fix reconnect logic and last time_us saving Reconnection is now handed by cancelling the connCtx context. This is a lot cleaner and the jetstream client package honors context cancellation. Saving of last time_us is also simplified now. We only save (update, rather) after the last seen event by incrementing the event's time_us by 1 (this is ok since it's a monotonic clock). We pick up from here upon reconnect and don't save last time_us for any other reason. Lastly, outside of first boot, we should only ever use UpdateLastTimeUs.
1 year ago
middleware.go
knotserver: setup known_dids and dev mode
1 year ago
routes.go
all: misc fixes
1 year ago
util.go
all: use securejoin
1 year ago