[Bug] confusing limit on library component count

[bradenmacdonald]

1. Improve error message when creating more than 1,000 components in a course. Currently it gives a generic error. It should say specifically that creating a component failed because the library has reached the maximum number of components supported.
2. Raise the limit in the platform from 1,000 to 100,000.

[bradenmacdonald]

@jmakowski1123 @ormsbee Please review this ticket.

[ormsbee]

@bradenmacdonald: How far do you think we could safely crank the limit on the search side of things? I'm tempted to just turn it up to 100K and see what happens. 😛

[bradenmacdonald]

@ormsbee I can't say from experience but I would hope it works fine even at 100K.

[pomegranited]

@jmakowski1123 @lizc577 @sdaitzman @marcotuts This is ready for AC testing on the sandbox

[ChrisChV]

@jmakowski1123 @lizc577 @sdaitzman @marcotuts Friendly reminder that this is ready for AC testing on the sandbox

[jmakowski1123]

Not sure how to test this? Is there a file with 100k components I could try to import?

[pomegranited]

Oh my apologies @jmakowski1123 , this is a hard one to test.

@bradenmacdonald is it worth taking a small amount of budget from the new project to create a huge library to test this issue, (and see how Meilisearch performs with the new limit)?

[bradenmacdonald]

@pomegranited I believe various people have already done that in the process of working on these issues - it should be relatively simple to paste a script into the console that mass-creates library blocks, and run that on the sandbox. In any case I agree it's a good idea to have a large library for testing on the sandbox.

[pomegranited]

I've got a script running to populate lib:OpenCraft:NL with 100,000 components -- will let you know when it's done.