plugin does not parse correctly bitbucket repositories with a dot in the name and returns 404 errors when trying to connect through API

[Joost Van Den Cruyce]

when trying to access the tabs for “pull requests” and “pipelines” following error pops up:

“Something went wrong

You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated.”

when debugging it seems every communication fails with 404, further investigation shows the plugin queries “my” repo if the actual repo name is “my.own.repo”, e.g. it drops everything after the first dot. The plugin interacts without problem with repositories which do not contain dots in their names.

I’m using the latest available plugin and VSCode

OS: macOS Ventura

[Andrew Quartey]

I can confirm that this is bonafide problem with the extension’s version 3.0.0. Downgrading to version 2.20.12 temporarily resolves the issue.

[Michael Kantz]

Experiencing the same issue. Thanks for reporting this.

[Jeffry De La Rosa]

The same issue

[Michael Bergquist Suarez]

Getting this aswell.

I've got a repo, lets call it "hello-1.0". I get a bunch of errors, 404:s being one of them. When I look in the extension output I get errors such as:

[2023-08-30 11:41:33:434] Error getting URL: https://api.bitbucket.org/2.0/repositories/my-organization/hello-1/branching-model  Error: Request failed with status code 404
[2023-08-30 11:41:33:434]  Error: error updating start work page: [object Object]
[2023-08-30 11:41:33:442] Error getting URL: https://api.bitbucket.org/2.0/repositories/my-organization/hello-1  Error: Request failed with status code 404

As you can see, the extension seem to strip away the dot and everything after: hello-1.0 becomes hello-1 .