Closed imanjra closed 3 weeks ago
This update introduces several enhancements and refactors across multiple files. Key changes include the integration of a new clearSpaces
function in the MainSpace
component, the addition of a QueueItemStatus
enum for better status management in OperatorInvocationRequestExecutor
, and improved state handling in the spaces
package. Additionally, build configurations have been updated to include new MongoDB download links and artifact upload steps.
Files | Change Summary |
---|---|
.../MainSpace/MainSpace.tsx |
Modified useSpaces to include clearSpaces and added an useEffect hook to call clearSpaces on mount. |
.../OperatorInvocationRequestExecutor.tsx |
Added useMemo to filter requests by QueueItemStatus.Pending and updated rendering to use pendingRequests . |
.../constants.ts |
Added QueueItemStatus enum with Pending , Executing , Completed , and Failed values. |
.../operators.ts |
Moved QueueItemStatus enum to constants.ts and updated imports accordingly. |
.../spaces/src/hooks.ts |
Replaced useEffect with conditional state setting, added clearSpaces function using useCallback , and updated dependencies. |
.../spaces/src/state.ts |
Modified spacesAtom declaration to allow SpaceNodeJSON values to be undefined . |
.github/workflows/build-db.yml |
Added a new step to upload a wheel artifact if the platform is not 'sdist', with a specific name and path. |
package/db/setup.py |
Added MongoDB download links for CentOS 7, 8, 9, Debian 9, and Windows (amd64). Updated version to "1.1.3" and modified _get_download() function for Windows support. |
In code's vast and winding maze,
We clear the spaces, set ablaze,
With enums guiding status bright,
Pending, done, in day and night.
Mongo links for all to see,
Our build now flows with clarity.
🌟🚀
[!WARNING]
Review ran into problems
Problems (1)
* Git: Failed to clone repository. Please contact CodeRabbit support.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@imanjra @benjaminpkane confirmed that workspace persistence works when navigating between datasets via the dataset selector in the App (although I believe the real test bed is Teams here, not OSS).
Similar to https://github.com/voxel51/fiftyone/pull/4469#issuecomment-2156058282, I did notice that if I manually remove ?workspace=WORKSPACE
from the URL bar and press ENTER, the workspace is added back to the URL.
However, unlike for saved views, if I navigate from http://localhost:5151/datasets/DATASET1?workspace=WORKSPACE
directly to http://localhost:5151/datasets/DATASET2
, it does correctly load the second dataset without carrying over the workspace.
Similar to https://github.com/voxel51/fiftyone/pull/4469#issuecomment-2156058282, I did notice that if I manually remove ?workspace=WORKSPACE from the URL bar and press ENTER, the workspace is added back to the URL.
This is intentional for both workspaces and saved views to recover app state based on the current session state. However, changing the workspace/view param in URL to some other workspace/view should trigger session to update along with the app.
Updated the base to merge/v0.24.1-to-main
What changes are proposed in this pull request?
Fixes some issues with loading and using workspaces in the app
How is this patch tested? If it is not, please explain why.
Using app and session
Release Notes
Is this a user-facing change that should be mentioned in the release notes?
See above
What areas of FiftyOne does this PR affect?
fiftyone
Python library changesSummary by CodeRabbit
New Features
Bug Fixes
Chores
QueueItemStatus
enum to a separate file.Refactor