Skip to content
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

"Unable to detect the current shell." when running Vagrant command #2115

Closed
3 tasks done
dms-cat opened this issue Mar 2, 2020 · 4 comments · Fixed by #2147
Closed
3 tasks done

"Unable to detect the current shell." when running Vagrant command #2115

dms-cat opened this issue Mar 2, 2020 · 4 comments · Fixed by #2147
Assignees
Labels
area/error-handling Bad error messages/insufficient error handling kind/bug Something isn't working as expected

Comments

@dms-cat
Copy link

dms-cat commented Mar 2, 2020

Issue

vagrant ssh default --command='poetry shell' fails with

Unable to detect the current shell.

If I instead run vagrant ssh default and then poetry shell it works fine.

I've also tried variants like vagrant ssh default --command='bash -ic "poetry shell"' with the same result.

@dms-cat dms-cat added the kind/bug Something isn't working as expected label Mar 2, 2020
@sambonner
Copy link

It looks the maintainer of Shellington recommends providing a default shell as a fallback. Is there a reason why this was not implemented for Poetry?

@finswimmer finswimmer self-assigned this Mar 8, 2020
@finswimmer finswimmer added the area/error-handling Bad error messages/insufficient error handling label Mar 8, 2020
@finswimmer
Copy link
Member

Hello @sambonner,

thanks a lot for reporting and linking to a possible solution.

Fix is on the way: #2147

fin swimmer

@abn abn closed this as completed in #2147 Apr 6, 2020
abn pushed a commit that referenced this issue Apr 6, 2020
@johannesgiani
Copy link

@dms-cat can you provide an example vagrant file of how you provision poetry? I am stuck here.

Copy link

github-actions bot commented Mar 2, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/error-handling Bad error messages/insufficient error handling kind/bug Something isn't working as expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants