Datasets:
Notifications from Datasets Server
The Datasets Server bot will post messages here about operations such as conversion to Parquet. There are some advantages associated with having a version of your dataset available in the Parquet format. You can learn more about these in the documentation.
Please comment below if you have any questions or feedback about this new notifications channel. Close the discussion if you want to stop receiving notifications.
Datasets Server has converted the dataset revision 6f3c08e to Parquet.
The Parquet files are published to the Hub in the refs/convert/parquet branch.
Datasets Server has converted the dataset revision 293f579 to Parquet.
The Parquet files are published to the Hub in the refs/convert/parquet branch.
Datasets Server has converted the dataset revision 4b007e7 to Parquet.
The Parquet files are published to the Hub in the refs/convert/parquet branch.
Datasets Server has converted the dataset revision b5b7a9d to Parquet.
The Parquet files are published to the Hub in the refs/convert/parquet branch.
Thanks for the comment. You can close this discussion to stop the notifications; would it work for you? BTW: is it related to the fact that this dataset is owned by an org? Happy to have more details (here or at https://github.com/huggingface/datasets-server/pull/1824)
Would it make sense to just update the original message to add the different revisions that have been converted? This way, you only receive one ping per repository. Here if I want this to continue to happen, I'm receiving pings on all my datasets which is a lot of notifications
Datasets Server has converted the dataset revision 768d9a9 to Parquet.
The Parquet files are published to the Hub in the refs/convert/parquet branch.
Here if I want this to continue to happen, I'm receiving pings on all my datasets which is a lot of notifications
As a mitigation, we have already limited the notifications to 1 per day per organization.
Would it make sense to just update the original message to add the different revisions that have been converted?
I'm not a fan of editing messages, but why not? Maybe the solution is to offer better control of the notifications on the Hub though.
Datasets Server has converted the dataset revision e192cfc to Parquet.
The Parquet files are published to the Hub in the refs/convert/parquet branch.
Datasets Server has converted the dataset revision eaa29e5 to Parquet.
The Parquet files are published to the Hub in the refs/convert/parquet branch.
I agree that editing original might be better. Translating this same situation to GitHub, I would not be happy with a bot that pings for every single commit. For example, the doc-builder bot does not write a comment for every commit in a PR, it just does a single comment and link will work. I don't think most users will want to get a new notification for every single commit. We can also not silence notifications at a repo level, so as a user i would be inclined to silence the whole org.
Datasets Server has converted the dataset revision e9d6b24 to Parquet.
The Parquet files are published to the Hub in the refs/convert/parquet branch.