Skip to content

fix(forge): progress message ordering#427

Merged
mhanberg merged 1 commit intomainfrom
fix-stale-progress-messages
Feb 22, 2026
Merged

fix(forge): progress message ordering#427
mhanberg merged 1 commit intomainfrom
fix-stale-progress-messages

Conversation

@scohen
Copy link
Contributor

@scohen scohen commented Feb 22, 2026

Due to the use of erpc_cast, it was possible that the completion message could arrive before a progress message. When this would happen (which would happen very often during expert's app startup process), emacs would not clear the current minibuffer's progress message. This would leave buidling xp-<something> in the minibuffer for the existing session, and no other messages would appear.

The fix is to use erpc_call, though this would have been easy to accomplish if progress had state, and could cancel any outstanding messages.

@scohen scohen requested review from Moosieus and mhanberg February 22, 2026 00:12
@scohen scohen changed the title [fix] fix ordering in progress messages fix(forge): fix ordering in progress messages Feb 22, 2026
Due to the use of erpc_cast, it was possible that the completion
message could arrive before a progress message. When this would
happen (which would happen very often during expert's app startup
process), emacs would not clear the current minibuffer's progress
message. This would leave `buidling xp-<something>` in the minibuffer
for the existing session, and no other messages would appear.

The fix is to use erpc_call, though this would have been easy to
accomplish if progress had state, and could cancel any outstanding messages.
@scohen scohen force-pushed the fix-stale-progress-messages branch from 3ca8045 to 23eebdc Compare February 22, 2026 00:34
@mhanberg mhanberg changed the title fix(forge): fix ordering in progress messages fix(forge): progress message ordering Feb 22, 2026
@mhanberg mhanberg merged commit f3b9187 into main Feb 22, 2026
37 of 38 checks passed
@mhanberg mhanberg deleted the fix-stale-progress-messages branch February 22, 2026 12:10
mhanberg pushed a commit that referenced this pull request Feb 22, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.1.0-rc.1](v0.1.0-rc.0...v0.1.0-rc.1)
(2026-02-22)


### Features

* prompt user to fetch deps when they get out of sync
([#405](#405))
([fc16ddc](fc16ddc))


### Bug Fixes

* build expert on latest nixpkgs
([#422](#422))
([d3eb92c](d3eb92c))
* bump spitfire v0.3.7
([#425](#425))
([ce508c8](ce508c8))
* **engine:** don't collect sibling scopes in Phoenix router
([#420](#420))
([b72bfc8](b72bfc8))
* **expert:** don't crash on missing root_uri
([#412](#412))
([11ed716](11ed716))
* **forge:** progress message ordering
([#427](#427))
([f3b9187](f3b9187))
* migrate expert runtime logging to OTP handlers
([#419](#419))
([8f2dda5](8f2dda5))
* provide typespec docs on hover for private functions
([#407](#407))
([79c5451](79c5451))


### Miscellaneous Chores

* release as 0.1.0-rc.1
([6f5986e](6f5986e))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants