-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict Between OpenAI and Spellcheck Add-ons When Sending Prompt in NVDA 2023.3 #15
Comments
The biggest issue here in my opinion is that, since the OpenAI library runs in the main thread, that error message freezes the entire screen reader until the user dismisses the popup. That assuming that the OpenAI library is the one reponsable for the popup message in the first place. |
In other words, a message box that is displayed outside the UI thread. |
Thanks @rayo-alcantar for the report and @jmdaweb for the explanations. For reference, here is the traceback:
|
I have encountered a compatibility issue between the OpenAI add-on (version 23.12.03) and the Spellcheck add-on (version 1.1) in NVDA (version 2023.3). The issue arises when attempting to send a prompt (using Control + Enter) while both add-ons are enabled.
Steps to Reproduce:
Expected Behavior:
The prompt should be sent and processed correctly without any errors, regardless of other enabled add-ons.
Actual Behavior:
When sending a prompt with OpenAI while Spellcheck is active, the process fails, and NVDA displays an error related to missing arguments.
Temporary Solution:
Deactivating the Spellcheck add-on, the OpenAI prompt submission works correctly. This suggests a conflict between the two add-ons.
Additional Information:
I am unable to provide an error trace as the issue prevents it from being captured. The problem is resolved only by deactivating Spellcheck, indicating a potential conflict between these two add-ons.
Environment:
• NVDA version: 2023.3
• OpenAI Add-on version: 23.12.03
• Spellcheck Add-on version: 1.1
The text was updated successfully, but these errors were encountered: