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
I have run q doctor in the affected terminal session
I have run q restart and replicated the issue again
Operating system
macOS 15.3.1 (24D70)
Expected behaviour
Amazon Q should detect which version of asdf is installed / used and modify suggestions/autocomplete to use that versions commands. See the list of breaking changes with 0.16. For example, I'd expect to get a suggestion for asdf set java <version> instead of asdf local java <version> when trying to change the java version with asdf 0.16+.
Actual behaviour
Regardless of the asdf version used, Amazon Q is offering suggestions from versions before v0.16.For example, when using asdf 0.16+, I still see suggestions for prior versions, such as asdf local java <version>, etc. See the full list of breaking changes with 0.16.
Steps to reproduce
Upgrade asdf to version 0.16+ and see that Amazon Q is still referencing commands from prior releases.
Checks
q doctor
in the affected terminal sessionq restart
and replicated the issue againOperating system
macOS 15.3.1 (24D70)
Expected behaviour
Amazon Q should detect which version of asdf is installed / used and modify suggestions/autocomplete to use that versions commands. See the list of breaking changes with 0.16. For example, I'd expect to get a suggestion for
asdf set java <version>
instead ofasdf local java <version>
when trying to change the java version withasdf
0.16+.Actual behaviour
Regardless of the
asdf
version used, Amazon Q is offering suggestions from versions before v0.16.For example, when usingasdf
0.16+, I still see suggestions for prior versions, such asasdf local java <version>
, etc. See the full list of breaking changes with 0.16.Steps to reproduce
Upgrade asdf to version 0.16+ and see that Amazon Q is still referencing commands from prior releases.
Environment
The text was updated successfully, but these errors were encountered: