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
This was discovered when testing #5981 which is based on the prerelease/2025.01 branch, however, the issue can be reproduced on main (currently @ fe3a53c) as well.
I think we'll need to step through commits from 2bc1b74 and earlier to see when this issue was first introduced. This commit is when we branched from main to create the prerelease/2025.01 branch.
Interpreter details:
Any
Describe the issue:
In dev builds (at least Mac and Windows), the Issue Reporter can be opened, but is blank and an error occurs. It is not possible to send an issue report through the Issue Reporter.
Interestingly, Jonathan noted that when using the debugger to step through the dev build, the Issue Reporter works fine!
Release builds don't have this issue.
mac_dev_issue_reporter.mp4
Steps to reproduce the issue:
Open a dev build of Positron Desktop on Mac or Windows
Click on Help in the top bar, then Report Issue
The Issue Reporter opens, but is blank and an error shows
Expected or desired behavior:
The Issue Reporter should show the issue submission form and no error should occur.
Were there any error messages in the UI, Output panel, or Developer Tools console?
Mac
No errors in the Dev Tools console, but the error notification shows:
Failed to execute 'invoke' on 'CreateHTMLCallback': The provided callback is no longer runnable.
Windows
No notification error, but the Dev Tools console includes:
[main 2025-01-15T15:19:09.119Z] [uncaught exception in main]: Error: Titlebar overlay is not enabled
log.ts:382
[main 2025-01-15T15:19:09.120Z] Error: Titlebar overlay is not enabled
at AuxiliaryWindow.updateWindowControls (file:///C:/Users/sharon/positron/out/vs/platform/windows/electron-main/windowImpl.js:307:17)
at AuxiliaryWindow.setWin (file:///C:/Users/sharon/positron/out/vs/platform/windows/electron-main/windowImpl.js:100:22)
at AuxiliaryWindow.doTryClaimWindow (file:///C:/Users/sharon/positron/out/vs/platform/auxiliaryWindow/electron-main/auxiliaryWindow.js:69:18)
at AuxiliaryWindow.tryClaimWindow (file:///C:/Users/sharon/positron/out/vs/platform/auxiliaryWindow/electron-main/auxiliaryWindow.js:44:14)
at App.<anonymous> (file:///C:/Users/sharon/positron/out/vs/platform/auxiliaryWindow/electron-main/auxiliaryWindowsMainService.js:51:33)
at App.emit (node:events:519:28)
at n._init (node:electron/js2c/browser_init:2:12818)
at openGuestWindow (node:electron/js2c/browser_init:2:101599)
at WebContents.<anonymous> (node:electron/js2c/browser_init:2:89067)
at WebContents.emit (node:events:519:28)
at WebContents.callbackTrampoline (node:internal/async_hooks:130:17)
The text was updated successfully, but these errors were encountered:
System details:
Positron and OS details:
This was discovered when testing #5981 which is based on the prerelease/2025.01 branch, however, the issue can be reproduced on
main
(currently @ fe3a53c) as well.I think we'll need to step through commits from 2bc1b74 and earlier to see when this issue was first introduced. This commit is when we branched from main to create the
prerelease/2025.01
branch.Interpreter details:
Any
Describe the issue:
In dev builds (at least Mac and Windows), the Issue Reporter can be opened, but is blank and an error occurs. It is not possible to send an issue report through the Issue Reporter.
Interestingly, Jonathan noted that when using the debugger to step through the dev build, the Issue Reporter works fine!
Release builds don't have this issue.
mac_dev_issue_reporter.mp4
Steps to reproduce the issue:
Expected or desired behavior:
The Issue Reporter should show the issue submission form and no error should occur.
Were there any error messages in the UI, Output panel, or Developer Tools console?
Mac
No errors in the Dev Tools console, but the error notification shows:
Windows
No notification error, but the Dev Tools console includes:
The text was updated successfully, but these errors were encountered: