Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-launcher
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-launcher
  • Issues
  • #22232
Closed
Open
Issue created May 11, 2017 by Taylor Yu@catalyst

gather info on how Tor Launcher uses bootstrap status messages

As part of the effort to improve the user experience during Tor Launcher bootstrap (legacy/trac#21951 (moved)), it would be helpful to know some details of how Tor Launcher currently uses bootstrap status messages (STATUS_CLIENT BOOTSTRAP asynchronous messages from the control protocol). Among other things, it could help Core Tor make short-term incremental changes to vastly improve the user experience.

  • Does the progress bar currently map phase numbers directly into percent-done on the bar?
  • Does it do anything with TAG= keywords in the BOOTSTRAP messages?
  • Does it do anything with SUMMARY= strings other than displaying them in the dialog box?
  • How does it know when to display the "copy logs" button with the warning icon?
  • Which other of the BOOTSTRAP keywords does it use and how?
  • Does it use any other asynchronous control protocol messages?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking