Skip to content

Investigate "failed to fill whole buffer" when updating the workspace #8212

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
Byron opened this issue Apr 18, 2025 · 1 comment
Open

Investigate "failed to fill whole buffer" when updating the workspace #8212

Byron opened this issue Apr 18, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@Byron
Copy link
Collaborator

Byron commented Apr 18, 2025

From Discord

Hello, I've an issue that appeared today in GitButler, I cannot update the workspace with upstream commits anymore, it fails with the message: failed to fill whole buffer. I've try to make it forget the workspace, delete all the gitbutler/ branches, login again to GitHub but it does not work, I can't integrate upstream changes anymore.


As fetches are performed using the Git command-line, we can probably assume that this works as expected. Hence, the failed to fill whole buffer seems to come from Rust code trying to stream data using std::io::Read.

The question is where that happens, and if it happens when reading objects.
We should be able to learn more about it by launching GitButler from the terminal, configured to print a backtrace and with detailed logging.

RUST_BACKTRACE=1 LOG_LEVEL=debug /Applications/GitButler\ Nightly.app/Contents/MacOS/gitbutler-tauri
@Byron Byron added the bug Something isn't working label Apr 18, 2025
@Byron Byron self-assigned this Apr 18, 2025
@Byron
Copy link
Collaborator Author

Byron commented May 5, 2025

It seems that updating the workspace is indeed a way to produce this issue, see this discord message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant