Adding Microsoft CodeXGlue Datasets
NONE
Oh one other thing. Mentioned in the PR was that I would need to regenerate the dataset_infos.json once the camel casing was done. However, I am unsure why this is the case since there is no reference to any object names in the dataset_infos.json file.

If it needs to be reran, I can try it do it on my own machine, but I've had a memory issues with a previous dataset due to my compute constraints so I'd prefer to hopefully avoid it all together if not necessary to regenerate.
2021-05-13T00:45:56Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-840199357
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg0MDE5OTM1Nw==
https://api.github.com/repos/huggingface/datasets/issues/comments/840199357/reactions
2021-05-13T00:45:56Z
https://api.github.com/repos/huggingface/datasets/issues/comments/840199357
https://avatars.githubusercontent.com/u/7613470?v=4
https://api.github.com/users/ncoop57/events{/privacy}
https://api.github.com/users/ncoop57/followers
https://api.github.com/users/ncoop57/following{/other_user}
https://api.github.com/users/ncoop57/gists{/gist_id}
https://github.com/ncoop57
ncoop57
MDQ6VXNlcjc2MTM0NzA=
https://api.github.com/users/ncoop57/orgs
https://api.github.com/users/ncoop57/received_events
https://api.github.com/users/ncoop57/repos
https://api.github.com/users/ncoop57/starred{/owner}{/repo}
https://api.github.com/users/ncoop57/subscriptions
User
https://api.github.com/users/ncoop57
public
NONE
Was just reviewing the `builder_name`s of each dataset and it seems like it is already following this format:

`CodeXGlueCcCloneDetectionBigCloneBenchMain -> code_x_glue_cc_clone_detection_big_clone_bench_main` Is there a location I am missing?
2021-05-14T18:48:33Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-841434371
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg0MTQzNDM3MQ==
https://api.github.com/repos/huggingface/datasets/issues/comments/841434371/reactions
2021-05-14T18:48:33Z
https://api.github.com/repos/huggingface/datasets/issues/comments/841434371
https://avatars.githubusercontent.com/u/7613470?v=4
https://api.github.com/users/ncoop57/events{/privacy}
https://api.github.com/users/ncoop57/followers
https://api.github.com/users/ncoop57/following{/other_user}
https://api.github.com/users/ncoop57/gists{/gist_id}
https://github.com/ncoop57
ncoop57
MDQ6VXNlcjc2MTM0NzA=
https://api.github.com/users/ncoop57/orgs
https://api.github.com/users/ncoop57/received_events
https://api.github.com/users/ncoop57/repos
https://api.github.com/users/ncoop57/starred{/owner}{/repo}
https://api.github.com/users/ncoop57/subscriptions
User
https://api.github.com/users/ncoop57
public
MEMBER
> Was just reviewing the `builder_name`s of each dataset and it seems like it is already following this format:
> 
> `CodeXGlueCcCloneDetectionBigCloneBenchMain -> code_x_glue_cc_clone_detection_big_clone_bench_main` Is there a location I am missing?

If it's already in this format then it's fine thanks ! It's all good then

To fix the CI you just need to add the `encoding=` parameters to the `open()` calls
2021-05-17T13:45:28Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-842337313
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg0MjMzNzMxMw==
https://api.github.com/repos/huggingface/datasets/issues/comments/842337313/reactions
2021-05-17T13:45:28Z
https://api.github.com/repos/huggingface/datasets/issues/comments/842337313
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
NONE
@lhoestq I think everything should be good to go besides the code styling, which seem to be due to missing or unsupported metadata tags for the READMEs, is this something I should worry about since all the other datasets seem to be failing as well?
2021-05-18T00:16:56Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-842728052
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg0MjcyODA1Mg==
https://api.github.com/repos/huggingface/datasets/issues/comments/842728052/reactions
2021-05-18T00:16:56Z
https://api.github.com/repos/huggingface/datasets/issues/comments/842728052
https://avatars.githubusercontent.com/u/7613470?v=4
https://api.github.com/users/ncoop57/events{/privacy}
https://api.github.com/users/ncoop57/followers
https://api.github.com/users/ncoop57/following{/other_user}
https://api.github.com/users/ncoop57/gists{/gist_id}
https://github.com/ncoop57
ncoop57
MDQ6VXNlcjc2MTM0NzA=
https://api.github.com/users/ncoop57/orgs
https://api.github.com/users/ncoop57/received_events
https://api.github.com/users/ncoop57/repos
https://api.github.com/users/ncoop57/starred{/owner}{/repo}
https://api.github.com/users/ncoop57/subscriptions
User
https://api.github.com/users/ncoop57
public
NONE
Awesome! Just committed your changes and I will begin on adding the TOCs and filling in the content for the new sections/subsections.

Also, I see that we are having to only use the `code` tag instead of individual langs and I get that is required for indexing or showing available tags on the datasets hub. However, as a future feature, it might be good to add tags for individual programming languages to make it easier to search.
2021-05-27T14:59:26Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-849706884
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg0OTcwNjg4NA==
https://api.github.com/repos/huggingface/datasets/issues/comments/849706884/reactions
2021-05-27T14:59:26Z
https://api.github.com/repos/huggingface/datasets/issues/comments/849706884
https://avatars.githubusercontent.com/u/7613470?v=4
https://api.github.com/users/ncoop57/events{/privacy}
https://api.github.com/users/ncoop57/followers
https://api.github.com/users/ncoop57/following{/other_user}
https://api.github.com/users/ncoop57/gists{/gist_id}
https://github.com/ncoop57
ncoop57
MDQ6VXNlcjc2MTM0NzA=
https://api.github.com/users/ncoop57/orgs
https://api.github.com/users/ncoop57/received_events
https://api.github.com/users/ncoop57/repos
https://api.github.com/users/ncoop57/starred{/owner}{/repo}
https://api.github.com/users/ncoop57/subscriptions
User
https://api.github.com/users/ncoop57
public
MEMBER
> Also, I see that we are having to only use the code tag instead of individual langs and I get that is required for indexing or showing available tags on the datasets hub. However, as a future feature, it might be good to add tags for individual programming languages to make it easier to search.

Yes I agree. We'll be able to reuse the tags per programming language from this PR when we allow this feature

cc @yjernite what do you think about extending our languages taxonomy to programming languages ?
2021-05-28T15:06:07Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-850484201
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1MDQ4NDIwMQ==
https://api.github.com/repos/huggingface/datasets/issues/comments/850484201/reactions
2021-05-28T15:06:07Z
https://api.github.com/repos/huggingface/datasets/issues/comments/850484201
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
NONE
Hey @lhoestq, just finalizing the READMEs and testing them against the automated test. For the non, WIN tests, it seems like there is some dependency issue that doesn't have to do with the new datasets. For the WIN tests, it looks like some of the headings are mislabeled such as "Supported Tasks and Leaderboards" -> "Supported Tasks" in the TOC you posted. Should I base my TOC on the one you posted or on the one that the test script is using? Also, it throws errors for some of the fields being empty, such as "Source Data" in the `code_x_glue_tt_text_to_text` dataset. However, I am not familiar with this dataset, so I put the `[More Information Needed]` stub, similar to the other sections I couldn't easily answer. For some of the sections like "Source Data", is this info required?
2021-05-30T22:36:03Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-851071696
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1MTA3MTY5Ng==
https://api.github.com/repos/huggingface/datasets/issues/comments/851071696/reactions
2021-05-30T22:36:03Z
https://api.github.com/repos/huggingface/datasets/issues/comments/851071696
https://avatars.githubusercontent.com/u/7613470?v=4
https://api.github.com/users/ncoop57/events{/privacy}
https://api.github.com/users/ncoop57/followers
https://api.github.com/users/ncoop57/following{/other_user}
https://api.github.com/users/ncoop57/gists{/gist_id}
https://github.com/ncoop57
ncoop57
MDQ6VXNlcjc2MTM0NzA=
https://api.github.com/users/ncoop57/orgs
https://api.github.com/users/ncoop57/received_events
https://api.github.com/users/ncoop57/repos
https://api.github.com/users/ncoop57/starred{/owner}{/repo}
https://api.github.com/users/ncoop57/subscriptions
User
https://api.github.com/users/ncoop57
public
MEMBER
Yes you're right, it is `Supported Tasks and Leaderboards` that we need to use, sorry about that

I also noticed the same for the splits section: we have to use `Data Splits` (not Data Splits Sample Size)

2021-05-31T09:44:52Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-851367109
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1MTM2NzEwOQ==
https://api.github.com/repos/huggingface/datasets/issues/comments/851367109/reactions
2021-05-31T09:52:58Z
https://api.github.com/repos/huggingface/datasets/issues/comments/851367109
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
MEMBER
Some subsections are also missing: `Initial Data Collection and Normalization`, `Who are the source language producers?`.
If you are interested you can fill those sections as well, or leave them empty for now.
This will also fix the error regarding "Source Data"

