{ "id": 342035, "title": "Why won't Kaggle show submission time?", "url": "/competitions/AI4Code/discussion/342035", "author_name": "", "post_date": "2022-08-05T10:15:50.112613200Z", "votes": 17, "comment_count": 12, "views": 0, "content": "

Is there any reason why Kaggle won't show us submission time? @argv

\n

I can't think of a good reason why this is the case. They are tracking this and it doesn't seem to be hard to add it. But, still after 12 years of Kaggle, I refresh the submission page and calculate submission time on my own.

", "messages": [ { "id": "1885670", "postDate": "08/05/2022 10:15:50", "content": "

Is there any reason why Kaggle won't show us submission time? @argv

\n

I can't think of a good reason why this is the case. They are tracking this and it doesn't seem to be hard to add it. But, still after 12 years of Kaggle, I refresh the submission page and calculate submission time on my own.

", "rawMarkdown": "Is there any reason why Kaggle won't show us submission time? @argv\n\nI can't think of a good reason why this is the case. They are tracking this and it doesn't seem to be hard to add it. But, still after 12 years of Kaggle, I refresh the submission page and calculate submission time on my own.", "votes": null }, { "id": "1885761", "postDate": "08/05/2022 11:19:28", "content": "

Still 13G cpu Mem and 16G gpu Mem😄. It would be much better if we could infer 2-3 times faster and limit submission time to 4 or 3 hours. Saving much of our time.

", "rawMarkdown": "Still 13G cpu Mem and 16G gpu Mem😄. It would be much better if we could infer 2-3 times faster and limit submission time to 4 or 3 hours. Saving much of our time.", "votes": null }, { "id": "1885796", "postDate": "08/05/2022 11:35:51", "content": "

I agree with that as well. But adding submission time seems trivial. And 0 cost.

", "rawMarkdown": "I agree with that as well. But adding submission time seems trivial. And 0 cost.", "votes": null }, { "id": "1885841", "postDate": "08/05/2022 12:03:08", "content": "

Totally agree with you, I do not undertand what leak will happen if show running time as we only have 5 submmisons each day and we can also get running time by manually watch progress.

", "rawMarkdown": "Totally agree with you, I do not undertand what leak will happen if show running time as we only have 5 submmisons each day and we can also get running time by manually watch progress.", "votes": null }, { "id": "1886007", "postDate": "08/05/2022 13:59:55", "content": "

Having submission time would make my kaggling experience so much better.

", "rawMarkdown": "Having submission time would make my kaggling experience so much better.", "votes": null }, { "id": "1886059", "postDate": "08/05/2022 14:42:15", "content": "

It could be gamed to get (limited) information from the private test set.

", "rawMarkdown": "It could be gamed to get (limited) information from the private test set.", "votes": null }, { "id": "1886062", "postDate": "08/05/2022 14:43:43", "content": "

How? What is the difference of manually refreshing the submission page?

", "rawMarkdown": "How? What is the difference of manually refreshing the submission page?", "votes": null }, { "id": "1886231", "postDate": "08/05/2022 16:33:37", "content": "

I can confirm the reason that we don't show times is to limit their utility in automated/high-volume probing. There are a couple channels where information can leak out--error messages, errored vs. not, submission timing--so we try to strike a balance between providing some debugging information without allowing too much information exfiltration.

", "rawMarkdown": "I can confirm the reason that we don't show times is to limit their utility in automated/high-volume probing. There are a couple channels where information can leak out--error messages, errored vs. not, submission timing--so we try to strike a balance between providing some debugging information without allowing too much information exfiltration.", "votes": null }, { "id": "1888843", "postDate": "08/07/2022 19:55:47", "content": "

@wcukierski Is there any other way for us to get submission time without having to look at the submission page or refresh non-stop? I am spending a ton of time on this, instead of solving the problem.

", "rawMarkdown": "wcukierski Is there any other way for us to get submission time without having to look at the submission page or refresh non-stop? I am spending a ton of time on this, instead of solving the problem.", "votes": null }, { "id": "1893649", "postDate": "08/11/2022 01:01:50", "content": "

@crodoc Try this script - https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/201047
\nWorks well, I have used it in the past.

", "rawMarkdown": "crodoc Try this script - https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/201047 \nWorks well, I have used it in the past.", "votes": null }, { "id": "1893667", "postDate": "08/11/2022 01:34:10", "content": "

Information can be leaked using sleep

", "rawMarkdown": "Information can be leaked using `sleep`", "votes": null }, { "id": "1894288", "postDate": "08/11/2022 11:34:00", "content": "

@wcukierski is using the script above allowed?

", "rawMarkdown": "wcukierski is using the script above allowed?", "votes": null }, { "id": "1896377", "postDate": "08/12/2022 19:27:07", "content": "

@crodoc yes

", "rawMarkdown": "crodoc yes", "votes": null } ], "comments": [ { "id": 1885761, "author_name": "goldenlock", "author_url": "", "post_date": "08/05/2022 11:19:28", "content": "

Still 13G cpu Mem and 16G gpu Mem😄. It would be much better if we could infer 2-3 times faster and limit submission time to 4 or 3 hours. Saving much of our time.

", "votes": null, "replies": [ { "id": 1885796, "author_name": "crodoc", "author_url": "", "post_date": "08/05/2022 11:35:51", "content": "

I agree with that as well. But adding submission time seems trivial. And 0 cost.

", "votes": null, "replies": [] }, { "id": 1885841, "author_name": "goldenlock", "author_url": "", "post_date": "08/05/2022 12:03:08", "content": "

Totally agree with you, I do not undertand what leak will happen if show running time as we only have 5 submmisons each day and we can also get running time by manually watch progress.

", "votes": null, "replies": [] }, { "id": 1886007, "author_name": "crodoc", "author_url": "", "post_date": "08/05/2022 13:59:55", "content": "

Having submission time would make my kaggling experience so much better.

", "votes": null, "replies": [] } ] }, { "id": 1886059, "author_name": "happycube", "author_url": "", "post_date": "08/05/2022 14:42:15", "content": "

It could be gamed to get (limited) information from the private test set.

", "votes": null, "replies": [ { "id": 1886062, "author_name": "crodoc", "author_url": "", "post_date": "08/05/2022 14:43:43", "content": "

How? What is the difference of manually refreshing the submission page?

", "votes": null, "replies": [] }, { "id": 1886231, "author_name": "wcukierski", "author_url": "", "post_date": "08/05/2022 16:33:37", "content": "

I can confirm the reason that we don't show times is to limit their utility in automated/high-volume probing. There are a couple channels where information can leak out--error messages, errored vs. not, submission timing--so we try to strike a balance between providing some debugging information without allowing too much information exfiltration.

", "votes": null, "replies": [] }, { "id": 1888843, "author_name": "crodoc", "author_url": "", "post_date": "08/07/2022 19:55:47", "content": "

@wcukierski Is there any other way for us to get submission time without having to look at the submission page or refresh non-stop? I am spending a ton of time on this, instead of solving the problem.

", "votes": null, "replies": [] }, { "id": 1893649, "author_name": "rashmibanthia", "author_url": "", "post_date": "08/11/2022 01:01:50", "content": "

@crodoc Try this script - https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/201047
\nWorks well, I have used it in the past.

", "votes": null, "replies": [] }, { "id": 1894288, "author_name": "crodoc", "author_url": "", "post_date": "08/11/2022 11:34:00", "content": "

@wcukierski is using the script above allowed?

", "votes": null, "replies": [] }, { "id": 1896377, "author_name": "wcukierski", "author_url": "", "post_date": "08/12/2022 19:27:07", "content": "

@crodoc yes

", "votes": null, "replies": [] } ] }, { "id": 1893667, "author_name": "zacchaeus", "author_url": "", "post_date": "08/11/2022 01:34:10", "content": "

Information can be leaked using sleep

", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "1885670": "Is there any reason why Kaggle won't show us submission time? @argv\n\nI can't think of a good reason why this is the case. They are tracking this and it doesn't seem to be hard to add it. But, still after 12 years of Kaggle, I refresh the submission page and calculate submission time on my own.", "1885761": "Still 13G cpu Mem and 16G gpu Mem😄. It would be much better if we could infer 2-3 times faster and limit submission time to 4 or 3 hours. Saving much of our time.", "1885796": "I agree with that as well. But adding submission time seems trivial. And 0 cost.", "1885841": "Totally agree with you, I do not undertand what leak will happen if show running time as we only have 5 submmisons each day and we can also get running time by manually watch progress.", "1886007": "Having submission time would make my kaggling experience so much better.", "1886059": "It could be gamed to get (limited) information from the private test set.", "1886062": "How? What is the difference of manually refreshing the submission page?", "1886231": "I can confirm the reason that we don't show times is to limit their utility in automated/high-volume probing. There are a couple channels where information can leak out--error messages, errored vs. not, submission timing--so we try to strike a balance between providing some debugging information without allowing too much information exfiltration.", "1888843": "wcukierski Is there any other way for us to get submission time without having to look at the submission page or refresh non-stop? I am spending a ton of time on this, instead of solving the problem.", "1893649": "crodoc Try this script - https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/201047 \nWorks well, I have used it in the past.", "1893667": "Information can be leaked using `sleep`", "1894288": "wcukierski is using the script above allowed?", "1896377": "crodoc yes" }, "source": "meta" }