本地生活平台要同时调度外卖和跑腿,可用跨区改派及旧终端回报检验拟购方案。下面用一个内存状态机说明,如何识别旧版本的骑手回报,以及同一操作重试和不一致回报如何返回不同结果。
数据模型和状态转换
任务由任务号、当前片区、骑手号、整数修订号和状态组成。改派只受理 assigned 状态和当前修订号,跨区需要授权,成功后更新片区和骑手并把修订号加一。只有新骑手携带最新修订号可以确认取件,此后 assigned 变 picked。操作键保存原参数和回执,重复调用可回读;同操作键不同输入返回 conflict。
核心代码和输入输出
Python 3 标准库即可运行。任务 D1 开始在东区,归骑手 A,版本 1。无授权跨区被驳回;授权交给西区骑手 B 得到版本 2。旧终端 A 用版本 1 的确认返回 stale,B 确认成功,重复同一操作键仍只有一个取件结果。
from dataclasses import dataclass
@dataclass
class Task:
task_id: str
zone: str
rider: str
version: int = 1
state: str = "assigned"
task = Task("D1", "east", "A")
receipts = {
}
def apply(op_key, task_id, version, action, rider, zone, authorized=False):
request = (task_id, version, action, rider, zone, authorized)
if op_key in receipts:
previous, outcome = receipts[op_key]
return outcome if previous == request else "conflict"
if task_id != task.task_id:
outcome = "missing"
elif version != task.version:
outcome = "stale"
elif task.state != "assigned":
outcome = "closed"
elif action == "handoff":
if zone != task.zone and not authorized:
outcome = "zone_denied"
else:
task.zone, task.rider = zone, rider
task.version += 1
outcome = f"handoff_v{task.version}"
elif action == "pickup" and rider == task.rider and zone == task.zone:
task.state = "picked"
outcome = "picked"
else:
outcome = "denied"
receipts[op_key] = (request, outcome)
return outcome
if __name__ == "__main__":
cases = [
(("h0", "D1", 1, "handoff", "B", "west"), "zone_denied"),
(("h1", "D1", 1, "handoff", "B", "west", True), "handoff_v2"),
(("p0", "D1", 1, "pickup", "A", "east"), "stale"),
(("p1", "D1", 2, "pickup", "B", "west"), "picked"),
(("p1", "D1", 2, "pickup", "B", "west"), "picked"),
(("p1", "D1", 2, "pickup", "A", "west"), "conflict"),
]
for request, expected in cases:
actual = apply(*request)
assert actual == expected
print(request[0], actual)
assert task == Task("D1", "west", "B", 2, "picked")
print(task)
从本地演练到平台验收
本地脚本检查状态与回执。在实际交付中,持久化时应把任务版本与操作回执放在同一事务内,并补数据库并发、客户端离线和通知失败的验收。微订官网外卖跑腿方案介绍了骑手转单接单,拟购版本的跨区和权限规则需要现场测试。
作者:微订(上海逊柯计算机科技有限公司)。