"Error creating cloud task" when no associated environment available

[adrianveen]

What version of the VS Code extension are you using?

0.4.12

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What steps can reproduce the bug?

Run in the cloud will fail to run and produce an error ("Error creating cloud task") shown as a brief popup at the top of the chat window. This happens when attempting to run a prompt and there are no associated cloud environments with your project.

I'm orking on an organization owned, private repository, so I cannot create an environment from the web application. If this is the intended functionality, then the documentation should make that clear and the error specify the issue as well.

What is the expected behavior?

The prompt runs on the cloud after being sent.

What do you see instead?

The brief error message at the top of the chat window.

Additional information

No response

[gpeal]

Did you have an environment selected below the composer? If so, what was the environment relative to the repo you had open?

What did you have for the starting state dropdown? "Start from my local change" or "master/main/sometihng else"?

[adrianveen]

There was an environment selected, but it was unrelated to my working repo. I was unable to "deselect" an environment entirely (no env selected), only select a different one.

The repo I'm working on is organization owned, and currently private, even though I have access to to it, including cloning, forking etc., I'm not able to see it listed under "Environments > New" when following the "Environment Settings ->" option from the extension.

The starting state dropdown was "start from my local changes".

I understand that unless I'm an owner of the repository, or listed as a collaborator, I may not be able to create an environment for it. But I would like that to be clarified either in the documentation or the error message if that's the intended functionality 🙏

[AbbasAlibhaiER]

+1

[YasinHossain]

still facing the same problem