Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solution stopped working after reaching 5k items #4698

Closed
2 of 9 tasks
damianino1 opened this issue Feb 12, 2024 · 3 comments
Closed
2 of 9 tasks

Solution stopped working after reaching 5k items #4698

damianino1 opened this issue Feb 12, 2024 · 3 comments
Labels
status:wrong-repo Issue does not belong to this repository as it does not relate to a sample

Comments

@damianino1
Copy link

Disclaimer

Yes

Sample

Contributor(s)

@hugoabernier

What happened?

Solution stopped working after reaching 5k items. It is loads only but if I remove few comments from the list, it starts working again as long as 5k items will be not reached.

grafik

Steps to reproduce

  1. Arrive at 5k comments
  2. Webpart will stop working
  3. Delete few comments to be again below 5k of comments and you'll see it will work again as long as 5k will be not reached

Expected behavior

Working correctly even over 5k of comments

Target SharePoint environment

SharePoint Online

Developer environment

None

Browsers

  • Internet Explorer
  • Microsoft Edge
  • Google Chrome
  • FireFox
  • Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

What version of Node.js is currently installed on your workstation?

What version of Node.js is required by the sample?

--

Paste the results of SPFx doctor

Additional environment details

No response

@damianino1 damianino1 added the type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs label Feb 12, 2024
@ghost
Copy link

ghost commented Feb 12, 2024

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@ghost ghost added the Needs: Triage 🔍 label Feb 12, 2024
@hugoabernier hugoabernier added status:wrong-repo Issue does not belong to this repository as it does not relate to a sample and removed type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs Needs: Triage 🔍 labels Feb 12, 2024
Copy link

Thank you for your submission, but this issues list is intended only for issues related to the samples in this repository.

For general SPFx development issues, you may want to try to create issues in the SP-Dev-Docs repository

@damianino1
Copy link
Author

@hugoabernier it is not correct, as on my thread on the SP-Dev-Docs repository I was forwarded back to open it here. It is not an general SPFx issue but a sp-dev-fx related issue. Please reopen kindly my thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:wrong-repo Issue does not belong to this repository as it does not relate to a sample
Projects
None yet
Development

No branches or pull requests

2 participants