html_url stringlengths 51 51 | title stringlengths 9 280 | comments stringlengths 63 24.7k | body stringlengths 51 58.6k | comments length int64 16 1.45k | text stringlengths 186 59.1k | embeddings listlengths 768 768 |
|---|---|---|---|---|---|---|
https://github.com/huggingface/datasets/issues/7214 | Formatted map + with_format(None) changes array dtype for iterable datasets | possibly due to this logic:
```python
def _arrow_array_to_numpy(self, pa_array: pa.Array) -> np.ndarray:
if isinstance(pa_array, pa.ChunkedArray):
if isinstance(pa_array.type, _ArrayXDExtensionType):
# don't call to_pylist() to preserve dtype of the fixed-size array
... | ### Describe the bug
When applying with_format -> map -> with_format(None), array dtypes seem to change, even if features are passed
### Steps to reproduce the bug
```python
features=Features(**{"array0": Array3D((None, 10, 10), dtype="float32")})
dataset = Dataset.from_dict({f"array0": [np.zeros((100,10,10... | 109 | Formatted map + with_format(None) changes array dtype for iterable datasets
### Describe the bug
When applying with_format -> map -> with_format(None), array dtypes seem to change, even if features are passed
### Steps to reproduce the bug
```python
features=Features(**{"array0": Array3D((None, 10, 10), dtyp... | [
0.0981326475739479,
-0.4397047460079193,
-0.04067501425743103,
0.07035092264413834,
0.46244239807128906,
-0.06503685563802719,
0.5293607115745544,
0.31564098596572876,
-0.038491833955049515,
-0.021876713261008263,
-0.07091649621725082,
0.7443006634712219,
-0.062373194843530655,
0.084774173... |
https://github.com/huggingface/datasets/issues/5012 | Force JSON format regardless of file naming on S3 | Hi ! Support for URIs like `s3://...` is not implemented yet in `data_files=`. You can use the HTTP URL instead if your data is public in the meantime | I have a file on S3 created by Data Version Control, it looks like `s3://dvc/ac/badff5b134382a0f25248f1b45d7b2` but contains a json file. If I run
```python
dataset = load_dataset(
"json",
data_files='s3://dvc/ac/badff5b134382a0f25248f1b45d7b2'
)
```
It gives me
```
InvalidSchema: No connection adap... | 28 | Force JSON format regardless of file naming on S3
I have a file on S3 created by Data Version Control, it looks like `s3://dvc/ac/badff5b134382a0f25248f1b45d7b2` but contains a json file. If I run
```python
dataset = load_dataset(
"json",
data_files='s3://dvc/ac/badff5b134382a0f25248f1b45d7b2'
)
```
It... | [
0.2356240600347519,
-0.03260774910449982,
0.013763888739049435,
-0.013254550285637379,
0.17930810153484344,
-0.17578455805778503,
0.1975647509098053,
0.2532143294811249,
0.08307377994060516,
0.07370838522911072,
-0.01387035008519888,
0.5979510545730591,
-0.2102200835943222,
0.4327723383903... |
https://github.com/huggingface/datasets/issues/5012 | Force JSON format regardless of file naming on S3 | Hi,
I want to make sure I understand this response. I have a set of files on S3 that are private for security reasons. Because they are not public files I cannot read those files (many are parquet) into my hf notebooks in Kaggle? That can't be correct, can it? | I have a file on S3 created by Data Version Control, it looks like `s3://dvc/ac/badff5b134382a0f25248f1b45d7b2` but contains a json file. If I run
```python
dataset = load_dataset(
"json",
data_files='s3://dvc/ac/badff5b134382a0f25248f1b45d7b2'
)
```
It gives me
```
InvalidSchema: No connection adap... | 50 | Force JSON format regardless of file naming on S3
I have a file on S3 created by Data Version Control, it looks like `s3://dvc/ac/badff5b134382a0f25248f1b45d7b2` but contains a json file. If I run
```python
dataset = load_dataset(
"json",
data_files='s3://dvc/ac/badff5b134382a0f25248f1b45d7b2'
)
```
It... | [
0.37514787912368774,
-0.22132404148578644,
0.04070267453789711,
0.038499511778354645,
0.09746859967708588,
-0.1697310209274292,
0.2889716625213623,
0.15318523347377777,
0.16126878559589386,
0.06703722476959229,
-0.12092676758766174,
0.6312375664710999,
-0.10404203087091446,
0.5032793879508... |
https://github.com/huggingface/datasets/issues/5012 | Force JSON format regardless of file naming on S3 | Hi ! There is a discussion at https://github.com/huggingface/datasets/issues/5281
Using the latest `datasets` 2.11 you can try passing fsspec URLs to private buckets to `data_files` in `load_dataset()`. Though this is still experimental and undocumented, so feedback is welcome. You may not have the best experience t... | I have a file on S3 created by Data Version Control, it looks like `s3://dvc/ac/badff5b134382a0f25248f1b45d7b2` but contains a json file. If I run
```python
dataset = load_dataset(
"json",
data_files='s3://dvc/ac/badff5b134382a0f25248f1b45d7b2'
)
```
It gives me
```
InvalidSchema: No connection adap... | 57 | Force JSON format regardless of file naming on S3
I have a file on S3 created by Data Version Control, it looks like `s3://dvc/ac/badff5b134382a0f25248f1b45d7b2` but contains a json file. If I run
```python
dataset = load_dataset(
"json",
data_files='s3://dvc/ac/badff5b134382a0f25248f1b45d7b2'
)
```
It... | [
0.172310933470726,
0.02975805290043354,
0.04746237024664879,
0.03164856880903244,
0.1887907087802887,
-0.14227062463760376,
0.2048283815383911,
0.19066572189331055,
0.11577461659908295,
0.06750994920730591,
-0.046311378479003906,
0.5999645590782166,
-0.159758523106575,
0.5780045390129089,
... |
https://github.com/huggingface/datasets/issues/6824 | Winogrande does not seem to be compatible with datasets version of 1.18.0 | Hi ! Do you mean 2.18 ? Can you try to update `fsspec` and `huggingface_hub` ?
```
pip install -U fsspec huggingface_hub
``` | ### Describe the bug
I get the following error when simply running `load_dataset('winogrande','winogrande_xl')`.
I do not have such an issue in the 1.17.0 version.
```Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python3.10/dist-packages/datasets/load.py", line... | 23 | Winogrande does not seem to be compatible with datasets version of 1.18.0
### Describe the bug
I get the following error when simply running `load_dataset('winogrande','winogrande_xl')`.
I do not have such an issue in the 1.17.0 version.
```Traceback (most recent call last):
File "<stdin>", line 1, in <module... | [
-0.7672982811927795,
0.122221440076828,
0.05378489941358566,
0.08904314786195755,
0.1577230840921402,
0.1300620138645172,
0.45174574851989746,
0.3389912545681,
-0.04396594688296318,
0.04765084758400917,
0.1569659560918808,
0.504392147064209,
-0.08829980343580246,
0.14867417514324188,
-0.... |
https://github.com/huggingface/datasets/issues/5950 | Support for data with instance-wise dictionary as features | Hi ! We use the Arrow columnar format under the hood, which doesn't support such dictionaries: each field must have a fixed type and exist in each sample.
Instead you can restructure your data like
```
{
"index": 0,
"keys": ["2 * x + y >= 3"],
"values": [["2 * x + y >= 3", "4 * x + 2 * y >= 6"]],
... | ### Feature request
I notice that when loading data instances with feature type of python dictionary, the dictionary keys would be broadcast so that every instance has the same set of keys. Please see an example in the Motivation section.
It is possible to avoid this behavior, i.e., load dictionary features as it i... | 87 | Support for data with instance-wise dictionary as features
### Feature request
I notice that when loading data instances with feature type of python dictionary, the dictionary keys would be broadcast so that every instance has the same set of keys. Please see an example in the Motivation section.
It is possible to ... | [
0.19504183530807495,
-0.34095364809036255,
0.0024531828239560127,
0.2926228940486908,
0.2256862372159958,
-0.06849905848503113,
0.2951245605945587,
0.02916012331843376,
0.14267385005950928,
0.20322425663471222,
0.2179425060749054,
0.4819653034210205,
-0.38490477204322815,
0.755951702594757... |
https://github.com/huggingface/datasets/issues/5950 | Support for data with instance-wise dictionary as features | Maybe there could be some type of automated conversion from dicts to tuples. I am also trying to wrangle a json-based dataset into `datasets` and it's awful because of this issue. | ### Feature request
I notice that when loading data instances with feature type of python dictionary, the dictionary keys would be broadcast so that every instance has the same set of keys. Please see an example in the Motivation section.
It is possible to avoid this behavior, i.e., load dictionary features as it i... | 31 | Support for data with instance-wise dictionary as features
### Feature request
I notice that when loading data instances with feature type of python dictionary, the dictionary keys would be broadcast so that every instance has the same set of keys. Please see an example in the Motivation section.
It is possible to ... | [
0.19504183530807495,
-0.34095364809036255,
0.0024531828239560127,
0.2926228940486908,
0.2256862372159958,
-0.06849905848503113,
0.2951245605945587,
0.02916012331843376,
0.14267385005950928,
0.20322425663471222,
0.2179425060749054,
0.4819653034210205,
-0.38490477204322815,
0.755951702594757... |
https://github.com/huggingface/datasets/issues/5950 | Support for data with instance-wise dictionary as features | Alternatively we can maybe support the [Json extension type](https://arrow.apache.org/docs/python/generated/pyarrow.JsonType.html#pyarrow.JsonType) in `pyarrow` ?
btw `datasets` is open to contributions on this subject if you'd like to take a look | ### Feature request
I notice that when loading data instances with feature type of python dictionary, the dictionary keys would be broadcast so that every instance has the same set of keys. Please see an example in the Motivation section.
It is possible to avoid this behavior, i.e., load dictionary features as it i... | 28 | Support for data with instance-wise dictionary as features
### Feature request
I notice that when loading data instances with feature type of python dictionary, the dictionary keys would be broadcast so that every instance has the same set of keys. Please see an example in the Motivation section.
It is possible to ... | [
0.19504183530807495,
-0.34095364809036255,
0.0024531828239560127,
0.2926228940486908,
0.2256862372159958,
-0.06849905848503113,
0.2951245605945587,
0.02916012331843376,
0.14267385005950928,
0.20322425663471222,
0.2179425060749054,
0.4819653034210205,
-0.38490477204322815,
0.755951702594757... |
https://github.com/huggingface/datasets/issues/5950 | Support for data with instance-wise dictionary as features | Hmm, I'll think about this a bit.
https://arrow.apache.org/docs/python/json.html
> Nested JSON objects convert to a struct type, and inference proceeds recursively on the JSON objects’ values.
https://arrow.apache.org/docs/dev/python/generated/pyarrow.JsonType.html
Hmm... AFAICT from reading the docs, the `JsonType... | ### Feature request
I notice that when loading data instances with feature type of python dictionary, the dictionary keys would be broadcast so that every instance has the same set of keys. Please see an example in the Motivation section.
It is possible to avoid this behavior, i.e., load dictionary features as it i... | 171 | Support for data with instance-wise dictionary as features
### Feature request
I notice that when loading data instances with feature type of python dictionary, the dictionary keys would be broadcast so that every instance has the same set of keys. Please see an example in the Motivation section.
It is possible to ... | [
0.19504183530807495,
-0.34095364809036255,
0.0024531828239560127,
0.2926228940486908,
0.2256862372159958,
-0.06849905848503113,
0.2951245605945587,
0.02916012331843376,
0.14267385005950928,
0.20322425663471222,
0.2179425060749054,
0.4819653034210205,
-0.38490477204322815,
0.755951702594757... |
https://github.com/huggingface/datasets/issues/5950 | Support for data with instance-wise dictionary as features | "The first option sounds good indeed, and more explicit / flexible.\n\n> but also would remove the n(...TRUNCATED) | "### Feature request\n\nI notice that when loading data instances with feature type of python dictio(...TRUNCATED) | 66 | "Support for data with instance-wise dictionary as features\n### Feature request\n\nI notice that wh(...TRUNCATED) | [0.19504183530807495,-0.34095364809036255,0.0024531828239560127,0.2926228940486908,0.225686237215995(...TRUNCATED) |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 32