Contest example: https://loj.ac/contest/40

Problem in contest example: https://loj.ac/contest/40/problem/1 (This URL is not considered as a problem URL in the current version.)

Due it is supporting that new Code Jam interface , I don't think that should not complicate to add Google Kick Start.

I have tried but that is not parsing the problem when I am clicking the '+' icon of 'Competitive Companion'.
Here is the code I have tried in CodeMarshalProblemParser.ts file in parsers/problem directory

import { Sendable } from '../../models/Sendable';
import { TaskBuilder } from '../../models/TaskBuilder';
import { htmlToElement } from '../../utils/dom';
import { Parser } from '../Parser';

export class CodeMarshalProblemParser extends Parser {
  public getMatchPatterns(): string[] {
    return ['https://algo.codemarshal.org/contests/*/problems/*'];
  }

  public async parse(url: string, html: string): Promise<Sendable> {
    const elem = htmlToElement(html);
    const task = new TaskBuilder().setUrl(url);

    const content = elem.querySelector('#main').querySelector('div').querySelector('div');

    task.setName(content.querySelector('div').textContent);

    const group = ['CodeMarshal'];

    task.setGroup(group.join(' - '));

    const scoreCpuTimeMemory = content.querySelector('p:first-of-type').textContent;
    let memory = scoreCpuTimeMemory.substr(scoreCpuTimeMemory.indexOf("Memory: ")+"Memory: ".length);
    memory = memory.substr(0, memory.length-2);
    const cpuTime = scoreCpuTimeMemory.substring(scoreCpuTimeMemory.indexOf("CPU: ")+"CPU: ".length, scoreCpuTimeMemory.indexOf("Memory: ")-1);

    task.setTimeLimit(parseInt(cpuTime, 10));
    task.setMemoryLimit(parseInt(memory, 10));

    const inputs = content.querySelectorAll(".sample-input");

    const outputs = content.querySelectorAll(".sample-output");

    for (let i = 0; i < inputs.length && i < outputs.length; i++) {
      const input = inputs[i].textContent;
      const output = outputs[i].textContent;

      task.addTest(input, output);
    }

    return task.build();
  }
}

This issue is open to discussion, but is primarily meant to keep track of progress on this idea, and to serve as some sort of documentation.

CHelper Companion was originally designed to solely support CHelper, but it would be cool if it would be able to send tasks to other tools aswell. Therefore, I have been thinking about sending the task information as a JSON-encoded string. This makes it easier for other (private) tools to work with the extension, as long as it can parse JSON input from an HTTP request.

The format

Here's an example of possible input:

{
    "name": "The A + B problem",
    "group": "Educational Codeforces Round 42 (Rated for Div. 2)",
    "url": "http://codeforces.com/problemset/problem/962/G",
    "memoryLimit": 256,
    "timeLimit": 2000,
    "testType": "single",
    "input": {
        "type": "stdin"
    },
    "output": {
        "type": "stdout"
    },
    "languages": {
        "java": {
            "mainClass": "Main",
            "taskClass": "TheABProblem"
        }
    },
    "tests": [{
        "input": "1 2\n",
        "output": "3\n"
    }, {
        "input": "5 5\n",
        "output": "10\n"
    }]
}

It's not required for a tool to parse all these options, since some of them are tool/language-specific. However, it is required for all extensions/tools that send data via this format to fill all required options.

Explanation

• name: The full name of the problem. Can be used for display purposes.
• group: Used to group problems together, which can be useful for archiving purposes.
• url: A link to the problem on the judge's website.
• memoryLimit: The memory limit in MB.
• timeLimit: The time limit in ms.
• testType: The type of the tests. Supports three options: "single", "multiNumber" and "multiEOF". Explanation of these three can be found on the JHelper wiki. This is currently CHelper and JHelper specific.
• input: An object which is used to configure how to receive input. Supported types:
  • stdin: Receive input via stdin. No additional options required.
  • file: Receive input via a file. The file name has to be given via the fileName option.
  • regex: Receive input via a file. The file to use is selected by taking the most recently modified that matches the given regex. The regex pattern to use has to be given via the pattern option.
• output: An object which is used to configure how to send output. Supported types:
  • stdout: Send output to stdout. No additional options required.
  • file: Send output to a file. The file name has to be given via the fileName option.
• languages: An object with language specific settings. At the moment this only contains Java settings, but since I don't think putting language specific settings as top-level options is a good idea, I decided to put them in an object. This also allows for other languages to have custom configuration added later on. Required keys:
  • java: An object with Java specific settings. Required options:
    • mainClass: The name of the outer class containing the solution.
    • taskClass: The classname-friendly version of the problem's full name. Cannot be the same as mainClass. Can also be useful for non-Java tools because a classname-friendly string is also a filename-friendly string.
• tests: An array of objects containing testcase-data. The JSON objects in the array all have two keys: input and output. Both the input and the output need to end with a newline character.

Pro's

• Being able to support more than just CHelper, even private tools as long as they can parse JSON input received via HTTP.
• At the moment the extension would break if Egor changes the Kattis parser. A JSON parser would resolve this issue.

Cons

• The extension would have to be renamed to something more general, since CHelper Companion implies it's only compatible with CHelper.

Tasks

• Convert the problem and contest parsers that still rely on CHelper to a JavaScript implementation
• Make all parsers parse the time limit of a problem
• Add a JSON parser to CHelper
• Add a JSON parser to JHelper
• Add the functionality to Hightail to accept JSON input via HTTP and parse it
• Make it possible to send the JSON data to multiple tools
• Make it possible to send the JSON data to a custom port on localhost to support private tools
• Create better documentation so it's easy for new tools to support the format
• Create an example to show how to support receiving the JSON data in other (private) tools
• Rename CHelper Companion to something more general (final step)

All changes on the extension relevant to this issue are done in the feature/universal branch.

Hi, during the AGC this morning, I was unable to use this extension to parse problems to CHelper. In IntelliJ, the Event Log said "CHelper: Unknown task type from Chrome parser: null"

After the contest I looked into it and saw there was an update recently, and installed 2.7.3 from this github -- and it worked again.

Tool name: CP Editor
Repo link: https://github.com/coder3101/cp-editor
Port: The default port is 10045, but can be set manually.

https://acmp.ru/index.asp?main=task&id_task=787

URL: https://loj.ac

Sample problem: 「IOI2019」Arranging Shoes

The sample tests are written in the <pre></pre> tags, I think it's usually safe to regard the first <pre></pre> tag as the first input, the second as the first output, the third as the second input…etc.

It will be better if only <pre></pre> in <h4 class="ui top attached block header">样例</h4> are considered.

Time limit: <span class="ui label">时间限制：1000 ms</span>

Memory limit: <span class="ui label">内存限制：1024 MiB</span>

Please add the following tool to your release and readme.

Tool name : Competitive Programming Helper
VS Code store link:https://marketplace.visualstudio.com/items?itemName=DivyanshuAgrawal.competitive-programming-helper

Source Code: https://github.com/agrawal-d/competitive-programming-helper/tree/master

Port:27121

Here's an example problem: here

URL: https://www.luogu.com.cn/

Sample problem: [IOI2019]Arranging Shoes

Sample tests:

• <div data-v-36768c72="" data-v-af321868="" class="sample-wrap sample" show-idx="true">
  • <div data-v-52f2d52f="" data-v-36768c72="" class="input">
  • <div data-v-52f2d52f="" data-v-36768c72="" class="output">

Time limit: <span data-v-83303c00="" class="value lfe-caption">1.00s</span>

Memory limit: <span data-v-83303c00="" class="value lfe-caption">125.00MB</span>

After the recent changes in the CodeJam environment, parser is not working at all. Can you please fix the issue as the new season of KickStart is starting on 24 March? Thanking You.

Problem example: http://uoj.ac/problem/3

The examples follow this format:

<h4>input</h4>
<pre>example</pre>
<h4>output</h4>
<pre>example</pre>

The TL and ML are a bit annoying, they are in MathJax:

时间限制：$3\texttt{s}$
空间限制：$512\texttt{MB}$

In http://uoj.ac/problem/492, the ML is 空间限制：$1\texttt{GB}$.

Hope you can solve this problem.

Also the contest: http://uoj.ac/contest/49

Problem in contest: http://uoj.ac/contest/49/problem/484

Can you add support for CSES platform as well?
Thanks!

Hi. Problems in HackerRank can be parsed but they come without the sample tests.

For example: https://www.hackerrank.com/contests/womens-codesprint-4/challenges/solve-the-queries/problem

Maybe a Layer 8 Problem.
I've got Chrome Extension installed.
And CHelper extension in Intellij.

The plugin parses from Codeforces like:
https://codeforces.com/problemset/problem/1307/G

but does not parse from Hackerrank, like:
https://www.hackerrank.com/challenges/simple-array-sum/problem

The CHacker extension behaves the same.

Please see AlexeyDmitriev/JHelper#101

It seems that the tool is having issues detecting the input for the problems in the interview preparation kit in HackerRank. The button in my Chrome browser does not even light up for such problems.

Here is a link to one such problem.

Here's an example problem: here

I tried parsing the contest - Link
However the parsing failed.

I can see that all the calls to the Codechef API were successful with 200.

Relevant screenshots -

Edit:- Same case for JULY15 and DEC15 as well.

I tried two problems during GCJ qual and both of them had equal name QualificationRound2019GoogleCodeJam2019 so I couldn't have two of them parsed in the same time.

When I'm on a codechef problem the marker changes to green and when I press it nothing happens.

Hacker Rank - 30-conditional-statements/problem

{
  "group": "",
  "input": {
    "type": "stdin"
  },
  "languages": {
    "java": {
      "mainClass": "Main",
      "taskClass": "HackerRankTutorials30DaysOfCode"
    }
  },
  "memoryLimit": 512,
  "name": "HackerRank - Tutorials - 30 Days of Code",
  "output": {
    "type": "stdout"
  },
  "testType": "single",
  *"tests": []*,
  "timeLimit": 4000,
  "url": "https://www.hackerrank.com/challenges/30-conditional-statements/problem"
}

As the result provided above shows, it doesn't parse multiple test cases. This is because of css query used in HackerRank Parser.

I guess [class*="challenge-body-html"] pre query should work.

Extension is parsing wrong input output data after updation of codeforces site updation by adding copy button. @jmerle

Hi!, first of all, thanks for your efforts to build this awesome extension, really saved a lot copy-pasting time.

My issue here is that the parser for zoj problems in vritual judge platform seems not working sometime. here is a picture showing this issue.

Add following links for you to verify, I was planning to fix by myself then to pull a request, but i didn't have any experience with node.js, so sad. :-) Have a nice day!
https://vjudge.net/problem/ZOJ-1586
https://vjudge.net/problem/ZOJ-1610
https://vjudge.net/problem/ZOJ-3209
https://vjudge.net/problem/ZOJ-3496

During onsite http://dashaai.contest.codeforces.com was used but parser was not active

Problems from UVA OJ are not being parsed. The plugin lights up when I open a problem on UVA OJ. When I click on it, it turns grey but nothing happens. The plugin works for other sites though.

Here are examples of 2 problems where this problem occur:

Problem1

Problem2

I am using the Google Chrome browser with the plugin.

Hi,

First of all, competitve-companion plugin is awesome. Thanks for the amazing work!

The following code chef problem has two test-cases but only one is parsed.

URL: https://www.codechef.com/APRIL19B/problems/MAXREM

P.S: I'm using Hightail along with competitive-companion

Can't parse https://acmp.ru/index.asp?main=task&id_task=120 this problem

First of all I wasn't sure whether to make this issue here or in CHelper/JHelper repo, as there seems to be a problem with both.

The problem

When parsing a full contest, I've noticed that the parsing stops after a number of tasks. It's not a problem with the parsing itself as the debug mode shows that they are all correctly parsed.

At first, it seemed like the problem happened with Google Chrome and on Windows only. Not on Firefox, and not on Linux. Using Chrome and Windows, the parsing always stops after exactly 6 tasks. But then, after some investigation, I've come to the conclusion that it depends on the number of problems to parse. I was able to reproduce these symptoms on Linux with Chrome as well with a large enough contest.

Fastest way to reproduce it: Try to parse a contest with more than 6 tasks on Windows using Chrome.

The cause

So I've done some investigation and for me there are two reasons for this.

• First, the simple servers created by CHelper/JHelper do not make a response, so after acquiring the data from competitive companion, they sort of "hang".
• Second, there is a timeout of 500ms set to the AJAX requests made to the server, which, on Chrome, results in all the requests still blocked after 500ms, to be canceled.

Why stop after exactly 6 tasks ? Because the maximum number of concurrent HTTP connections per hostname in Chrome and Firefox is 6. So the server processes the first 6 requests, and the subsequent ones are cancelled.

My suggestion

Ideally, the solution would be to make fewer AJAX calls by making one JSON with all the contest data, but that would break compatibility with the tools.
Otherwise, I would suggest to either remove the timeout of 500ms, provided that the tool's server always responds, or to increase it significantly. In both cases, the server has to respond in order not to block the following requests.

Why is the problem more explicit on Windows using Chrome ? Chrome on Windows seems to process AJAX calls slower than other browsers, something I still cannot understand. Maybe a bug ?
Here is a comparison between what happens making 10 AJAX requests on Chrome, on Windows and Linux. (The timeout for the calls is set to 5000ms)

Windows :

Linux :

Notice how the last 4 requests take more than 500ms to be processed. They would just be cancelled if I set the timeout to 500ms.

acmp.ru
https://informatics.msk.ru/

It would be nice if you add this sites too

The UI of AtCoder seems to have changed recently, and the plugin is not working on AtCoder now.

Hi, I'd like to use this extension during the contest where I will not have access to the Internet but where I an prepare archive with data

Can you explain how to create extension to Chrome/FF and how to install it offline later?

Thanks.

I just found that when a problem's inputs have symbols like greater('>') or less('<'), they will be parsed into &gt, &lt respectively.

For example this link

POC:

Possible place to fix:

Here innerHtml doesn't parse &gt and &lt to '>' and '<', I tried to replace this function to innerText, but it gave me an error. so sad :-(

When I solving https://train.usaco.org/usacoprob2?a=8Vt1VSIM12q&S=subset, the usaco parser is not working.
Maybe the https is the reason?

Hi!

I am using this plugin + clion. You know it's so cool. I can actually parse contest in one click. It will nice if add topcoder too.

@jmerle
v2.9.2 has not been released at Chrome Web Store yet.
Is there any problem happened?

http://acmp.ru/index.asp?main=task&id_task=536

Third test should be

1 8 3
9

URL https://official.contest.yandex.ru/opencupXIX/contest/10486/problems/7/?lang=ru

stacktrace:

content.js:8004 TypeError: Cannot read property '1' of null
    at resolve (content.js:36727)
    at new Promise (<anonymous>)
    at YandexProblemParser.parse (content.js:36720)
    at content.js:7999
    at Generator.next (<anonymous>)
    at content.js:7962
    at new Promise (<anonymous>)
    at __awaiter (content.js:7958)
    at parse (content.js:7992)
    at handleMessage (content.js:8019)

HTML file

I couldn't parse contest but I could parse problem

When I try to click on the extension + icon, it just doesn't show up. Not a pop up nor eventlog nothing.
Please help me. I have installed CHelper plugin on intellJ. Thanks in advanced.

Looks like it is not working for AtCoder. It used to work couple of days back. I have tried using it on Mac/Chrome as well as on Windows/Chrome. It does work for other sites though such as CodeForeces, CSAcademy, etc.

Hey, I am tried using this extension for both CHelper (IntelliJ Idea) and JHelper(Clion) But it is not parsing any Problem to the IDE.
I am using Linux and my internet is behind a proxy.

Code Chef contest

Hi,
CodeChef website parsing is not working.

The error message is:

content.js:1785 TypeError: Cannot read property 'textContent' of null
    at USACOTrainingProblemParser.<anonymous> (content.js:3990)
    at Generator.next (<anonymous>)
    at content.js:3964
    at new Promise (<anonymous>)
    at __awaiter (content.js:3960)
    at USACOTrainingProblemParser.parse (content.js:3976)
    at content.js:1780
    at Generator.next (<anonymous>)
    at content.js:1749
    at new Promise (<anonymous>)

And I found this code in source:

task.setName(elem.querySelector('center > h1').textContent);

But in https usaco, the task name is embraced with

<center><b><font size="7"></font></b></center>

And the diff causes the error above.

You must add https://practice.geeksforgeeks.org. Example: https://practice.geeksforgeeks.org/problems/path-in-matrix/0

I am using version 2.9.1 on Chrome.
Tried parsing CodeForces task and CSAcademy and those worked fine.

Here is the error (looking from developer tool) :

content.js:1874 TypeError: Cannot read property '1' of null
at AtCoderProblemParser. (content.js:591)
at Generator.next ()
at content.js:570
at new Promise ()
at __awaiter (content.js:566)
at AtCoderProblemParser.parse (content.js:582)
at content.js:1869
at Generator.next ()
at content.js:1838
at new Promise ()

Hi,

Thanks for developing the competitive-companion plugin. Its amazing! ❤️

I found an issue while parsing this problem from codeforces.com.

Special characters like > and < in the test cases are not parsed properly

I expected the parsed output to be:

3
2
<>
3
><<
1
>

Actual parsed output:

3
2
<>
3
><<
1
>

P.S: I'm using Highttail along with competitive-companion plugin