While trying to add reviewers to a new pull request today, the browser makes a call to recommendation API for a list of eligible users, but isn't able to receive a valid response from the server. All other actions to create a the pull request work fine.
After creating the pull request without reviewers, the action of trying to add reviewers via the right reviewers sections makes the same call, and fails identically as previously.
EDIT: This issue seems to affect all interface elements that search for users via a text-list, like search-by-author in pull requests etc.
Please note that this was working fine as of Friday, July the 5th, 2024.
The call is as below(with cookies stripped, and identifying data obfuscated):
curl 'https://bitbucket.org/gateway/api/v1/recommendations'
--compressed
-X POST
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:125.0) Gecko/20100101 Firefox/125.0'
-H 'Accept: */*'
-H 'Accept-Language: en-US,en;q=0.5'
-H 'Accept-Encoding: gzip, deflate, br'
-H 'Referer: https://bitbucket.org/abc/xyz/pull-requests/1'
-H 'content-type: application/json'
-H 'Origin: https://bitbucket.org'
-H 'Connection: keep-alive'
-H 'Sec-Fetch-Mode: cors'
-H 'Sec-Fetch-Site: same-origin'
-H 'Pragma: no-cache'
-H 'Cache-Control: no-cache'
-H 'TE: trailers'
--data-raw '{"context":{"containerId":"1034a47f-d5cc-4ce8-86d4-c621732bfd0a","contextType":"BitbucketPullRequestReviewers","principalId":"Context","productKey":"bitbucket","siteId":"bitbucket","sessionId":"536a2571-3bf7-4950-992a-badbadb001ee","productAttributes":{"emailDomain":"Context","isPublicRepo":false,"workspaceIds":["8badf00d-b035-4f7b-be07-aaaa1111eeee"],"pullRequestId":12}},"includeUsers":true,"includeGroups":false,"includeTeams":false,"includeNonLicensedUsers":false,"maxNumberOfResults":20,"performSearchQueryOnly":false,"searchQuery":{"cpusQueryHighlights":{"query":"","field":""},"customQuery":"","customerDirectoryId":"","filter":"account_status:\"active\" AND (NOT email_domain:\"connect.atlassian.com\") AND (NOT account_type:app)","minimumAccessLevel":"APPLICATION","queryString":"","restrictTo":{"userIds":[],"groupIds":[]},"searchUserbase":false}}'
The response headers are as below:
HTTP/2 400
date: Mon, 08 Jul 2024 05:25:41 GMT
content-type: application/json
server: AtlassianEdge
x-trace-id: f887978ab19749babde581b5c039fca7
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-frame-options: SameOrigin
content-encoding: gzip
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
atl-traceid: f887978ab19749babde581b5c039fca7
report-to: {"endpoints": [{"url": "https://dz8aopenkvv6s.cloudfront.net"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600} nel: {"failure_fraction": 0.001, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"}
X-Firefox-Spdy: h2
The reponse is as below:
{
"message":"The request to xpsearch-user-searcher failed with an Http 400 BAD_REQUEST error.",
"status":"BAD_REQUEST",
"statusCode":400
}
Has anyone faced a similar issue with the BB cloud web interface on api calls failing?
Hey @Samveen Gulati _via Sygitech_ ,
thank you for reaching out to Community!
By the time you posted this question, a limited number of users were facing issues navigating the Bitbucket Cloud interface. Our engineering team promptly investigated the issue, and the page's navigation should be working as usual again.
In this case, could you please confirm if you are still facing this issue? If yes, is it also reproducible if you try using your browser's Incognito mode?
Thank you, @Samveen Gulati _via Sygitech_ !
Patrik S
Hi @Patrik S
Much after posting this, I realized that the community isn't a place for bug reports, and instead opened a support ticket for this issue. I'm happy to say that the ticket has been worked on, and the issue is now resolved.
Thanks you for your time and effort.
Samveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.