No description
The persisted grid_data files contain atoms (:base_m, :top_m, :thickness_m, :min_freq_ghz, :native_min_gradient, :ducts, etc.) that live in modules which aren't eagerly loaded during application start. warm_grid_cache_from_latest_profile runs in Application.start/2 before those modules get pulled in by their first call sites, so [:safe] was rejecting our own legitimate files at boot — every weather page hit crashed with "invalid or unsafe external representation of a term". The whole point of [:safe] is to refuse atoms from untrusted external ETF input. ProfilesFile.write!/2 in this same module is the only writer of these files, so the input is trusted by definition — drop the flag. The test additions round-trip the production data shape including duct fields as a regression guard. |
||
|---|---|---|
| .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