-
Notifications
You must be signed in to change notification settings - Fork 160
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
job-history query returns all jobs regardless of page or page_size parameter #354
Comments
paginate dynamically is supported only if it is started with the |
Thanks! Will try it out! |
Using "--persistent" as a flag removes all history from being displayed:
There should be jobs listed in this history JSON array. |
Recommend new project FooocusAPI to you |
remove all? I cannot understand it. I started the server with the "--persistent" but no records in database.db |
Yes, I have reviewed some code, but not all of it. I found some bugs when saving records to the database. I am trying to fix it. Maybe will open one issue/pr later. |
Hello! Loving this API!! I'm building a quick application to support some of my workflows, and I started running into issues when trying to manage the job history endpoint. No matter what I send to it - it returns all jobs. So that:
http://ai01.tylephony.com:8888/v1/generation/job-history?page=1&page_size=2
Still returns:
I was hoping that by sending different pages and page sizes, I could paginate dynamically, but it looks like I'll need to handle the full list myself. Do you know if this is a bug?
Running the latest release, v0.4.0.6, on Windows.
The text was updated successfully, but these errors were encountered: