Skip to content

Latest commit

 

History

History
134 lines (95 loc) · 10.8 KB

CHANGELOG.md

File metadata and controls

134 lines (95 loc) · 10.8 KB

Changelog

v3.2.0 (2021-04-11)

Full Changelog

Fixed bugs:

  • Fix issue where python processes run forever #23

Merged pull requests:

v3.1.0 (2021-03-27)

Full Changelog

Merged pull requests:

v3.0.0 (2021-03-24)

Full Changelog

Fixed bugs:

  • Engine stalls when submitted code returns None. #19

Closed issues:

  • Switch from running code in LXC to Docker? #59
  • Build script for lovelace-image #57
  • Multiple gunicorn workers #52
  • Turn into a real Python package? #51
  • Tiny optimization: lxc file pull all output pickles at once #47
  • Dynamic resources must all have different names #44
  • Document setting up lovelace-engine as a systemd service #38
  • Document symbolic links used #32
  • Improve Julia runner performance #24
  • Add support for C and C++ #20
  • Engine must run users’ programs in parallel #12

Merged pull requests:

v2.0 (2019-07-22)

Full Changelog

Fixed bugs:

  • I think engine forgets to delete dynamic resources #36

Closed issues:

  • Merge the different runners? #46
  • make test should glob for *.py files #34
  • Do not disable existing loggers when using logging.ini to configure a logger #42
  • Performance benchmarking #28
  • Execute test cases in batches #25
  • Engine should store temporary files in /tmp #22

Merged pull requests:

v1.1 (2019-01-04)

Full Changelog

Closed issues:

  • Add support for Julia #13
  • Augment the Python Runner with the ability to use either Python 2 or 3 #10
  • Set up automated deployment of the Engine #6

v1.0 (2018-11-26)

Full Changelog

Closed issues:

  • Add support for Fortran #14
  • Engine must run users' code securely #11
  • Setup a custom global logger. #8
  • Accurate reporting of CPU time and RAM usage by the engine. #7
  • As a user, I want my submissions to undergo static Python code analysis. #5
  • As a developer, I would like to have a Makefile to automate setting up my development environment #4
  • Allow engine clients to send code for execution #3
  • Decide: what kind of format should we use for inputs and outputs? #2
  • Decide: should we expect submitted code to read input from a file, command line, or both? #1

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator