Skip to content

APIv2: Aggregates, timeseries, conversion_rate, hostname (#4251) #1

APIv2: Aggregates, timeseries, conversion_rate, hostname (#4251)

APIv2: Aggregates, timeseries, conversion_rate, hostname (#4251) #1

Triggered via push June 28, 2024 13:17
Status Success
Total duration 8m 0s
Artifacts

elixir.yml

on: push
Static checks (format, credo, dialyzer)
7m 50s
Static checks (format, credo, dialyzer)
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

30 warnings
Build and test (ce_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 (ce_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 (ce_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 (ce_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 (ce_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 (ce_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: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, 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: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
Static checks (format, credo, dialyzer)
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
Static checks (format, credo, dialyzer)
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
Static checks (format, credo, dialyzer)
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
Static checks (format, credo, dialyzer)
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
Static checks (format, credo, dialyzer)
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
Static checks (format, credo, dialyzer)
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