We need to create an endpoint where user can poll for the submissions that were made using polling mode. All the jobs are stored in the src/models/Submission model which has a result key. While polling the user will give us the submission id and we'll return the submission object

• create a new folder src/routes/api/submissions
  • create an index.ts file which'll act as the url map
  • create an controller.ts file which'll export an object containing the handler
  • mount /api/submissions/:id endpoint to the polling controller
• write test for the api
  • Test if the API fives 403 if the api key is not provided or incorrect
  • Test if the API gives 404 if submission id not found
  • Test if the API gives returns the serialized submission model
  • update the test here and here

The dependency pg was updated from 7.12.0 to 7.12.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

pg is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency amqplib was updated from 0.5.3 to 0.5.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

amqplib is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Is this by design? Api key check should be required in prod.

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency ts-node was updated from 8.8.2 to 8.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/sequelize was updated from 4.27.27 to 4.27.28.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/sequelize is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

delete runPool[submissionId]

after the response has been sent ?

@abhishek97

The devDependency @types/chai was updated from 4.1.7 to 4.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/chai is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

In task-master, testcases.input is used whereas in jude-api it is defined as testcases[0].stdin and ...stdout

The dependency minio was updated from 7.0.11 to 7.0.12.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

minio is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency uuid was updated from 3.3.2 to 3.3.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

uuid is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency @types/request was updated from 2.48.2 to 2.48.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/request is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/express was updated from 4.17.0 to 4.17.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/express is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

for POST /api/run an extra body parameter called mode

Possible values of mode are -

• sync
• poll
• callback

For sync mode

• current mode of operation
• request is held till judgement is over, and then response is sent

Poll mode

• on request, we create a new job id
• send the job id in the response
• when judgement is over, in db, update the job status to done
• client can continuosly request status of job via job id
• GET /api/run/:jobid
  • responds status: running till it is incomplete
  • responses status: success or status: error with output and error base64 when done

callback mode (or webhook mode)

• request body will contain a callbackUrl param also
• when job is done, judge will make a POST request to callbackUrl

Add support to run project submissions in frameworks like react, node, django etc.

Check this issue on judge-taskmaster

• Create a new API endpoint /api/project
  • Create routes/api/project directory
  • Write validator to support following request payload

  {
    "problem": <problem zip url>,
    "submission": <submission zip url>,
    "lang": <language>,
    "submissionDirs": <directories that can be editted>,
    "timelimit" <timelimit in seconds>,
    "mode": "sync" | "poll" | "callback",
    "callback": <if mode is callback then url>
  }
  

  • Send job to queue required by judge-taskmaster
  • Implement onSuccess listener on the controller

Since we have added more features to the application we need to update our tests as well

• Add E2E API tests
  For writing these tests we will be using https://www.chaijs.com/plugins/chai-http/

  • Create test/e2e directory
  • For each of scenario we will have a separate file e.g. run scenario will have RunScenario.spec.ts
  • Write tests for run scenario
    Since there will be no consumers on the other end of the queue, we will have to call onSuccess method on the controllers manually using setTimeout function with the mock result and assert it with the response from the API
    • Run Code in Sync Mode and check if the response is correct
    • Run Code in Poll Mode
      • Check if the response is returning job id
      • Check if the job runs successfully after calling onSuccess method
    • Run Code in Callback Mode
      • Check if the response is returning job id
      • Setup another mock server or echo-server and assert the result
  • Write test for submit scenario
    • Run Code in Sync Mode and check if the response is correct
    • Run Code in Poll Mode
      • Check if the response is returning job id
      • Check if the job runs successfully after calling onSuccess method
    • Run Code in Callback Mode
      • Check if the response is returning job id
      • Setup another mock server or echo-server and assert the result

• Add Unit tests

  • Create test/unit directory
  • Create test for Validators in each of the scenario
  • Write exhaustive set of test requests and assert the result

Tests for project endpoint in the API and project validator

The devDependency @types/minio was updated from 7.0.2 to 7.0.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/minio is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

this seems wrong

Hello, I was testing your api through the docs link that was provided that too returns a null statement and when I did a get request from Postman it returns errorCode 001 with message "Key not found, or expired. Generate a new one in your console." Any help on how I could generate a key?

The devDependency request was updated from 2.88.0 to 2.88.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

request is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

SubmitValidator Class 's name is wrong

RunValidator and SubmitValidator both should check if the lang is a correct language.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• Replaced the old Node.js version in your .nvmrc with the new one
• The engines config in 1 of your package.json files was updated to the new Node.js version

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Since the judege-taskmaster and ** judge-api** codebases are used in production applications, the code needs to follow particular standards and guidelines, which can greatly increase its maintainability as a community project.

Therefore linters should be set as would be done under coding-blocks/judge-taskmaster#41 up to force standard code guidelines on the repository.

Working on it, would send PR as soon as the issue acknowledged.