Closed Bug 1127924 Opened 10 years ago Closed 10 years ago

processor needs to pass --symbols-cache and --symbols-url to stackwalker

Categories

(Socorro :: Backend, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: lars)

References

Details

stackwalker is now able to download and store symbols from HTTP, processor needs to be able to pass these along.
Summary: processor needs to path --symbols-cache and --symbols-url to stackwalker → processor needs to pass --symbols-cache and --symbols-url to stackwalker
Blocks: 1097216
is "--symbol-cache" a boolean or is there a value of some type associated with it?
and is there a docstring that i ought to associate with "--symbol_cache". how does "--symbol_cache" differ from "--symbol_cache_path" that already exists?
(In reply to K Lars Lohn [:lars] [:klohn] from comment #1) > is "--symbol-cache" a boolean or is there a value of some type associated > with it? (In reply to K Lars Lohn [:lars] [:klohn] from comment #2) > and is there a docstring that i ought to associate with "--symbol_cache". > > how does "--symbol_cache" differ from "--symbol_cache_path" that already > exists? From "stackwalker --help": --symbols-url A base URL from which URLs to symbol files can be constructed --symbols-cache A directory in which downloaded symbols can be stored
Assignee: nobody → lars
Status: NEW → ASSIGNED
Commit pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/189d4dcf3a3b3c9b02005f4e3feff78dfd0d4d90 fix bug 981079 and 1127924 - support stackwalker HTTP symbol fetch and caching
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
A detail I neglected to mention before is that stackwalker can accept multiple --symbols-url options, which we need to use since we have separate public/private buckets. I went ahead and implemented this in the feature that landed, with explicit --private_symbol_url and --public_symbol_url options (it's fine to leave one unspecified)
You need to log in before you can comment on or make changes to this bug.