You can see the template of the readme here:
https://github.com/huggingface/datasets/blob/9d8bf36fdb861d9b2922d7c782fb58f9f542997c/templates/README.md
2021-05-31T09:57:53Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-851374796
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1MTM3NDc5Ng==
https://api.github.com/repos/huggingface/datasets/issues/comments/851374796/reactions
2021-05-31T09:58:53Z
https://api.github.com/repos/huggingface/datasets/issues/comments/851374796
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
MEMBER
> > Also, I see that we are having to only use the code tag instead of individual langs and I get that is required for indexing or showing available tags on the datasets hub. However, as a future feature, it might be good to add tags for individual programming languages to make it easier to search.
> 
> Yes I agree. We'll be able to reuse the tags per programming language from this PR when we allow this feature
> 
> cc @yjernite what do you think about extending our languages taxonomy to programming languages ?

Sounds good, as long as they all share a prefix! maybe `code_cpp`, `code_java`, etc. ? 

I don't think we currently have `_` in language codes/names, but also don't see what it would break *a priori*
2021-06-01T13:48:44Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-852139907
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1MjEzOTkwNw==
https://api.github.com/repos/huggingface/datasets/issues/comments/852139907/reactions
2021-06-01T13:48:44Z
https://api.github.com/repos/huggingface/datasets/issues/comments/852139907
https://avatars.githubusercontent.com/u/10469459?v=4
https://api.github.com/users/yjernite/events{/privacy}
https://api.github.com/users/yjernite/followers
https://api.github.com/users/yjernite/following{/other_user}
https://api.github.com/users/yjernite/gists{/gist_id}
https://github.com/yjernite
yjernite
MDQ6VXNlcjEwNDY5NDU5
https://api.github.com/users/yjernite/orgs
https://api.github.com/users/yjernite/received_events
https://api.github.com/users/yjernite/repos
https://api.github.com/users/yjernite/starred{/owner}{/repo}
https://api.github.com/users/yjernite/subscriptions
User
https://api.github.com/users/yjernite
public
MEMBER
We don't use `_` but there are some languages that use `-` though like `en-US`. Let's use `-` maybe, to match the same hierarchy pattern ?
2021-06-01T15:57:31Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-852240896
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1MjI0MDg5Ng==
https://api.github.com/repos/huggingface/datasets/issues/comments/852240896/reactions
2021-06-01T15:57:31Z
https://api.github.com/repos/huggingface/datasets/issues/comments/852240896
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
CONTRIBUTOR
Hi guys, I just started working on https://github.com/huggingface/datasets/pull/997 this morning and I just realized that you were finishing it... You may want to get the dataset cards from https://github.com/madlag/datasets, and maybe some code too, as I did a few things like moving _CITATION and _DESCRIPTION to globals.


2021-06-04T16:42:21Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-854865981
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1NDg2NTk4MQ==
https://api.github.com/repos/huggingface/datasets/issues/comments/854865981/reactions
2021-06-04T16:42:21Z
https://api.github.com/repos/huggingface/datasets/issues/comments/854865981
https://avatars.githubusercontent.com/u/272253?v=4
https://api.github.com/users/madlag/events{/privacy}
https://api.github.com/users/madlag/followers
https://api.github.com/users/madlag/following{/other_user}
https://api.github.com/users/madlag/gists{/gist_id}
https://github.com/madlag
madlag
MDQ6VXNlcjI3MjI1Mw==
https://api.github.com/users/madlag/orgs
https://api.github.com/users/madlag/received_events
https://api.github.com/users/madlag/repos
https://api.github.com/users/madlag/starred{/owner}{/repo}
https://api.github.com/users/madlag/subscriptions
User
https://api.github.com/users/madlag
public
CONTRIBUTOR
I am renaming the main classes to match the dataset names, for example : CodeXGlueTcTextToCodeMain -> CodeXGlueTcTextToCode . And I am regenerating the dataset_infos.json accordingly.
2021-06-07T10:06:09Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-855794801
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1NTc5NDgwMQ==
https://api.github.com/repos/huggingface/datasets/issues/comments/855794801/reactions
2021-06-07T10:06:09Z
https://api.github.com/repos/huggingface/datasets/issues/comments/855794801
https://avatars.githubusercontent.com/u/272253?v=4
https://api.github.com/users/madlag/events{/privacy}
https://api.github.com/users/madlag/followers
https://api.github.com/users/madlag/following{/other_user}
https://api.github.com/users/madlag/gists{/gist_id}
https://github.com/madlag
madlag
MDQ6VXNlcjI3MjI1Mw==
https://api.github.com/users/madlag/orgs
https://api.github.com/users/madlag/received_events
https://api.github.com/users/madlag/repos
https://api.github.com/users/madlag/starred{/owner}{/repo}
https://api.github.com/users/madlag/subscriptions
User
https://api.github.com/users/madlag
public
MEMBER
Thanks for renaming the classes and updating the dataset_infos.json ! This looks all clean now :)

