Cannot read properties of undefined (reading 'length')

[alexmoraru25]

Describe the bug
For some grid instances either when loading the data or moving to the next page I get one of these errors:

• Cannot read properties of undefined (reading 'length')
• Cannot read properties of undefined (reading 'rows')

The data is there, loaded but the Previous/Next buttons are disabled and at the very bottom I get another message:
An error happened while fetching the data

What is more interesting is that sometime it works perfectly, but most of the time not.

Additional context
I am using the gridjs-angular component.
I have multiple gridjs-angular components in the same page.

I have tried the following:

• loading the static data and also using a Promise/timeout
• assigning column (and data) ids
• disabling the search feature seems to work (???) but we need it

[joeworkman]

I have this same issue. Were you able to find the root cause?

[joeworkman]

The expection is getting thrown inside of this for loop... inside pipline.ts

[joeworkman]

This occurs when prev is undefined when running await processor.process(prev). I sort of get lost in the weeds after that since I am not familiar enough with the code.

It looks as if the processor is for the pagination in my instance. This makes sense since my table gets built but the pagination is broken.

[OussamaKhoubran]

Any updates about this issue?

[tbasoft]

gridjs.umd.js:1 [Grid.js] [ERROR]: TypeError: Cannot read properties of undefined (reading 'length') i ahve same error

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[joeworkman]

I really hate the stale bot...

[joseba890]

I have the same intermittent issue. Behavior is exactly as described by joeworkman.

Have no idea how to remedy, but adding processingThrottleMs to the configuration and increasing the value from the default (100ms, if memory serves) does mitigate, but does not eliminate the issue.

However, the increase in the throttle rate causes rendering to slow down, unfortunately.

[nickgarver]

i also have this issue and the only solve is to disable pagination, which i need because of the table length. it seems it also doesnt throw this error if the data is loading extremely fast. all data is there, just the pages break