akka/akka-core

Unstashed messages enqueued in TestActorRef mailbox while processing a message from self are stuck until another message is received

Open

#30,170 建立於 2021年4月7日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Scala (13,277 star) (3,547 fork)batch import
help wantednice-to-have (low-prio)t:testing

描述

In the following workflow, unstashed messages are enqueued in the mailbox but are not processed as expected:

  1. Send message (messageOne) from TestKit to TestActorRef
  2. TestActorRef underlying actor stashes messageOne and schedules a subsequent message to self (selfMessage)
  3. selfMessage is sent and processed and messageOne is unstashed during processing of selfMessage
  4. messageOne is not processed
  5. Send another message (messageTwo) from TestKit to TestActorRef
  6. Both messageOne and messageTwo are processed

akka.testkit.CallingThreadDispatcher#runQueue appears to process the provided MessageQueue at the time of invocation rather than using the active Mailbox MessageQueue.

貢獻者指南

技術棧
scala
領域
backendtesting
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Akka fundamentalsUnderstanding of actor mailboxKnowledge of CallingThreadDispatcher
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
Investigate the implementation of CallingThreadDispatcher.runQueue method and its interaction with the Mailbox's MessageQueue. The issue suggests that runQueue processes the provided MessageQueue instead of the active one. Compare with the expected behavior and check if there are any related changes in the codebase. Consider looking at the stashing mechanism and how messages are unstashed during self message processing.