Info

Open Website

Testing and Issues

You can test this app and submit issues during the testing period of the Data Clustering Contest, Stage 2 contest.

Entries with serious issues will not be able to win the contest, but even minor issues might be important for overall results.

Voting

24
by rating

Issues

Fair Mammoth Jul 31 at 22:20
The following issues have been identified while testing the algorithm:

1.EN
– Certain important threads are not present in the 'Main' section and inside categories.
– It is not possible to evaluate sorting quality: most of the threads contain only 1-2 articles.
– Many threads are not relevant for the wide English-speaking audience.

2. RU
– Certain important threads are not present in the 'Main' section and inside categories.
– It is not possible to evaluate sorting quality: most of the threads contain only 1-2 articles.
– Many threads are not relevant for readers from Russia.
20
Fair Leopard Jul 7 at 16:10
In our preliminary tests, this submission received the following scores (out of 100):

Languages: 100
News EN: 90
News RU: 92
Categories EN: 37
Categories RU: 19
Threads EN: 35
Threads RU: 13
11
Fair Leopard Jun 23 at 20:40
We had to fix the following issues before running the algorithm and will apply relevant penalties during the final scoring:
- rebuild from source code with nightly rust (due to the error: version 'GLIBC_2.29' not found)
Suave Penguin Jun 24 at 07:54
Thank you for that
But i don't understand why my server part isn't working according to the error log query returned no rows is only possible if no article was indexed by the server hence nothing can be returned since there is no article
Fair Leopard Jun 24 at 13:11
Right after the first start of the server, a GET request is made to check server availability. The server must respond with error 503 until it's ready (https://contest.com/docs/data_clustering2#stage-2-indexing-and-ranking). Your server returned an empty response instead (CURL request failed with error #52: Empty reply from server).
Suave Penguin Jun 24 at 14:14
In order to panic at line 510 a specific get request must be made i.e GET threads/<period>&<lang_code>&<category> with no article in the database. Which fails the server expects at least one article in the database which will then be used to get the date of the newest article if there isn't any article it will crash
the flow of your dc-check.php was PUT -> GET -> DELETE and repeat. so i assumed before any GET /threads request there should be entries in the database.

If there is at least one entry in the database. The error should disappear so probably using PUT->GET->DELETE will return articles

Also another minor issue was mispelling of 'sport' in line 187 of categories.rs. I would appreciate if that was renamed to 'sports'
Fair Leopard Jun 24 at 21:23
The testing script only checks that the app launches correctly and uses the correct output format for all types of requests.
We had to re-run your algorithm using DELETE request instead of GET for checking server availability and will apply relevant penalties during the final scoring.
Nobody added any issues yet...