-
Notifications
You must be signed in to change notification settings - Fork 392
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
[#6279] feat (gvfs-fuse): Add gvfs-fuse integration tests for big files and open-file flag test cases #6280
base: main
Are you sure you want to change the base?
Conversation
� Conflicts: � .github/workflows/gvfs-fuse-build-test.yml � clients/filesystem-fuse/tests/bin/gvfs_fuse.sh
if self.buffer.len() > OpenDalFileSystem::WRITE_BUFFER_SIZE { | ||
let mut new_buffer: Vec<u8> = | ||
Vec::with_capacity(OpenDalFileSystem::WRITE_BUFFER_SIZE + 4096); | ||
new_buffer.append(&mut self.buffer); |
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.
You didn't clear the buffer after writing to the underlying fs, is that expected?
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.
Yes, the self.buffer
is cleared after the append operation.
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.
could you point out where did you clear the buffer?
Ok(data.len() as u32) | ||
} | ||
|
||
async fn close(&mut self) -> Result<()> { | ||
if !self.buffer.is_empty() { | ||
let mut new_buffer: Vec<u8> = vec![]; |
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.
buffer not cleared too?
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.
same
What changes were proposed in this pull request?
Add gvfs-fuse integration tests for big files and open-file flag test cases
Why are the changes needed?
Fix: #6279
Does this PR introduce any user-facing change?
No
How was this patch tested?
IT