This PR looks all good to me :) One just needs to merge master into this branch to make sure the CI is green with the latest changes. It should also fix the current CI issues that are not related to this PR
2021-06-07T16:44:00Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-856095252
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1NjA5NTI1Mg==
https://api.github.com/repos/huggingface/datasets/issues/comments/856095252/reactions
2021-06-07T16:44:00Z
https://api.github.com/repos/huggingface/datasets/issues/comments/856095252
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
NONE
Woot woot :rocket:! All green, looks like it is ready for showtime. Thank you both @lhoestq and especially @madlag, I think these datasets are going to be a great new addition to :hugs: datasets and I can't wait to use them in my research :nerd_face:.
2021-06-08T00:35:46Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-856352446
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1NjM1MjQ0Ng==
https://api.github.com/repos/huggingface/datasets/issues/comments/856352446/reactions
2021-06-08T00:36:37Z
https://api.github.com/repos/huggingface/datasets/issues/comments/856352446
https://avatars.githubusercontent.com/u/7613470?v=4
https://api.github.com/users/ncoop57/events{/privacy}
https://api.github.com/users/ncoop57/followers
https://api.github.com/users/ncoop57/following{/other_user}
https://api.github.com/users/ncoop57/gists{/gist_id}
https://github.com/ncoop57
ncoop57
MDQ6VXNlcjc2MTM0NzA=
https://api.github.com/users/ncoop57/orgs
https://api.github.com/users/ncoop57/received_events
https://api.github.com/users/ncoop57/repos
https://api.github.com/users/ncoop57/starred{/owner}{/repo}
https://api.github.com/users/ncoop57/subscriptions
User
https://api.github.com/users/ncoop57
public
CONTRIBUTOR
Thanks @ncoop57 for you contribution! It will be really cool to see those datasets used as soon as they are released !
2021-06-08T09:23:18Z
https://github.com/huggingface/datasets/pull/2357#issuecomment-856609931
https://api.github.com/repos/huggingface/datasets/issues/2357
MDEyOklzc3VlQ29tbWVudDg1NjYwOTkzMQ==
https://api.github.com/repos/huggingface/datasets/issues/comments/856609931/reactions
2021-06-08T09:23:18Z
https://api.github.com/repos/huggingface/datasets/issues/comments/856609931
https://avatars.githubusercontent.com/u/272253?v=4
https://api.github.com/users/madlag/events{/privacy}
https://api.github.com/users/madlag/followers
https://api.github.com/users/madlag/following{/other_user}
https://api.github.com/users/madlag/gists{/gist_id}
https://github.com/madlag
madlag
MDQ6VXNlcjI3MjI1Mw==
https://api.github.com/users/madlag/orgs
https://api.github.com/users/madlag/received_events
https://api.github.com/users/madlag/repos
https://api.github.com/users/madlag/starred{/owner}{/repo}
https://api.github.com/users/madlag/subscriptions
User
https://api.github.com/users/madlag
public
Hi there, this is a new pull request to get the CodeXGlue datasets into the awesome HF datasets lib. Most of the work has been done in this PR #997 by the awesome @madlag. However, that PR has been stale for a while now and so I spoke with @lhoestq about finishing up the final mile and so he told me to open a new PR with the final changes :smile:. 

I believe I've met all of the changes still left in the old PR to do, except for the change to the languages. I believe the READMEs should include the different programming languages used rather than just using the tag "code" as when searching for datasets, SE researchers may specifically be looking only for what type of programming language and so being able to quickly filter will be very valuable. Let me know what you think of that or if you still believe it should be the "code" tag @lhoestq.