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
/
appview
/
state
/
at
f124604f62f438704888e3f8f2a5bdef2b843a2d
6 files
Akshay
clean up collaborators a bit
1y ago
904f19ea
git_http.go
clean up collaborators a bit
1 year ago
middleware.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
repo.go
clean up collaborators a bit
1 year ago
settings.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
signer.go
finish repo-settings page
1 year ago
state.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