Read 16384 columns instead of actual columns

[rockingdice]

Read the xlsx file, the actual columns are 19, but it reads 16384 columns instead, which make the server hang.

Steps to reproduce the issue:

1. read the xlsx file provided
2. debug inside the GetCols function
3. check the cols:

Describe the results you received:
16384 cols

Describe the results you expected:
19 cols or similar results

Output of go version:

1.18.10

Excelize version or commit ID:

2.8.0

Environment details (OS, Microsoft Excel™ version, physical, etc.):
MacOS/Centos 7

[rockingdice]

ct_new_buff.xlsx

the xlsx file that have the issue.

[xuri]

Thanks for your issue. There are 16384 columns in the worksheet "ct_new_buff", even though the cells right of column "S" seem blank, these cells have custom styles event it, there's cell was not empty, as the documentation of the Excelize library says, only the continually blank cells in the tail of each row will be skipped, so these cells can not be skipped, you can also confirm this by open the workbook by Excel application, the length of the horizontal scroll bar is different between "ct_new_buff" and "Sheet1" in your workbook. So the conduct is expected. I've closed this issue. If you have any questions, please let me know, and you can reopen this anytime.

[rockingdice]

Thanks for your issue. There are 16384 columns in the worksheet "ct_new_buff", even though the cells right of column "S" seem blank, these cells have custom styles event it, there's cell was not empty, as the documentation of the Excelize library says, only the continually blank cells in the tail of each row will be skipped, so these cells can not be skipped, you can also confirm this by open the workbook by Excel application, the length of the horizontal scroll bar is different between "ct_new_buff" and "Sheet1" in your workbook. So the conduct is expected. I've closed this issue. If you have any questions, please let me know, and you can reopen this anytime.

Thank you for your explanation.