Skip to content

A proof-of-concept for a long-running function#12722

Draft
Byron wants to merge 2 commits intogitbutlerapp:masterfrom
Byron:next5
Draft

A proof-of-concept for a long-running function#12722
Byron wants to merge 2 commits intogitbutlerapp:masterfrom
Byron:next5

Conversation

@Byron
Copy link
Collaborator

@Byron Byron commented Mar 7, 2026

For but-lite we need a way to deal with (potentially) long-running operations.

The PoC presented here is pretty much based on what gix does when it comes to progress and cancellation.

Tasks

  • PoC callee
  • but-testing integration to see the Rust side

Notes for the Reviewer

You can work backwards from cargo run -p but-testing -- long-running -d 5s, which represents a Rust caller.

@vercel
Copy link

vercel bot commented Mar 7, 2026

@Byron is attempting to deploy a commit to the GitButler Team on Vercel.

A member of the Team first needs to authorize it.

While it's using `gix::Progress`, it could also use anything else for that.
There might also be alternatives that offer checks for cancellation as part of the progress,
but I found it better to make this explcit.

Co-authored-by: chatgpt-codex-connector[bot] <199175422+chatgpt-codex-connector[bot]@users.noreply.github.com>
That's particularly interesting for the Progress visualisation
and instantiation, as our 'renderer' would be a forwarder of
sorts to pass the progress state on to the frontend.

Co-authored-by: Sebastian Thiel <sebastian.thiel@icloud.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant