-
Notifications
You must be signed in to change notification settings - Fork 5
feat: subchunk write order #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
Open
ilan-gold
wants to merge
9
commits into
main
Choose a base branch
from
ig/subchunk_write_order
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
5ef4b1b
feat: subchunk write order
ilan-gold 746f39c
chore: test
ilan-gold 2a59fc5
chore: deprecated calls
ilan-gold 28cce28
fix: not unreachable
ilan-gold 037db6e
Update README.md
ilan-gold 1338e49
fmt
flying-sheep 46506a5
chore: explanation in readme
ilan-gold 0ff7867
clippy
flying-sheep 4dad7bb
fix type
flying-sheep File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,10 @@ | ||
| use std::fmt::Display; | ||
|
|
||
| use pyo3::{PyErr, PyResult, PyTypeInfo}; | ||
| use zarrs::array::CodecError; | ||
| use pyo3::{ | ||
| Borrowed, Bound, FromPyObject, IntoPyObject, PyAny, PyErr, PyResult, PyTypeInfo, Python, | ||
| exceptions::PyValueError, types::PyString, | ||
| }; | ||
| use zarrs::array::{CodecError, codec::SubchunkWriteOrder}; | ||
|
|
||
| use crate::ChunkItem; | ||
|
|
||
|
|
@@ -41,3 +44,42 @@ pub fn is_whole_chunk(item: &ChunkItem) -> bool { | |
| item.chunk_subset.start().iter().all(|&o| o == 0) | ||
| && item.chunk_subset.shape() == bytemuck::must_cast_slice::<_, u64>(&item.shape) | ||
| } | ||
|
|
||
| #[derive(Debug, Clone, Copy)] | ||
| pub struct SubchunkWriteOrderWrapper(pub SubchunkWriteOrder); | ||
|
|
||
| impl<'py> IntoPyObject<'py> for SubchunkWriteOrderWrapper { | ||
| type Target = PyString; | ||
| type Output = Bound<'py, PyString>; | ||
| type Error = PyErr; | ||
|
|
||
| fn into_pyobject(self, py: Python<'py>) -> Result<Self::Output, Self::Error> { | ||
| match self.0 { | ||
| SubchunkWriteOrder::C => Ok("C".into_pyobject(py)?), | ||
| SubchunkWriteOrder::Random => Ok("random".into_pyobject(py)?), | ||
| _ => Err(PyValueError::new_err( | ||
| "Unrecognized subchunk write order for converting to python object, only `C` and `random` allowed.", | ||
| )), | ||
| } | ||
| } | ||
| } | ||
|
|
||
| impl<'py> FromPyObject<'_, 'py> for SubchunkWriteOrderWrapper { | ||
| type Error = PyErr; | ||
|
|
||
| fn extract(option: Borrowed<'_, 'py, PyAny>) -> PyResult<SubchunkWriteOrderWrapper> { | ||
| match option.extract::<&str>()? { | ||
| "C" => Ok(SubchunkWriteOrderWrapper(SubchunkWriteOrder::C)), | ||
| "random" => Ok(SubchunkWriteOrderWrapper(SubchunkWriteOrder::Random)), | ||
| _ => Err(PyValueError::new_err( | ||
| "Unrecognized subchunk write order while extracting to rust, only `C` and `random` allowed.", | ||
| )), | ||
| } | ||
| } | ||
| } | ||
|
|
||
| impl pyo3_stub_gen::PyStubType for SubchunkWriteOrderWrapper { | ||
| fn type_output() -> pyo3_stub_gen::TypeInfo { | ||
| pyo3_stub_gen::TypeInfo::with_module("typing.Literal['C', 'random']", "typing".into()) | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah duh!
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the parameter is called |
||
| } | ||
| } | ||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this is requeired because of the orphan rule right?
SubchunkWriteOrderis not our type andIntoPyObjectisn’t either. Did you try implementingSubchunkWriteOrderExtinstead for which you then implementIntoPyObject? The orphan rule probably prevents that too, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So went my thinking, although I think
IntoPyObjectnot being ourtraithas nothing to do with this - it's just that we don't createSubchunkWriteOrderhereIs that different than what we have here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, it’d be a trait instead of a type, which would let us use the unwrapped type. But as said, probably doesn’t work.