instruqt/cli

Instruqt CLI. Contains the releases of the Instruqt commandline interface.

cli's Issues

`instruqt auth login` fails on headless machines

When trying to login to the Instruqt CLI on a machine without a GUI (for example, a cloud VM or Google Cloud Shell), the auth command fails:

$ instruqt auth login
==> Signing in to instruqt
==> Please open the following address in your browser and sign in with your Instruqt credentials:
==> http://localhost:15777/
    [ERROR] exec: "xdg-open": executable file not found in $PATH

Is there a flag or option to skip the xdg-open step? On Google Cloud Shell or an VM, it is easy to visit http://localhost:15777/ manually, so there is no need to auto-open a browser.

How to configure default organisation after logging in with github?

steps:

1. command instruqt auth login
2. in web browser login with my github
3. enter command instruqt track create
   expected:
   To be able to do what it says in the docs
   
   Actual Result:
   Cli returns:
   [ERROR] Default organization not configured. Use instruqt auth login to set it.

CLI broken update

Running arm64 macbook air m2, guessing update must have pulled latest amd64

➜  Projects ./instruqt track logs {{ organization }}/{{ track }}
An update of the CLI is required. Type yes to update now: yes
==> Updating CLI.
    OK

    The CLI has been updated. Please re-run your command.
➜  Projects ./instruqt track logs {{ organization }}/{{ track }}
zsh: bad CPU type in executable: ./instruqt
➜  Projects ./instruqt track logs {{ organization }}/{{ track }}
zsh: bad CPU type in executable: ./instruqt

Apple silicon and arm64 build of cli

It would be great to have apple silicon and arm64 build of the instruqt cli

Is there a CHANGELOG somewhere?

It would be useful to have a CHANGELOG, especially for changes affecting users of the cli.

`instruqt auth login` fails on Windows Subsystem for Linux

I'm using WSL on Windows 10; can't log in using the command line tool because it wants to open a browser...

Can we get a ARM binary too?

Provide an homebrew formula for mac

I took the initiative to create this: https://github.com/ams0/homebrew-instruqt but will be great to have it turn into:

$> brew install instruqt/instruqt/instruqt

Potential security issue?

Accidentally stumbled upon this during one training using Instruqt's platform. .aws is usually/conventionally the folder where AWS credentials and secret configs exist.

Unable to use CLI after update

CLI fails after update

➜ instruqt auth login
==> Signing in to instruqt
==> Please open the following address in your browser and sign in with your Instruqt credentials:
==> http://localhost:15777/
==> Storing credentials
    [ERROR] Post "https://play.instruqt.com/graphql": dial tcp: lookup play.instruqt.com on 127.0.0.1:53: read udp 127.0.0.1:62817->127.0.0.1:53: i/o timeout

Login works after reverting my CLI back to 2031-3aadb7d. CLI fails again after forced update.

⇣7% ➜ instruqt auth login
==> Signing in to instruqt
==> Please open the following address in your browser and sign in with your Instruqt credentials:
==> http://localhost:15777/
==> Storing credentials

==> Run instruqt track create to create your first track.
    OK

ProductName:	Mac OS X
ProductVersion:	10.15.7
BuildVersion:	19H1615


Darwin <REMOVED> 19.6.0 Darwin Kernel Version 19.6.0: Sun Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64 x86_64

Misleading CLI error regarding `track.yml`

Issue

On a few occasions, I and some members of my team have encountered an issue when attempting to push to instruqt. The CLI reports an error with the track.yml file, but the actual error seems to be with the assignment.md file in the teaser or contents properties.

Track info

slug: multi-analyzer
org: mongodb-dev

Error

2024-03-29T14:49:17.1526677Z ==> Reading track definition
2024-03-29T14:49:17.7525015Z     �[1;31m[ERROR]�[0m yaml: line 11: could not find expected ':'
2024-03-29T14:49:17.7526341Z     
2024-03-29T14:49:17.7551897Z ##[error]Process completed with exit code 1.

Actual issue:

In assignment.md, the issue actually seems to an improperly formatted teaser or contents property in the front-matter. If the indenting is off, it exits with an error

Suggested change

It seems like a more accurate error message in the CLI could mitigate some issues for users. There have been instances in the slack channel of this very issue impacting other teams as well. An error message that is specific to the file that is causing the problem would be better.

examples:

• slack thread 1
• slack thread 2