You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you expect to happen? What happened instead?
Currently, the page limit from org quotas is only set when a new workflow is created, but not when a workflow is edited.
Additionally, the crawl / workflow details pages report the overall cluster max pages, not the per org quotas, if any.
Reproduction instructions
Start a crawl in an org with quotas.
Observe the crawl and workflow details pages for the crawl.
Also:
Edit an existing workflow in an org with quotas.
Check the page limit set on the crawl.
Screenshots / Video
No response
Environment
No response
Additional details
Fix forthcoming. The fix is to set the page limit on the crawl when created, and when serializing the workflow, and not store it in the config.
In case the quota is later updated, it would apply to all existing workflows.
The text was updated successfully, but these errors were encountered:
- add ensure_page_limit_quotas() which sets the limit to the quota
- set the page limit when: creating new crawl, creating configmap, returning crawl workflow
- don't set the quota page limit on new or existing crawl workflows (remove setting it on new workflows) to allow updated quotas to take affect for next crawl
- fixes#2369
- add ensure_page_limit_quotas() which sets the limit to the quota
- set the page limit when: creating new crawl, creating configmap, returning crawl workflow
- don't set the quota page limit on new or existing crawl workflows (remove setting it on new workflows) to allow updated quotas to take affect for next crawl
- fixes#2369
Browsertrix Version
1.13.2
What did you expect to happen? What happened instead?
Currently, the page limit from org quotas is only set when a new workflow is created, but not when a workflow is edited.
Additionally, the crawl / workflow details pages report the overall cluster max pages, not the per org quotas, if any.
Reproduction instructions
Also:
Screenshots / Video
No response
Environment
No response
Additional details
Fix forthcoming. The fix is to set the page limit on the crawl when created, and when serializing the workflow, and not store it in the config.
In case the quota is later updated, it would apply to all existing workflows.
The text was updated successfully, but these errors were encountered: