CaseClauseError
- Dominant language
- Elixir
- Stars
- 1.3k
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
We've shortly switched to swarm in the quantum library.
We're seeing two errors when we do agressive up / down scaling.
These errors may very well be errors on the side of the quantum library, but I'm not able to determine the problem.
```
web_5 | 19:33:01.556 [error] [swarm on quantum_swarm_umbrella@172.18.0.14] [tracker:handle_handoff] ** (CaseClauseError) no case clause matching: {:entry, QuantumSwarm.Scheduler.ExecutionBroadcaster, #PID<32732.1428.0>, #Reference<0.3516506690.689963012.197623>, %{mfa: {Quantum.ExecutionBroadcaster, :start_link, [%Quantum.ExecutionBroadcaster.StartOpts{debug_logging: true, job_broadcaster_reference: {:via, :swarm, QuantumSwarm.Scheduler.JobBroadcaster}, name: QuantumSwarm.Scheduler.ExecutionBroadcaster, scheduler: QuantumSwarm.Scheduler, storage: Quantum.Storage.Noop}]}}, {{0, 3}, {1, 3}}}
```
The issue is tracked here on quantums side: https://github.com/quantum-elixir/quantum-core/issues/374
Help to this issue is very welcome.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported tracker:handle_handoff CaseClauseError during aggressive scaling and compare it with Quantum issue 374. Reproduce the swarm and Quantum interaction if possible, then determine whether the failure belongs in Swarm or Quantum; done requires a confirmed cause and an agreed fix location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100