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

allow penalty-free execution of whitelisted shell commands #41

Open
filipsch opened this issue May 28, 2018 · 4 comments
Open

allow penalty-free execution of whitelisted shell commands #41

filipsch opened this issue May 28, 2018 · 4 comments

Comments

@filipsch
Copy link
Contributor

filipsch commented May 28, 2018

@gvwilson commented on Sun May 27 2018

As a user doing a Unix shell course, in consoleExercises I want to be able to run commands like pwd and ls as often as I like without triggering execution of SCTs (influencing submission metrics). After discussion with @filipsch, it seems we could add a whitelist of commands that short-circuit execution of SCTs. These could be provided on a per-exercise, per-chapter, or per-course basis; the last of these three is probably sufficient for everything except the first few chapters of the "Intro to Shell" course (where we definitely don't want these commands short-circuited).

@filipsch filipsch self-assigned this May 28, 2018
@filipsch
Copy link
Contributor Author

I would definitely opt for a per-exercise level setup first, as we can just piggy back on top of the SCT with a Ex().whitelist() function that alters the typical SCT execution in some way. Doing things on per-chapter and per-course basis is going to be more tricky.
This will also require backend changes.

@gvwilson
Copy link

Is there something like a pre-exercise code block at the chapter level? I suspect that for most chapters, I'll want to whitelist exactly the same set of commands for every exercise.

@filipsch
Copy link
Contributor Author

@gvwilson no there isn't, that's why this would be so hard.

@gvwilson
Copy link

Understood.

@filipsch filipsch removed their assignment Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants