Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timestamp in runs.json #1

Open
asazorojas opened this issue Mar 20, 2016 · 2 comments
Open

Timestamp in runs.json #1

asazorojas opened this issue Mar 20, 2016 · 2 comments

Comments

@asazorojas
Copy link

Hey guys, great job with the scoreboard... one little question: in the runs.json file what does the timestamp field represent? the time between two consecutive requests to the feed-server or something else?

And BTW, where is the feed-server?

Bests!

@wookayin
Copy link
Member

Hi @asazorojas, sorry for the very late response.

The time.timestamp field in runs.json represents a snapshot number (revision) of the internal contest database. This is undocumented and originates from a legacy (original) design, hence the wrong and inappropriate name. Its intended usage is to keep track to which revision the last data update has been performed. If the feedserver is capable of deliver the changes only between the last revision (specified in that field) and the latest (e.g. changed_runs.json). However, I believe it is not mandatory as the scoreboard will also work if full run information runs.json is available (instead of partial deltas only).

BTW, In the following development version, I will fix the confusing name; some of compatibility might break.

I regret to inform that feedserver is not currently publicized. I should have released it earlier, but I have had no enough time to wrap it up. Hope I can make it soon.

@asazorojas
Copy link
Author

No problem, I figured it out because as you said it works perfectly fine ;).Thanks @wookayin !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants