getsentry / getsentry/sentry

In native raw stack trace image list, render code id instead of debug id?

Open
#88,115 1 comment 0 reactions 0 assignees View on GitHub
Feature Native
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

When downloading a raw stack trace with image list (currently only possible when looking at unsymbolicated stack trace, covered in https://github.com/getsentry/team-ingest/issues/686), the ID rendered for the debug files is the debug id: https://github.com/getsentry/sentry/blob/5cbbe2e849e594554d23e2c4884a37092b1e35e1/src/sentry/lang/native/applecrashreport.py#L265

A [customer wrote in](https://www.notion.so/sentry/1c38b10e4b5d80ce9952ce3baf4bdd55) because they expected the code id instead.

Not sure if this is by design, this was the last change to the code: [PR](https://github.com/getsentry/sentry/pull/15835)

Contributor guide

Open the contributing guide

Research direction

Start at src/sentry/lang/native/applecrashreport.py:265, where the debug-file ID is rendered for native raw stack trace image lists. Read PR 15835 and the linked team-ingest issue to understand the intended identifier and current unsymbolicated-stack-trace flow. Done means the rendered identifier matches the agreed behavior, with relevant coverage updated if existing tests cover this path.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.