No description
Observed in prod: after the CDS cap guard shipped, jobs started landing but one leg per tile-month would routinely stay in 'accepted' state for 16+ hours while the other completed in ~90 minutes. CDS's per-user queue fairness apparently serializes competing leg requests and the single-level ones got stranded behind higher-priority work. Add an age-based stuck detector in Era5PollWorker: if a row has been submitted for more than 4 hours and neither leg is fully done, treat both legs as terminal, clean them up from CDS, and re-enqueue the submit. Re-uses the resubmit_vanished path. 4h is ~8× the normal completion time so transient queue variance doesn't trip it, but tight enough that stuck jobs self-heal in a working session. |
||
|---|---|---|
| .forgejo/workflows | ||
| .github | ||
| assets | ||
| bin | ||
| config | ||
| docs | ||
| k8s | ||
| lib | ||
| lib_ml | ||
| notebooks | ||
| priv | ||
| rel | ||
| scripts | ||
| test | ||
| vendor | ||
| .credo.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitignore | ||
| .tool-versions | ||
| AGENTS.md | ||
| algo.md | ||
| app.json | ||
| CLAUDE.md | ||
| Dockerfile | ||
| elevation.md | ||
| mix.exs | ||
| mix.lock | ||
| prediction.md | ||
| README.md | ||
| tail_logs.sh | ||
| updates.md | ||
Microwaveprop
To start your Phoenix server:
- Run
mix setupto install and setup dependencies - Start Phoenix endpoint with
mix phx.serveror inside IEx withiex -S mix phx.server
Now you can visit localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.
Learn more
- Official website: https://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix