A catch-all place for feedback collected during a user testing session, which can later be broken into separate issues.

Bugs

Minify breaks when trying to view Python (known bug) REMOVED

• Reviewer: Prof. Kate, James R., Yucheng W.
  • Steps to reproduce the problem: Use minify and then click Python checkbox, output breaks (known bug)

Python 2 doesn't work (known bug) FIXED

• Reviewer: Collin V., Jamie K.
  • Steps to reproduce the problem: Select different target under compilation parameters

Suggestions

App

• Reviewer: Prof. Kate

  • Help the tutorial team to be able to add a "run" button next to a block of code so that the output will appear directly under it.
    • Talk to tutorial team for API functions
  • Information icon/pop-up to tell first-time users what the options mean RESOLVED
  • Add label for "Coconut Compilation Parameters" RESOLVED
  • Show line numbers in the editor and compiled Python (add an option?) RESOLVED
  • Include a way to save the file RESOLVED
  • Stress-testing? (What happens when we have a timeout?)
    • Timeout error is not informative

• Reviewer: Collin V., Jamie K.

  • Explain what no_tco is REMOVED

• Reviewer: James R., Yucheng W.

  • What is the difference between "Keep line numbers" and "Keep lines"? REMOVED
  • (repeat) Explain what no_tco is
  • (repeat) Show line numbers in the editor and compiled Python
  • Different font size RESOLVED

• Reviewer: Chen P., Nelll W.

  • Theme color options (e.g. purple) WON'T DO
  • (repeat) Bigger font size
  • (repeat) Show line numbers in the editor and compiled Python

• Reviewer: Evan H.

  • Can't tell difference between traceback and not traceback RESOLVED
  • Help tutorial team RESOLVED

README

• Reviewer: Luis H.

  • "Add a video...? Just kidding."

• Reviewer: Nelll W.

  • Looks outdated, since the highlighted traceback now shows in the Python

• Reviewer: Collin V., Jamie K.

  • Looks good.

Update README.md

• Delete index route in app/app.py
• Delete app/static
• Delete app/templates
• Delete test_page_loads in tests/test_interpreter.py

• Rename app/app.py -> app/my_app.py to support entry app function
• Add Zappa configuration

• coconut() method is too long

Use logging instead of print in app.py

Plans:

• Use TimedRotatingFileHandler

'provide an option to choose what Coconut version to use (or even "coconut-develop")'

Plans:

• N/A

I've been thinking about this and I think it might make sense to finally make a monorepo as we finish the project.

Pros

• Unified repository (all code, issues, & PRs in one place)
• Reduction of three organization repos to one repo
• Deploy frontend without the need of two different remotes

Cons

• Lose commit history of frontend (not a big deal)

Changes needed

• Create folder client in root directory with the contents of https://github.com/cs121-team-panda/coconut-interpreter-react
• Merge continuous integration CircleCI configs
• Delete https://github.com/cs121-team-panda/coconut-interpreter-react and https://github.com/cs121-team-panda/coconut-interpreter
• Rename this repository to coconut-interpreter
• Update README.md accordingly later

I'm sort of confused on how the code works on app.py. -bw

As a result, people will be able to see their code.

'provide a way to change the compilation parameters (e.g. compile to Python 3 instead of universal Python as if you had passed "--target 3")'

Plans:

• write/test backend
• implement frontend (@jcruz)
  • ideas: a gear? hover over run button for options?
• merge backend PR #51

The easiest way to get AWS credit is through HMC, since Mudd is part of the AWS educate program. Here are the instructions for setting that up. If that doesn't work for some reason, let me know, and I'm still trying to figure this out, but I'll probably have you file an expense report on Coconut's Open Collective page.

Idea: a button or changing the color

Status: GREEN

Task:

• Let's highlight all errors in red.

Plans:

• Parse traceback in backend and send object with line number, error message to client

Probably use something from https://loading.io/ to show that the app is running after you click 'run'.

The following code:

'a'

produces an error since our separator expects a newline.

From cs121-team-panda/coconut-interpreter-react#38

The program didn't handle the case when the compiler has a return code of something except 0.

'provide an option to show the user the compiled Python (without the header)'

Needed for Phase 2 presentations.

Progress: Green

Plans:

• Measure the run-time for all coconut code from the tutorial website and put it in the table.
• Measure the run-time on Heroku; try with small code and big code from the tutorial.
• Measure the run-time on AWS; same as above.

• Protect the os module in Python.
• Allow only standard libraries.

'fix the "Mixed Content" message shown in the Chrome developer console'

Ideally I could do something where yarn start would give me a backend that I am testing?

• Add git clone as initial step
• Explicitly say install Node separately from Yarn
• Add make sure running Python 3?
• Add note under Python packages: installed with pip
• Fix requirements.txt (Werkzeug to version 0.12)

See here

"ideally with some pre-defined starting code"

and send to the group doing the tutorial once we're done

Status: Yellow

Plans:

• Get the emails of the tutorial team.
• Communicate with other teams, ask for their pipeline.
• Show how to embed the editor to the other team.

It seems that Heroku is able to handle when 2 processes are invoked at the same time.

'provide a way to interrupt execution (as if you pressed Ctrl-C)'

Plans

• Figure out how map the process to the client so we can cancel an ongoing process.

The compiled file is required to have the following string only once and somewhere. Otherwise, it creates the following error.

# Compiled Coconut: -----------------------------------------------------------\n\n

Causes an error in this case.

Status: Yellow

Plans:

• Get AWS Credit.
• Change CircleCI to deploy to AWS instead of Heroku.
• Research AWS Lambda
• (If using Docker)
  • Setup docker image.
  • Have a single user's requests direct to the same container and have a different container for each user.

References:

• https://github.com/christophetd/docker-python-sandbox
  • We would need to modify this so that each request does not create/destroy its own container.
• http://containertutorials.com/docker-compose/flask-simple-app.html
• https://djangostars.com/blog/what-is-docker-and-how-to-use-it-with-python/

Example:

Major security concerns for online compilers/interpreters are malicious codes submitted from users. In the current system, the code is evaluated on the server-side. From the server perspective, the server may happen to run the potentially malicious code. Some potential problems may arise, at least but not limited to:

• DDoS attack to exhaust the server's resources.
• Manipulate file structures using os module

There are two main ways of addressing this security concern: running code on client-side and on server-side.

1. Client-side
   In short, we can execute everything client-side using JavaScript, and possibly use tools like Brython that essentially converts Python script to JavaScript and in order for it to be executed on the client-side.

Keypoints

• Not work with some of the libraries.
• Depend on specific versions of library.
• Tend to be 3 to 5 times slower.

2. Server-side
   2.1 Use Sandbox
   General ideas are to use the concept of sandboxing that lets the potentially malicious code in that sandbox. See more discussion here. In Python, we have some discussions here.
   2.2 Use RestrictedPython
   RestrictedPython 4.0b2 is a defined subset of the Python language which allows to provide a program input into a trusted environment.

Keypoints

• Faster
• Not depend on specific versions of library.

Thoughts on this issue are very appreciated.

Need to return only traceback related to coconut's code.

Traceback (most recent call last):
  File "/home/circleci/project/tests/test_interpreter.py", line 88, in test_error
    assert ERR_OUTPUT in response.data
AssertionError

Stdout:
Finish compilation [5f1d2705-d2b3-4f34-84ee-b5bc1efaac56] to [5f1d2705-d2b3-4f34-84ee-b5bc1efaac56.py]
Error in running Coconut's code
Delete temp files 5f1d2705-d2b3-4f34-84ee-b5bc1efaac56 and 5f1d2705-d2b3-4f34-84ee-b5bc1efaac56.py
Output is
b'Traceback (most recent call last):\n  File "5f1d2705-d2b3-4f34-84ee-b5bc1efaac56.py", line 638, in <module>\n    1 + "a"\nTypeError: unsupported operand type(s) for +: \'int\' and \'str\'\n'
		

E.g. a response such as

{
  output: "hello, world"
}

This is in preparation to not have to refresh the page to run the code.

• Installation instructions
• How to run
• Update features (i.e. Python switch, updated error messages, etc.)

'nicely highlight Coconut-specific syntax (e.g. "match" or "case")'

Status: GREEN

Plans:

• List all the keywords to be highlighted (Ref here)
• Separate keywords into different groups because we plan to highlight them differently, I think.
• Extend the syntax formatting based on here on some small expressions + Test
• Populate and extend the syntax highlighting for all keywords.

Prevent programs from taking arbitrarily large CPU or memory to compile.