Panic when importing parquet file

[Chuck321123]

Checks

• I have checked that this issue has not already been reported.
• I have confirmed this bug exists on the latest version of Polars.

Reproducible example

Log output

No response

Issue description

So I got this panic error, but I dont know how to replicate it. Would be nice if someone could find a fix to this.

Expected behavior

That it doesnt panic

Installed versions

--------Version info---------
Polars:               1.0.0-beta.1
Index type:           UInt32
Platform:             Linux-6.8.0-1005-raspi-aarch64-with-glibc2.39
Python:               3.12.3 | packaged by conda-forge | (main, Apr 15 2024, 18:17:49) [GCC 12.3.0]

----Optional dependencies----
adbc_driver_manager:  <not installed>
cloudpickle:          3.0.0
connectorx:           <not installed>
deltalake:            <not installed>
fastexcel:            <not installed>
fsspec:               <not installed>
gevent:               <not installed>
great_tables:         <not installed>
hvplot:               <not installed>
matplotlib:           3.9.0
nest_asyncio:         1.6.0
numpy:                1.26.4
openpyxl:             3.1.4
pandas:               2.2.2
pyarrow:              16.1.0
pydantic:             <not installed>
pyiceberg:            <not installed>
sqlalchemy:           <not installed>
torch:                <not installed>
xlsx2csv:             <not installed>
xlsxwriter:           <not installed>

[ritchie46]

Can you show the full backtrace with RUST_BACKTRACE=1 and share the parquet file?

[Chuck321123]

@ritchie46 I turned on rust backtrace from now on, but the file has updated while i was asleep and is now working. It consists of 1 row with a datetime column and several float32 columns in its working state. About 306 columns. I'll let you know if I'm able to replicate the error.

[Chuck321123]

@ritchie46 Put my read parquet function in a try-except loop before it failed. Here are some previous error messages:

[Chuck321123]

After updating to v1.0.0-rc.2 I haven't encountered this error again. I'll reopen the case if it happens again.