Skip to content

fix: use old multitenancy in generated removals of previous indexes #2543

fix: use old multitenancy in generated removals of previous indexes

fix: use old multitenancy in generated removals of previous indexes #2543

Triggered via pull request April 23, 2025 15:03
Status Failure
Total duration 11m 52s
Artifacts 1

elixir.yml

on: pull_request
Matrix: ash-ci
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
ash-ci (15) / Report Mix Dependencies
Process completed with exit code 1.
ash-ci (16) / Report Mix Dependencies
Process completed with exit code 1.
ash-ci (14) / Report Mix Dependencies
Process completed with exit code 1.
ash-ci (16) / mix sobelow
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
ash-ci (15) / mix sobelow
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention
ash-ci (14) / mix sobelow
Range.new/2 and first..last default to a step of -1 when last < first. Use Range.new(first, last, -1) or first..last//-1, or pass 1 if that was your intention

Artifacts

Produced during runtime
Name Size Digest
github-pages Expired
368 KB
sha256:3c2f27eac7ca04908df96bd29590270158dba802e04dad0f13abca4a37c059bf