Describe the Bug
When running the Ungoliant pipeline, everything proceeds smoothly initially as the JSONL files for each language are built. However, after a couple of hours, an error suddenly appears in the logs, and thereafter, only this error persists. I am curious as to why this occurs and whether it could be resolved by skipping the problematic inputs.
Describe the Bug When running the Ungoliant pipeline, everything proceeds smoothly initially as the JSONL files for each language are built. However, after a couple of hours, an error suddenly appears in the logs, and thereafter, only this error persists. I am curious as to why this occurs and whether it could be resolved by skipping the problematic inputs.
To Reproduce Nothing specific to mention, just the routine: downloading and pipelining.
Expected Behavior The expected behavior is for the pipeline to function as it did earlier or to skip the corrupt inputs.
Screenshots
at first:
later:
Desktop (Please Complete the Following Information):