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
https://github.com/dosu-ai/example/issues/2
To address the issue where the sidebar does not appear when hovered over in compact mode on a maximized window, but works when the window is not maximized, you can try several steps. These include ensuring certain preferences are set correctly, checking the sidebar's default expansion state, and reviewing CSS rules that might affect visibility.
Dosu often links to nonexistent example issues under @dosu-ai, stating that they are relevant. Usually issue 1 or 2.
I found related issues that might be helpful:
https://github.com/dosu-ai/example/issues/1582
The suggested solution is that the issue will be addressed in the next update, as confirmed by the main developer. It has also been fixed in the latest update.
https://github.com/dosu-ai/example/issues/1558
The suggested solution is to try turning off the "Uniform Workspace Button" mod, as it may be causing the issue. Removing it and restarting has helped others.
Sometimes it uses issue numbers that exist on the repo, but are still irrelevant, all while still linking to a nonexistent example repo instead of the current repo. In both instances, it is citing words that have not been spoken in the issues it is attempting to link to.
This is a very common occurrence with this bot. Whenever it tries to link, the first link will almost always be accompanied with the description "This has been addressed, this has been confirmed by the developer, it's already fixed, update your program." At least for Zen, the second link, if one is provided, also usually mentions the Uniform Workspace mod. There was one issue, zen-browser/desktop#1634, that had this problem, and dosu likes to bring it up very frequently despite never actually successfully linking to this issue, or even getting its number right. It loves 1582 and 1558.
Unless it's misconfigured on this repo, it seems this feature is producing more noise than signal and it'd be best to take it down until it can be refined.
The text was updated successfully, but these errors were encountered:
different55
changed the title
Bot is really frickin' bad at identifying relevant issues. a
Bot is really frickin' bad at identifying relevant issues. And linking to issues.
Nov 28, 2024
Although, still, the issues are not relevant, and, still, for first links it insists that the issue was fixed in a past commit regardless of all other facts and inputs.
It's almost ok, it still links to irrelevant issues, showing its weird fondness for 1582 and 1558 as always, still linking to nonexistent example repos, but it does provide one tiny nugget of good info in its summary:
The suggested solution is that the feature will be added back as a mod.
This is actually correct, although it's not at all clear if it drew from a source or if it just got lucky.
zen-browser/desktop#3277 (comment)
Dosu often links to nonexistent example issues under @dosu-ai, stating that they are relevant. Usually issue 1 or 2.
zen-browser/desktop#3280 (comment)
Sometimes it uses issue numbers that exist on the repo, but are still irrelevant, all while still linking to a nonexistent example repo instead of the current repo. In both instances, it is citing words that have not been spoken in the issues it is attempting to link to.
This is a very common occurrence with this bot. Whenever it tries to link, the first link will almost always be accompanied with the description "This has been addressed, this has been confirmed by the developer, it's already fixed, update your program." At least for Zen, the second link, if one is provided, also usually mentions the Uniform Workspace mod. There was one issue, zen-browser/desktop#1634, that had this problem, and dosu likes to bring it up very frequently despite never actually successfully linking to this issue, or even getting its number right. It loves 1582 and 1558.
Unless it's misconfigured on this repo, it seems this feature is producing more noise than signal and it'd be best to take it down until it can be refined.
The text was updated successfully, but these errors were encountered: