Skip to content
Back to pull request #375

chore: split Elixir tasks #37

Sign in to view logs

chore: split Elixir tasks

chore: split Elixir tasks #37

Triggered via pull request June 28, 2024 13:12
@haulethhauleth
synchronize #375
hauleth:chore/split-elixir-tasks
Status Success
Total duration 7m 9s
Artifacts –

elixir.yml

on: pull_request
Fetch deps
13s
Fetch deps
Compile project in test env
1m 34s
Compile project in test env
Formatting checks
13s
Formatting checks
Code style
23s
Code style
Run tests
1m 34s
Run tests
Dialyze
3m 53s
Dialyze
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Code style: test/support/cluster.ex#L24
Numbers larger than 9999 should be written with underscores: 10_201
Code style: test/support/fixtures/single_connection.ex#L1
Modules should have a @moduledoc tag.
Code style: lib/supavisor/protocol/client.ex#L1
Modules should have a @moduledoc tag.
Code style: lib/supavisor/tenants/cluster_tenants.ex#L1
Modules should have a @moduledoc tag.
Code style: lib/supavisor/tenants/cluster.ex#L1
Modules should have a @moduledoc tag.
Code style: lib/supavisor/protocol/client.ex#L6
Modules should have a @moduledoc tag.
Code style: lib/supavisor/pg_parser.ex#L1
Modules should have a @moduledoc tag.
Code style: lib/supavisor/helpers.ex#L330
Prefer using an implicit `try` rather than explicit `try`.
Code style: lib/supavisor_web/controllers/metrics_controller.ex#L30
Do not use parentheses when defining a function which has no arguments.
Code style: lib/supavisor/monitoring/osmon.ex#L64
Do not use parentheses when defining a function which has no arguments.