Set Up Code Mapping fails when the file is at the top of the source repository

[bruno-garcia]

On this event, I clicked on:

I left a feedback in Sentry

Replay at that point in time

Note, I had just added mappings on the GitHub config manually

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[bruno-garcia]

Let me know if this isnt' Product: Issues 👁

[sentry-io]

Sentry Feedback: JAVASCRIPT-2YH9

[lobsterkatie]

@armenzg, do you know why this could be happening?

[armenzg]

I know why. If you look at the replay there's a link to the error.

We currently prevent creating code mappings when the file is at the top of the repository:

sentry/src/sentry/issues/auto_source_code_config/code_mapping.py

Line 99 in 5c29cde

or frame_file_path.find("/") == -1

This is because we started doing all work with Python packaged frames, thus, always expecting at least a directory. This was a mistake.

Fixing it would require making sure we have good test coverage to prevent regressions. I tried to play it safe when prototyping but ended up writing a lot of code with this assumption.

[armenzg]

I'm tracking it now as part of the project.