You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there is empty string (i.e. "") in record field values, uploading records will raise an error httpx.RemoteProtocolError: peer closed connection without sending complete message body (incomplete chunked read), which I think is not helpful for locating the problem. Besides, it would be best if the system automatically processes the empty value for users (e.g. fill a "none").
Stacktrace and Code to create the bug
import argilla as rg
client = rg.Argilla(
api_url="<api_url>", api_key="<api_key>")
settings = rg.Settings(
guidelines="These are some guidelines.",
fields=[
rg.TextField(
name="text", title="text", use_markdown=True
),
],
questions=[
rg.LabelQuestion(
name="label",
labels=["label_1", "label_2", "label_3"]
),
],
metadata=[
rg.TermsMetadataProperty(
name="id",
)
]
)
dataset = rg.Dataset(
name="sample_dataset_0",
workspace="sft",
settings=settings,
)
dataset.create()
dataset = client.datasets(name="sample_dataset_0")
records = [
rg.Record(
fields={
"text": "",
},
metadata={"id": "0"},
),
rg.Record(
fields={
"text": "What is the boiling point of water?",
},
metadata={"id": "1"},
),
]
dataset.records.log(records)
Expected behavior
Display error message suggesting the empty value or process the empty value automatically.
Describe the bug
When there is empty string (i.e. "") in record field values, uploading records will raise an error
httpx.RemoteProtocolError: peer closed connection without sending complete message body (incomplete chunked read)
, which I think is not helpful for locating the problem. Besides, it would be best if the system automatically processes the empty value for users (e.g. fill a "none").Stacktrace and Code to create the bug
Expected behavior
Display error message suggesting the empty value or process the empty value automatically.
Environment:
The text was updated successfully, but these errors were encountered: