getsentry / getsentry/sentry

Perforce depots not appearing in Code Mapping dropdown despite successful p4 depots query

Open
#116,148 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Product Area: Settings - Integrations Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Environment

SaaS (https://sentry.io/)

Steps to Reproduce
  1. Install the Perforce integration with valid credentials.
  2. Confirm the connection is working (server logs show successful user-login and user-depots commands from Sentry).
  3. Confirm the configured service account has depot access by running p4 depots as that user.
  4. Navigate to Settings > Integrations > Perforce > Configurations > Code Mappings > Add Mapping.
  5. Observe that the depot dropdown is empty.

Additional Context

Removing and reinstalling the integration multiple times did not resolve the issue.
Server logs confirm user-login and user-depots commands are reaching the Perforce server successfully.
Running p4 depots manually as the service account returns the expected depots.

*user-reported bug. Intercom ticket #102195765

Expected Result

Depots accessible to the configured service account should appear in the dropdown.

Actual Result

The dropdown is empty, despite the server logs confirming that Sentry is successfully querying p4 depots and the service account having access to the depots.

Product Area

Unknown

Link

No response

DSN

No response

Version

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Perforce integration's user-depots result into the Settings > Integrations > Perforce > Configurations > Code Mappings > Add Mapping flow; the report names no files or tests. Reproduce with a valid service account and compare the returned depots with the dropdown options. Done means accessible depots appear in the dropdown.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.