Refactor Testing Utils #19
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
magniloquency
force-pushed
the
refactor-testing-utils-2
branch
from
b1f4c32 to
1fe2940
Compare
magniloquency
force-pushed
the
add-uds-tests
branch
from
0058144 to
4a1cd49
Compare
magniloquency
force-pushed
the
refactor-testing-utils-2
branch
from
7b95608 to
3759861
Compare
magniloquency
force-pushed
the
add-uds-tests
branch
2 times, most recently
from
bafd75e to
04b3f37
Compare
* Rename python.h to compatibility.h Signed-off-by: gxu <[email protected]> * Bump Version Number Signed-off-by: gxu <[email protected]> --------- Signed-off-by: gxu <[email protected]>
* Initial Ray Compatibility * Add support for nested client fix ray test case, copy numpy array docs Pass all relevant arguments from ray.init to SchedulerClusterCombo feat: Improve Ray compatibility by supporting object reference passing feat: Improve Ray compatibility for function, add cancel, and tests docs: Add docstrings to all methods and classes in ray.py docs: Add module-level docstring to ray.py * Add new Ray test Fix mypy feat: Improve Ray compatibility layer and fix remote decorator usage feat: Add NotImplementedError for class decoration in ray.remote compatibility Introduces a check within the compatibility layer in to detect when a class is being decorated. Since the current Scaler compatibility layer does not support for classes, a is now raised in such cases, providing clearer feedback for unsupported usage. lint Fix: Address Ray compatibility issues and mypy error This commit resolves several issues in the Scaler Ray compatibility layer: - Prevents during Ray shutdown by patching and . These modules were attempting to decorate classes with , which is not yet supported by the Scaler compatibility layer, causing callbacks to fail. - Fixes a error in within the method. The function was causing to lose type information for objects. Explicitly casting to resolves this type-checking issue. feat(ray_compat): Improve type hints for map_unordered Introduced a new TypeVar 'V' and updated the signature of map_unordered to use 'RayRemote[[V], T]' and 'List[V]' for better type safety and clarity. feat(ray_compat): Add no-op patches for unsupported functions and test for ray.actor - Implemented no-op helper functions (_return_empty_dict, _return_empty_list). - Created NotImplementedMock for unsupported modules/functions to raise NotImplementedError. - Applied no-op patches to various unsupported ray functions and modules, including ray.actor. - Added a new test case (test_ray_actor_not_implemented) to verify that accessing ray.actor raises the expected NotImplementedError. docs(ray_compat): Add documentation for Ray compatibility layer - Created new documentation file: docs/source/tutorials/ray_compatibility.rst - Updated docs/source/index.rst to include the new documentation. - Clarified the import order of ray and scaler.compat.ray in the documentation. improve ray docs don't implicitly init on put, update docs Update docs update docs, add examples * add new example, fix wrapped fn signature remove dbg print delete test file fix ray test * Add more Ray examples, add support for num_returns to compatibility layer fix requirements for python 3.8 fix 3.8 fix type hint type hint update docs update docs for num_returns * Simplify function wrapping * move files * try using pytorch 2.5.1 * feat: Add skipped_tests.txt and integrate into CI/CD * bump version * simplify example skipping, rename file
Bumps [nicegui[plotly]](https://github.com/zauberzeug/nicegui) from 2.24.2 to 3.4.1. - [Release notes](https://github.com/zauberzeug/nicegui/releases) - [Changelog](https://github.com/zauberzeug/nicegui/blob/main/release.dockerfile) - [Commits](zauberzeug/nicegui@v2.24.2...v3.4.1) --- updated-dependencies: - dependency-name: nicegui[plotly] dependency-version: 3.4.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: sharpener6 <[email protected]>
* Update AsyncPriorityQueue to reduce complexity Signed-off-by: gxu <[email protected]> * Bump Version Number Signed-off-by: gxu <[email protected]> * Apply suggestions Signed-off-by: gxu <[email protected]> * Remove redundant AsyncSortedPriorityQueue - AsyncPriorityQueue implements the feature of AsyncSortedPriorityQueue Signed-off-by: gxu <[email protected]> --------- Signed-off-by: gxu <[email protected]>
Signed-off-by: gxu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.