inkandswitch / inkandswitch/backstitch-sync-server

IP not logged for connected actions

Open
#5 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
16
Forks
3
PR merge metrics
No merged PRs in 30d

Description

While there's rudimentary IP logging, there's no way to differentiate the actions of multiple simultaneously connected clients in the logs. We should figure out a way to log the IP along with the remote repo ID (or something similar) so that we can reconstruct a history for debugging.

Contributor guide

Open the contributing guide

Research direction

Start by locating the existing rudimentary IP logging and the code handling simultaneously connected clients in the sync server. Determine how a remote repo ID or similar identifier can be logged with each IP, then verify that the resulting logs can reconstruct actions for debugging.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.