You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Bitbucket throwing error "Activating Bitbucket features failed" even when disabled. Our Bitbucket instance is no longer running, we have migrated to GitHub. Every time I open my VS Code instance, I get the error above. I have verified the Bitbucket feature is toggled OFF in the Atlassian Settings for the Atlassian Plugin, see screenshot below.
To Reproduce
Steps to reproduce the behavior:
Not sure you can, but you need to point to a deactivated Bitbucket instance
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Environment and Version (please complete the following information):
I knew reproducing might be an issue :(. There is nothing set there but even if there was, if the feature is toggled off, it should not be trying to do anything with any settings within that feature, right? I have never connected it to Bitbucket Cloud, we only ever had on-prem which is decomm'd.
Describe the bug
Bitbucket throwing error "Activating Bitbucket features failed" even when disabled. Our Bitbucket instance is no longer running, we have migrated to GitHub. Every time I open my VS Code instance, I get the error above. I have verified the Bitbucket feature is toggled OFF in the Atlassian Settings for the Atlassian Plugin, see screenshot below.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Environment and Version (please complete the following information):
Version: 1.96.4 (system setup)
Commit: cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
Date: 2025-01-16T00:16:19.038Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: