- edited description
Can't view the pull request details in the pull request tab window
The issue still exists, for some PR it is not possible to see details.
When I click on ‘Details’ in the pull requests tree view, the pull request page is opening and loading but then it is getting black.
Using developer tools in VS I found the messages:
[Embedded Page] RangeError: Invalid time value webviewElement.ts:99
[Embedded Page] Uncaught RangeError: Invalid time value webviewElement.ts:99
Extension Version 2.9.1
VSCode:
Version: 1.57.1 (user setup)
Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
Date: 2021-06-17T13:28:07.755Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.19042
No issues with v2.8.6.
Comments (21)
-
reporter -
reporter - edited description
-
Also experiencing the same behaviour. On selection of the PR details they are displayed for a brief moment before disappearing.
Same version of VS Code installed
-
Unable to create branch, failing on errors:
Error while fetching latest pull requests TypeError: Cannot read property 'curlCommand' of undefined
Error: Error authenticating with Bitbucket: TypeError: Cannot read property 'replace' of undefined
-
-
reporter - edited description
-
Reset authentication helped in my case.
I think that in case of “Credentials are already marked as invalid.” and “Blocking request due to previous 40[1|3]” , the VScode don’t show error of invalid connection and just failing with type errors
-
I am having the same issue. After clicking the “details” element in a PR, the PR overview begins to render for a half-second, then the whole tab goes blank. With quick timing I was able to get a screenshot to see what was rendering before the page goes blank:
The developer tools console shows there may have been an issue with the time:
I am able to successfully view the details element of only one PR: the very most recent one in my project. Perhaps that has something to do with the time error.
-
macos have the same issue
-
getting same issue in macos - vscode latest version
[Embedded Page] RangeError: Invalid time value
webviewElement.ts:100 [Embedded Page] Uncaught RangeError: Invalid time value -
Having the same issue on Linux (CentOS Stream)
Code: 1.59.0-insider
Extension: v2.9.1 -
I’m having the same issue on Windows 10 (although remotely connected to Linux over SSH)
Code: 1.59.0
Extension: v2.9.1
I do find that sometimes the PR view loads, and other times it doesn’t. I haven’t been able to decipher what the common denominator is that causes them to not load, but it seems like the more activity has happened on the PR, the more likely it is to NOT be displayed. They always display, but when the problem occurs, the view goes to a blank window almost immediately after it loads.
-
I am having the same error message but on the Pipelines view.
It displays blank and “Invalid time value” error is shown in the dev console.
I’m using MacOS, VSCode 1.59.1 and v2.9.1 of the extension.
If I revert the extension to v2.8.6 it works fine
-
Same issue with
VS Code 1.63.2
Extension: v2.10.1
Bitbucket Data Center v7.17.4mui.be2529db.js:1 RangeError: Invalid time value at $ (pullRequestDetailsPageV2.2fb41b13.chunk.js:1) at qe (pullRequestDetailsPageV2.2fb41b13.chunk.js:1) at qi (mui.be2529db.js:1) at hu (mui.be2529db.js:1) at sl (mui.be2529db.js:1) at ul (mui.be2529db.js:1) at Zu (mui.be2529db.js:1) at mui.be2529db.js:1 at t.unstable_runWithPriority (mui.be2529db.js:1) at Ho (mui.be2529db.js:1)
-
I am having the same issue when viewing any PR with a comment. If a PR doesn’t have a comment it loads fine, otherwise I get a blank page as shown above.
-
Getting the following errors:
-
@David Bohan Are you using Bitbucket Cloud or Bitbucket Server?
-
Account Deactivated @Nick Rundquist I'm not the person you asked, but I'm seeing the same issue (and errors in dev console) and using Bitbucket Server.
-
I’ve just released version 2.10.6 which should fix this issue. Let me know if you’re still seeing it.
-
Account Deactivated @Nick Rundquist thanks for the quick turnaround! I am able to read PR details again.
-
- changed status to resolved
- Log in to comment