Skip to content

fix: 🐛 cluster detection #38

fix: 🐛 cluster detection

fix: 🐛 cluster detection #38

Triggered via pull request January 8, 2025 13:57
Status Success
Total duration 8m 3s
Artifacts

elixir.yml

on: pull_request
Static checks (format, credo, dialyzer)
58s
Static checks (format, credo, dialyzer)
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

23 warnings
Static checks (format, credo, dialyzer)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test (ce_test, postgres:16)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test (test, postgres:16, experimental_reduced_joins)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test (test, postgres:16, experimental_reduced_joins)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead
Build and test (test, postgres:16, experimental_reduced_joins)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:15)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test (test, postgres:15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:15)
62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead
Build and test (test, postgres:15)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:15)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:15)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test (test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test (test, postgres:16)
62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead
Build and test (test, postgres:16)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it