Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Collector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • Metrics
  • Collector
  • Issues
  • #28003
Closed
Open
Created Oct 11, 2018 by Karsten Loesing@karsten

Consider refactoring various code that makes descriptors persistent

From legacy/trac#27390 (moved):

"How much does the new function in PersistenceUtils differ from the similar functions:

onionperf/OnionPerfDownloader.java:  public void cleanUpRsyncDirectory() throws ConfigurationException {
exitlists/ExitListDownloader.java:  public void cleanUpRsyncDirectory() {
bridgedescs/SanitizedBridgesWriter.java:  public void cleanUpRsyncDirectory() throws ConfigurationException {
relaydescs/ArchiveWriter.java:  public void cleanUpRsyncDirectory() {

Currently webstats does seem to be the only module that uses the shared function. The relaydescs module may need something more complex to handle persisting microdescriptors for longer, but the other modules could maybe just switch? This could be a new ticket."

Needs discussion first.

Assignee
Assign to
Time tracking