regalloc: multiple uses of vreg with a Stack constraint are not supported

Getting this regalloc error in my GC branch. I've tweaked GC barriers but haven't done anything funky.
Wasm
This is the test Wasm...
            (module
                (table 1 externref)

                (func (export "run") (param externref)
                    i32.const 0
                    local.get 0
                    table.set 0
                )
            )

.clif Test Case
It gets translated to this CLIF...
function u0:0(i64 vmctx, i64, r64) fast {
        gv0 = vmctx
        gv1 = load.i64 notrap aligned readonly gv0+8
        gv2 = load.i64 notrap aligned gv1
        gv3 = vmctx
        gv4 = load.i64 notrap aligned gv3+72
        gv5 = load.i32 notrap aligned gv3+80
        table0 = dynamic gv4, min 0, bound gv5, element_size 8, index_type i32
        sig0 = (i64 vmctx, i64) system_v
        sig1 = (i64 vmctx, i32 uext, i32 uext) -> i32 uext system_v
        sig2 = (i64 vmctx, i32 uext) -> i32 uext system_v
        stack_limit = gv2

                                    block0(v0: i64, v1: i64, v2: r64):
                                        v17 -> v0
                                        v29 -> v0
                                        v30 -> v0
    @002b                               v21 = load.i32 notrap aligned v0+80
    @0027                               v3 = iconst.i32 0
                                        v36 = icmp eq v21, v3  ; v3 = 0
    @002b                               brif v36, block8, block9

                                    block8 cold:
    @002b                               trap table_oob

                                    block9:
    @002b                               v24 = load.i64 notrap aligned v0+72
    @002b                               v28 = select_spectre_guard v36, v24, v24
                                        v4 -> v28
    @002b                               v5 = load.i32 notrap aligned table v28
    @002b                               v8 = is_null.r64 v2
    @002b                               brif v8, block3, block2

                                    block2:
    @002b                               v9 = load.i64 notrap aligned v2+8
                                        v32 = iconst.i64 1
    @002b                               v10 = iadd v9, v32  ; v32 = 1
    @002b                               store notrap aligned v10, v2+8
    @002b                               jump block3

                                    block3:
    @002b                               v11 = bitcast.i64 little v2
    @002b                               v12 = ireduce.i32 v11
    @002b                               store.i64 notrap aligned table v28, v12
    @002b                               v6 = uextend.i64 v5
    @002b                               v7 = bitcast.r64 little v6
    @002b                               v13 = is_null v7
    @002b                               brif v13, block7, block4

                                    block4:
    @002b                               v14 = load.i64 notrap aligned v7+8
                                        v33 = iconst.i64 -1
    @002b                               v15 = iadd v14, v33  ; v33 = -1
                                        v39 = iconst.i64 0
    @002b                               v16 = icmp eq v15, v39  ; v39 = 0
    @002b                               brif v16, block5, block6

                                    block5 cold:
    @002b                               v18 = load.i64 notrap aligned readonly v0+56
    @002b                               v19 = load.i64 notrap aligned readonly v18+200
    @002b                               v20 = bitcast.i64 v7
    @002b                               call_indirect sig0, v19(v0, v20)
    @002b                               jump block7

                                    block6:
                                        v40 = iadd.i64 v14, v33  ; v33 = -1
    @002b                               store notrap aligned v40, v7+8
    @002b                               jump block7

                                    block7:
    @002d                               jump block1

                                    block1:
    @002d                               return
    }

VCode
And that CLIF gets lowered to this VCode
VCode {
      Entry block: 0
      v195 := v232
      v198 := v231
      v199 := v230
      v200 := v229
      v201 := v228
      v203 := v227
      v205 := v194
      v206 := v205
      v207 := v226
      v208 := v207
      v209 := v225
      v210 := v224
      v212 := v223
      v215 := v221
      v216 := v220
      v217 := v208
      v218 := v222
    Block 0:
        (original IR block: block0)
        (successor: Block 11)
        (successor: Block 1)
        (instruction range: 0 .. 4)
      Inst 0: args %v192=%rdi %v193=%rsi %v194=%rdx
      Inst 1: movl    80(%v192), %v232l
      Inst 2: testl   %v195l, %v195l
      Inst 3: jz      label11; j label1
    Block 1:
        (original IR block: block9)
        (successor: Block 2)
        (successor: Block 3)
        (instruction range: 4 .. 12)
      Inst 4: movq    72(%v192), %v231
      Inst 5: testl   %v195l, %v195l
      Inst 6: cmovzq  %v198, %v198, %v230
      Inst 7: movl    0(%v199), %v229l
      Inst 8: cmpq    $0, %v194
      Inst 9: setz    %v228b
      Inst 10: testb   %v201b, %v201b
      Inst 11: jnz     label2; j label3
    Block 2:
        (successor: Block 4)
        (instruction range: 12 .. 13)
      Inst 12: jmp     label4
    Block 3:
        (original IR block: block2)
        (successor: Block 4)
        (instruction range: 13 .. 16)
      Inst 13: movl    $1, %v227l
      Inst 14: addq    %v203, 8(%v194)
      Inst 15: jmp     label4
    Block 4:
        (original IR block: block3)
        (successor: Block 5)
        (successor: Block 6)
        (instruction range: 16 .. 22)
      Inst 16: movq    %v199, 0(%v206)
      Inst 17: movl    %v200l, %v226l
      Inst 18: cmpq    $0, %v208
      Inst 19: setz    %v225b
      Inst 20: testb   %v209b, %v209b
      Inst 21: jnz     label5; j label6
    Block 5:
        (successor: Block 9)
        (instruction range: 22 .. 23)
      Inst 22: jmp     label9
    Block 6:
        (original IR block: block4)
        (successor: Block 8)
        (successor: Block 7)
        (instruction range: 23 .. 27)
      Inst 23: movq    8(%v208), %v224
      Inst 24: lea     -1(%v210), %v223
      Inst 25: testq   %v212, %v212
      Inst 26: jz      label8; j label7
    Block 7:
        (original IR block: block6)
        (successor: Block 9)
        (instruction range: 27 .. 30)
      Inst 27: lea     -1(%v210), %v222
      Inst 28: movq    %v218, 8(%v208)
      Inst 29: jmp     label9
    Block 8:
        (original IR block: block5)
        (successor: Block 9)
        (instruction range: 30 .. 34)
      Inst 30: movq    56(%v192), %v221
      Inst 31: movq    200(%v215), %v220
      Inst 32: call    *%v216
      Inst 33: jmp     label9
    Block 9:
        (original IR block: block7)
        (successor: Block 10)
        (instruction range: 34 .. 35)
      Inst 34: jmp     label10
    Block 10:
        (original IR block: block1)
        (instruction range: 35 .. 36)
      Inst 35: rets
    Block 11:
        (original IR block: block8)
        (instruction range: 36 .. 37)
      Inst 36: ud2 table_oob
    }

Steps to Reproduce
clif-util compile --target x86_64 regalloc-error.clif

Expected Results
No compilation errors
Actual Results
thread 'main' panicked at /home/nick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/regalloc2-0.9.3/src/ion/liveranges.rs:884:57:
multiple uses of vreg with a Stack constraint are not supported

cc @cfallin @elliottt any ideas what's going on here? Error message is not super helpful.

@fitzgen would you perchance be able to get the RA2 liverange dump as well? You can get that by forcing the verbose flag to true in RegallocOptions (it's also set true according to some condition in CL that I forget -- we should really unify our "please log everything" settings!) and then grabbing the trace-level log output.
Also for our potential reproduction: does the CLIF show the same result when compiled on main?

Here is the live range dump:

[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block11
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: []
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block11: []
[2024-03-19T15:39:07Z TRACE cranelift_codegen::isa::x64::inst::emit_state] adjust virtual sp offset by 0x0: 0x0 -> 0x0
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block10
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: []
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] MachBuffer: use_label_at_offset: offset 61 label MachLabel(6) kind JmpRel32
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block10: []
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block9
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] MachBuffer: use_label_at_offset: offset 66 label MachLabel(5) kind JmpRel32
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: []
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block9: []
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block5
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::vcode] emitting block Block(6)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: []
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block5: []
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] MachBuffer: bind label MachLabel(6) at offset 70
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block8
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: []
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v220i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v192i fixed(p7i) was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v226i fixed(p6i) was_live = false
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] enter optimize_branches:
     b = [MachBranch { start: 7, end: 13, target: MachLabel(1), fixup: 0, inverted: Some([15, 133, 0, 0, 0, 0]), labels_at_this_branch: [] }, MachBranch { start: 26, end: 32, target: MachLabel(3), fixup: 1, inverted: Some([15, 132, 0, 0, 0, 0]), labels_at_this_branch: [] }, MachBranch { start: 59, end: 65, target: MachLabel(6), fixup: 2, inverted: Some([15, 132, 0, 0, 0, 0]), labels_at_this_branch: [] }, MachBranch { start: 65, end: 70, target: MachLabel(5), fixup: 3, inverted: None, labels_at_this_branch: [] }]
     l = [MachLabel(6)]
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(6), offset: 61, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 66, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v220i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] optimize_branches: last branch MachBranch { start: 65, end: 70, target: MachLabel(5), fixup: 3, inverted: None, labels_at_this_branch: [] } at off 70
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v221i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v221i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v192i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer]  -> more than one branch; prev_b = MachBranch { start: 59, end: 65, target: MachLabel(6), fixup: 2, inverted: Some([15, 132, 0, 0, 0, 0]), labels_at_this_branch: [] }
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer]  -> uncond follows a conditional, and conditional's target resolves to current offset
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block8: [192, 226]
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] truncate_last_branch: truncated MachBranch { start: 65, end: 70, target: MachLabel(5), fixup: 3, inverted: None, labels_at_this_branch: [] }; off now 65
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block7
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer]  -> reassigning target of condbr to MachLabel(5)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: []
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] optimize_branches: last branch MachBranch { start: 59, end: 65, target: MachLabel(5), fixup: 2, inverted: Some([15, 133, 0, 0, 0, 0]), labels_at_this_branch: [] } at off 65
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v222i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v226i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v222i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v224i reg was_live = false
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] leave optimize_branches:
     b = [MachBranch { start: 7, end: 13, target: MachLabel(1), fixup: 0, inverted: Some([15, 133, 0, 0, 0, 0]), labels_at_this_branch: [] }, MachBranch { start: 26, end: 32, target: MachLabel(3), fixup: 1, inverted: Some([15, 132, 0, 0, 0, 0]), labels_at_this_branch: [] }, MachBranch { start: 59, end: 65, target: MachLabel(5), fixup: 2, inverted: Some([15, 133, 0, 0, 0, 0]), labels_at_this_branch: [] }]
     l = [MachLabel(6)]
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block7: [224, 226]
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::abi] Epilogue: [movq    %rbp, %rsp, popq    %rbp, ret]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block6
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: [192, 224, 226]
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::vcode] emitting block Block(1)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v223i reg was_live = false
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] MachBuffer: bind label MachLabel(1) at offset 70
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v223i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v223i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v224i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v224i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v226i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block6: [192, 226]
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] enter optimize_branches:
     b = [MachBranch { start: 7, end: 13, target: MachLabel(1), fixup: 0, inverted: Some([15, 133, 0, 0, 0, 0]), labels_at_this_branch: [] }, MachBranch { start: 26, end: 32, target: MachLabel(3), fixup: 1, inverted: Some([15, 132, 0, 0, 0, 0]), labels_at_this_branch: [] }, MachBranch { start: 59, end: 65, target: MachLabel(5), fixup: 2, inverted: Some([15, 133, 0, 0, 0, 0]), labels_at_this_branch: [] }]
     l = [MachLabel(1)]
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block4
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] optimize_branches: last branch MachBranch { start: 59, end: 65, target: MachLabel(5), fixup: 2, inverted: Some([15, 133, 0, 0, 0, 0]), labels_at_this_branch: [] } at off 70
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: [192, 226]
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] purge_latest_branches: removing branch MachBranch { start: 59, end: 65, target: MachLabel(5), fixup: 2, inverted: Some([15, 133, 0, 0, 0, 0]), labels_at_this_branch: [] }
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v225i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v225i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v225i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] leave optimize_branches:
     b = []
     l = [MachLabel(1)]
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v226i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v226i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::vcode] emitting block Block(3)
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] MachBuffer: bind label MachLabel(3) at offset 72
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v229i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v230i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v194i reg was_live = false
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] enter optimize_branches:
     b = []
     l = [MachLabel(3)]
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block4: [192, 194, 229, 230]
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] leave optimize_branches:
     b = []
     l = [MachLabel(3)]
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block2
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: [192, 194, 229, 230]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block2: [192, 194, 229, 230]
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::vcode] emitting block Block(5)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block3
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] MachBuffer: bind label MachLabel(5) at offset 74
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: [192, 194, 229, 230]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v227i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v194i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] enter optimize_branches:
     b = []
     l = [MachLabel(5)]
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v227i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] leave optimize_branches:
     b = []
     l = [MachLabel(5)]
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block3: [192, 194, 229, 230]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block1
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: [192, 194, 229, 230]
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] enter optimize_branches:
     b = []
     l = []
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v228i reg was_live = false
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] leave optimize_branches:
     b = []
     l = []
     f = [MachLabelFixup { label: MachLabel(1), offset: 9, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(3), offset: 28, kind: JmpRel32 }, MachLabelFixup { label: MachLabel(5), offset: 61, kind: JmpRel32 }]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v228i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v228i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer]  -> label_offset = 70, known, required = false (pos<PHONE_NUMBER> neg<PHONE_NUMBER>)
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] patching in-range!
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v194i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer]  -> label_offset = 72, known, required = false (pos<PHONE_NUMBER> neg<PHONE_NUMBER>)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v229i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] patching in-range!
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v230i reg was_live = true
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer]  -> label_offset = 74, known, required = false (pos<PHONE_NUMBER> neg<PHONE_NUMBER>)
[2024-03-19T15:39:07Z TRACE cranelift_codegen::machinst::buffer] patching in-range!
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v230i reuse(0) was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v231i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v231i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v232i reg was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v232i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v231i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v192i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block1: [192, 194, 232]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computing liveins for block0
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> initial liveout set: [192, 194, 232]
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v232i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v232i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v232i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Use: v192i reg was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v192i fixed(p7i) was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v193i fixed(p6i) was_live = false
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] op Def: v194i fixed(p2i) was_live = true
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] computed liveins at block0: []
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] inst36 is safepoint
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p0i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p1i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p2i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p6i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p7i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p8i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p9i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p10i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p11i
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p0f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p1f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p2f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p3f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p4f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p5f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p6f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p7f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p8f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p9f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p10f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p11f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p12f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p13f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p14f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] adding liverange to preg: CodeRange { from: progpoint32-post, to: progpoint33-pre } to p15f
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] processing inst32 operand at progpoint32-pre: Use: v220i reg
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(220) range CodeRange { from: progpoint30-pre, to: progpoint32-post }
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] Use of Use: v220i reg at progpoint32-pre -> LiveRangeIndex(0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v220i reg, pos: progpoint32-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(0) with weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] processing inst32 operand at progpoint32-pre: Use: v192i fixed(p7i)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(192) range CodeRange { from: progpoint30-pre, to: progpoint32-post }
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] Use of Use: v192i fixed(p7i) at progpoint32-pre -> LiveRangeIndex(1)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v192i fixed(p7i), pos: progpoint32-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(1) with weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] processing inst32 operand at progpoint32-pre: Use: v226i fixed(p6i)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(226) range CodeRange { from: progpoint30-pre, to: progpoint32-post }
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] Use of Use: v226i fixed(p6i) at progpoint32-pre -> LiveRangeIndex(2)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v226i fixed(p6i), pos: progpoint32-pre, slot: 2, weight: 35447 } into lr LiveRangeIndex(2) with weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] inst32 is safepoint
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] vreg v226 live at safepoint inst32
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] processing inst31 operand at progpoint31-post: Def: v220i reg
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] Def of v220 at progpoint31-post
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v220i reg, pos: progpoint31-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(0) with weight SpillWeight(5000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(8000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint31-post
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] processing inst31 operand at progpoint31-pre: Use: v221i reg
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(221) range CodeRange { from: progpoint30-pre, to: progpoint31-post }
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] Use of Use: v221i reg at progpoint31-pre -> LiveRangeIndex(3)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v221i reg, pos: progpoint31-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(3) with weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] processing inst30 operand at progpoint30-post: Def: v221i reg
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] Def of v221 at progpoint30-post
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(3)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v221i reg, pos: progpoint30-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(3) with weight SpillWeight(5000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(8000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint30-post
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] processing inst30 operand at progpoint30-pre: Use: v192i reg
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] Use of Use: v192i reg at progpoint30-pre -> LiveRangeIndex(1)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v192i reg, pos: progpoint30-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(1) with weight SpillWeight(3000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] processing inst28 operand at progpoint28-pre: Use: v222i reg
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(222) range CodeRange { from: progpoint27-pre, to: progpoint28-post }
[2024-03-19T15:39:07Z TRACE regalloc2::ion::liveranges] Use of Use: v222i reg at progpoint28-pre -> LiveRangeIndex(4)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v222i reg, pos: progpoint28-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(4) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst28 operand at progpoint28-pre: Use: v226i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(226) range CodeRange { from: progpoint27-pre, to: progpoint28-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v226i reg at progpoint28-pre -> LiveRangeIndex(5)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v226i reg, pos: progpoint28-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(5) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst27 operand at progpoint27-post: Def: v222i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v222 at progpoint27-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(4)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v222i reg, pos: progpoint27-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(4) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(8000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint27-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst27 operand at progpoint27-pre: Use: v224i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(224) range CodeRange { from: progpoint27-pre, to: progpoint27-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v224i reg at progpoint27-pre -> LiveRangeIndex(6)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v224i reg, pos: progpoint27-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(6) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(192) live at end of block --> create range CodeRange { from: progpoint23-pre, to: progpoint27-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(192) range CodeRange { from: progpoint23-pre, to: progpoint27-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(224) live at end of block --> create range CodeRange { from: progpoint23-pre, to: progpoint27-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(224) range CodeRange { from: progpoint23-pre, to: progpoint27-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(226) live at end of block --> create range CodeRange { from: progpoint23-pre, to: progpoint27-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(226) range CodeRange { from: progpoint23-pre, to: progpoint27-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst25 operand at progpoint25-pre: Use: v223i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(223) range CodeRange { from: progpoint23-pre, to: progpoint25-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v223i reg at progpoint25-pre -> LiveRangeIndex(8)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v223i reg, pos: progpoint25-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(8) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst25 operand at progpoint25-pre: Use: v223i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v223i reg at progpoint25-pre -> LiveRangeIndex(8)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v223i reg, pos: progpoint25-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(8) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst24 operand at progpoint24-post: Def: v223i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v223 at progpoint24-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(8)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v223i reg, pos: progpoint24-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(8) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(11000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint24-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst24 operand at progpoint24-pre: Use: v224i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v224i reg at progpoint24-pre -> LiveRangeIndex(6)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v224i reg, pos: progpoint24-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(6) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst23 operand at progpoint23-post: Def: v224i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v224 at progpoint23-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(6)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v224i reg, pos: progpoint23-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(6) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(11000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint23-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst23 operand at progpoint23-pre: Use: v226i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v226i reg at progpoint23-pre -> LiveRangeIndex(5)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v226i reg, pos: progpoint23-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(5) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(192) live at end of block --> create range CodeRange { from: progpoint16-pre, to: progpoint22-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(192) range CodeRange { from: progpoint16-pre, to: progpoint22-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(226) live at end of block --> create range CodeRange { from: progpoint16-pre, to: progpoint22-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(226) range CodeRange { from: progpoint16-pre, to: progpoint22-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst20 operand at progpoint20-pre: Use: v225i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(225) range CodeRange { from: progpoint16-pre, to: progpoint20-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v225i reg at progpoint20-pre -> LiveRangeIndex(11)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v225i reg, pos: progpoint20-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(11) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst20 operand at progpoint20-pre: Use: v225i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v225i reg at progpoint20-pre -> LiveRangeIndex(11)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v225i reg, pos: progpoint20-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(11) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst19 operand at progpoint19-post: Def: v225i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v225 at progpoint19-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(11)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v225i reg, pos: progpoint19-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(11) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(11000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint19-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst18 operand at progpoint18-pre: Use: v226i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v226i reg at progpoint18-pre -> LiveRangeIndex(10)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v226i reg, pos: progpoint18-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(10) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst17 operand at progpoint17-post: Def: v226i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v226 at progpoint17-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(10)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v226i reg, pos: progpoint17-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(10) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(8000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint17-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst17 operand at progpoint17-pre: Use: v229i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(229) range CodeRange { from: progpoint16-pre, to: progpoint17-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v229i reg at progpoint17-pre -> LiveRangeIndex(12)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v229i reg, pos: progpoint17-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(12) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst16 operand at progpoint16-pre: Use: v230i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(230) range CodeRange { from: progpoint16-pre, to: progpoint16-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v230i reg at progpoint16-pre -> LiveRangeIndex(13)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v230i reg, pos: progpoint16-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(13) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst16 operand at progpoint16-pre: Use: v194i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(194) range CodeRange { from: progpoint16-pre, to: progpoint16-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v194i reg at progpoint16-pre -> LiveRangeIndex(14)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v194i reg, pos: progpoint16-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(14) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(192) live at end of block --> create range CodeRange { from: progpoint13-pre, to: progpoint16-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(192) range CodeRange { from: progpoint13-pre, to: progpoint16-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(194) live at end of block --> create range CodeRange { from: progpoint13-pre, to: progpoint16-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(194) range CodeRange { from: progpoint13-pre, to: progpoint16-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(229) live at end of block --> create range CodeRange { from: progpoint13-pre, to: progpoint16-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(229) range CodeRange { from: progpoint13-pre, to: progpoint16-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(230) live at end of block --> create range CodeRange { from: progpoint13-pre, to: progpoint16-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(230) range CodeRange { from: progpoint13-pre, to: progpoint16-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst14 operand at progpoint14-pre: Use: v227i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(227) range CodeRange { from: progpoint13-pre, to: progpoint14-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v227i reg at progpoint14-pre -> LiveRangeIndex(15)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v227i reg, pos: progpoint14-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(15) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst14 operand at progpoint14-pre: Use: v194i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v194i reg at progpoint14-pre -> LiveRangeIndex(14)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v194i reg, pos: progpoint14-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(14) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst13 operand at progpoint13-post: Def: v227i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v227 at progpoint13-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(15)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v227i reg, pos: progpoint13-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(15) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(8000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint13-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(192) live at end of block --> create range CodeRange { from: progpoint12-pre, to: progpoint13-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(192) range CodeRange { from: progpoint12-pre, to: progpoint13-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(194) live at end of block --> create range CodeRange { from: progpoint12-pre, to: progpoint13-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(194) range CodeRange { from: progpoint12-pre, to: progpoint13-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(229) live at end of block --> create range CodeRange { from: progpoint12-pre, to: progpoint13-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(229) range CodeRange { from: progpoint12-pre, to: progpoint13-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(230) live at end of block --> create range CodeRange { from: progpoint12-pre, to: progpoint13-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(230) range CodeRange { from: progpoint12-pre, to: progpoint13-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(192) live at end of block --> create range CodeRange { from: progpoint4-pre, to: progpoint12-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(192) range CodeRange { from: progpoint4-pre, to: progpoint12-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(194) live at end of block --> create range CodeRange { from: progpoint4-pre, to: progpoint12-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(194) range CodeRange { from: progpoint4-pre, to: progpoint12-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(229) live at end of block --> create range CodeRange { from: progpoint4-pre, to: progpoint12-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(229) range CodeRange { from: progpoint4-pre, to: progpoint12-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(230) live at end of block --> create range CodeRange { from: progpoint4-pre, to: progpoint12-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(230) range CodeRange { from: progpoint4-pre, to: progpoint12-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst10 operand at progpoint10-pre: Use: v228i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(228) range CodeRange { from: progpoint4-pre, to: progpoint10-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v228i reg at progpoint10-pre -> LiveRangeIndex(16)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v228i reg, pos: progpoint10-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(16) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst10 operand at progpoint10-pre: Use: v228i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v228i reg at progpoint10-pre -> LiveRangeIndex(16)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v228i reg, pos: progpoint10-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(16) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst9 operand at progpoint9-post: Def: v228i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v228 at progpoint9-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(16)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v228i reg, pos: progpoint9-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(16) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(11000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint9-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst8 operand at progpoint8-pre: Use: v194i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v194i reg at progpoint8-pre -> LiveRangeIndex(14)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v194i reg, pos: progpoint8-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(14) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(9000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst7 operand at progpoint7-post: Def: v229i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v229 at progpoint7-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(12)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v229i reg, pos: progpoint7-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(12) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(8000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint7-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst7 operand at progpoint7-pre: Use: v230i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v230i reg at progpoint7-pre -> LiveRangeIndex(13)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v230i reg, pos: progpoint7-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(13) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst6 operand at progpoint6-post: Def: v230i reuse(0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v230 at progpoint6-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(13)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v230i reuse(0), pos: progpoint6-post, slot: 1, weight: 35447 } into lr LiveRangeIndex(13) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(9000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint6-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst6 operand at progpoint6-pre: Use: v231i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(231) range CodeRange { from: progpoint4-pre, to: progpoint6-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v231i reg at progpoint6-pre -> LiveRangeIndex(17)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v231i reg, pos: progpoint6-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(17) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst6 operand at progpoint6-pre: Use: v231i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v231i reg at progpoint6-pre -> LiveRangeIndex(17)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v231i reg, pos: progpoint6-pre, slot: 2, weight: 35447 } into lr LiveRangeIndex(17) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst5 operand at progpoint5-pre: Use: v232i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(232) range CodeRange { from: progpoint4-pre, to: progpoint5-post }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v232i reg at progpoint5-pre -> LiveRangeIndex(18)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v232i reg, pos: progpoint5-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(18) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst5 operand at progpoint5-pre: Use: v232i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v232i reg at progpoint5-pre -> LiveRangeIndex(18)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v232i reg, pos: progpoint5-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(18) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst4 operand at progpoint4-post: Def: v231i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v231 at progpoint4-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(17)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v231i reg, pos: progpoint4-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(17) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(11000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint4-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst4 operand at progpoint4-pre: Use: v192i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v192i reg at progpoint4-pre -> LiveRangeIndex(9)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v192i reg, pos: progpoint4-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(9) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(192) live at end of block --> create range CodeRange { from: progpoint0-pre, to: progpoint4-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(192) range CodeRange { from: progpoint0-pre, to: progpoint4-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(194) live at end of block --> create range CodeRange { from: progpoint0-pre, to: progpoint4-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(194) range CodeRange { from: progpoint0-pre, to: progpoint4-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] vreg VRegIndex(232) live at end of block --> create range CodeRange { from: progpoint0-pre, to: progpoint4-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(232) range CodeRange { from: progpoint0-pre, to: progpoint4-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst2 operand at progpoint2-pre: Use: v232i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v232i reg at progpoint2-pre -> LiveRangeIndex(18)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v232i reg, pos: progpoint2-pre, slot: 0, weight: 35447 } into lr LiveRangeIndex(18) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(9000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst2 operand at progpoint2-pre: Use: v232i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v232i reg at progpoint2-pre -> LiveRangeIndex(18)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v232i reg, pos: progpoint2-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(18) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(12000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst1 operand at progpoint1-post: Def: v232i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v232 at progpoint1-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(18)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v232i reg, pos: progpoint1-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(18) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(17000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint1-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst1 operand at progpoint1-pre: Use: v192i reg
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Use of Use: v192i reg at progpoint1-pre -> LiveRangeIndex(9)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v192i reg, pos: progpoint1-pre, slot: 1, weight: 35447 } into lr LiveRangeIndex(9) with weight SpillWeight(3000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(6000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst0 operand at progpoint0-post: Def: v192i fixed(p7i)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v192 at progpoint0-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(9)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v192i fixed(p7i), pos: progpoint0-post, slot: 0, weight: 35640 } into lr LiveRangeIndex(9) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(11000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint0-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst0 operand at progpoint0-post: Def: v193i fixed(p6i)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v193 at progpoint0-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(4294967295)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] add_liverange_to_vreg: vreg VRegIndex(193) range CodeRange { from: progpoint0-post, to: progpoint1-pre }
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> invalid; created LiveRangeIndex(19)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v193i fixed(p6i), pos: progpoint0-post, slot: 1, weight: 35640 } into lr LiveRangeIndex(19) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] processing inst0 operand at progpoint0-post: Def: v194i fixed(p2i)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Def of v194 at progpoint0-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> has existing LR LiveRangeIndex(14)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Def: v194i fixed(p2i), pos: progpoint0-post, slot: 2, weight: 35640 } into lr LiveRangeIndex(14) with weight SpillWeight(5000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(14000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]  -> started at block start; trimming to progpoint0-post
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] Safepoint-induced stack use of Use: v226i stack at progpoint32-pre -> LiveRangeIndex(2)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] insert use Use { operand: Use: v226i stack, pos: progpoint32-pre, slot: 255, weight: 35060 } into lr LiveRangeIndex(2) with weight SpillWeight(1000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges]   -> now range has weight SpillWeight(4000.0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(192) range LiveRangeIndex(9)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(192) range LiveRangeIndex(7)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(192) range LiveRangeIndex(1)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(193) range LiveRangeIndex(19)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(194) range LiveRangeIndex(14)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(220) range LiveRangeIndex(0)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(221) range LiveRangeIndex(3)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(222) range LiveRangeIndex(4)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(223) range LiveRangeIndex(8)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(224) range LiveRangeIndex(6)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(225) range LiveRangeIndex(11)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(226) range LiveRangeIndex(10)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(226) range LiveRangeIndex(5)
[2024-03-19T15:39:08Z TRACE regalloc2::ion::liveranges] multi-fixed-reg cleanup: vreg VRegIndex(226) range LiveRangeIndex(2)

Reproduces on bd2ea901d3, which was main as of a couple weeks ago.

Here's a little more detail on the panic:
multiple uses of vreg with a Stack constraint are not supported: [Use { operand: Use: v226i fixed(p6i), pos: progpoint32-pre, slot: 2, weight: 35447 }, Use { operand: Use: v226i stack, pos: progpoint32-pre, slot: 255, weight: 35060 }]

Sure enough, Cranelift is asking regalloc2 to put v226 both on the stack, and in p6 (a physical register). This is now possible with overlapping LRs (Trevor's recent change) but wasn't for a long time, hence the panic.
progpoint32 corresponds to Inst 32, which is:
  Inst 32: call    *%v216

so I suspect we're both passing a ref as an argument (fixed register constraint according to ABI) and having it participate in the safepoint. Perhaps we should copy function args to new vregs? That's likely easier than re-engineering regalloc2's frontend to infer an overlap case here.

so I suspect we're both passing a ref as an argument (fixed register constraint according to ABI) and having it participate in the safepoint.

What's interesting is that in this case, the value is not live after the call, so arguably doesn't need to participate in the safepoint, and also relatedly the call takes a pointer not a reference (although the i64 pointer is a bitcast of an r64 reference) for this very reason (the call is the ref-count-reached-zero-so-call-to-the-vm-to-drop-the-object call; see block5 cold in the CLIF).


PaaS example does not deploy in Azure

First of all, thanks for your great demo and talk on JakartaOne!
I wanted to follow the demos, also the ones not shown in the talk, but had problems with the PaaS tutorial.
I did it twice to be sure that I followed all steps correctly, but there seems to be a problem during deployment, the service and web page won't come up.
I connected the logs and saw this:
2019-09-13 12:41:57,581 INFO [org.jboss.as.server] (ServerService Thread Pool -- 45) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
2019-09-13 12:41:57,585 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status reportWFLYCTL0184: New missing/unsatisfied dependencies:service jboss.naming.context.java.jdbc.JavaEECafeDB (missing) dependents: [service jboss.persistenceunit."ROOT.war#coffees".FIRST_PHASE, service jboss.persistenceunit."ROOT.war#coffees"]WFLYCTL0448: 26 additional services are down due to their dependencies being missing or failed
2019-09-13 12:41:57,672 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
2019-09-13 12:41:57,676 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://<IP_ADDRESS>:9990/management
2019-09-13 12:41:57,677 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://<IP_ADDRESS>:9990
2019-09-13 12:41:57,679 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) started (with errors) in 9707ms - Started 484 of 687 services (30 services failed or missing dependencies, 341
Any idea what I might have done wrong or is there anything missing in the tutorial?

There could be a number of things that are happening. It is likely the DB is not configured correctly or the dependent resources were not uploaded correctly.
Please email me at<EMAIL_ADDRESS>What I have found is that a quick screen share is the most efficient way of getting to the bottom of what is going on. Often it is something pretty simple.

This issue has been solved and a minor clarification to the instructions made.


Add multi language support

Use an internationalization library for C/C++ (10%)

for example: http://userguide.icu-project.org/intro

Externalize strings all over the code
Create translations
Find translators
UI (90%)

Use JavaScript libraries for i18n

My only concern is, that this will lead to a situation, where even more players will speak their native language in the public chat on an international server...

AssaultCube's main menu is available in German btw

If we use .po files, we can use http://hosted.weblate.org/ for collaboration.


Interactive window toolbar is wrapping

It does not in notebooks but it does in the interactive window.

This looks like the webview interactive window. The builtin interactive window's toolbar should not wrap, i.e. behaves exactly the same way as the toolbar in native notebooks:

Yeah, user error.


Match default binding modes are stable, remove some ref

bors: r+

ugh, will require bumping pinned versions, of course. Clippy is broken atm, hopefully I can remember to bump once it unbreaks. Leaving open until then.

bors: r+

I have no idea the clippy install failed, when I had clippy working on my machine with rustc-2018-04-06 and clippy-0.0.193, but let's try again with rustc-2018-04-07, I guess.

Clippy built! bors: r+

bors: r+
(It needs to be on its own line, whoops)

gah, bors...

bors: retry
bors: r+
This is good, collided with the other PR


fix(deps): update required version as new features are used from it

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes https://github.com/googleapis/gax-nodejs/issues/1557 🦕

@Rochet2 would you mind singing the CLA please?

@alexander-fenster Done


[Message BUS] like SQS receipt_handle  can delete Messsage anywhere

Dose the Message azure.servicebus.Message had a property like receipt_handle it can use to delete or send messages? Receive once get the ReceiptHandle and can delete anywhere?
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/sqs-example-sending-receiving-msgs.html?highlight=receipthandle
receipt_handle = message['ReceiptHandle']
Delete received message from queue
sqs.delete_message(
QueueUrl=queue_url,
ReceiptHandle=receipt_handle
)
print('Received and deleted message: %s' % message)

Hi @DzcleisureCN ,
Can I assume you are on version 0.50.* ? (as opposed to 7.0.0b*)
If so, yes, simply call message.complete() as demonstrated in this sample.
Closing this as I hope it answers your question, but if any other clarity is needed or if I've misunderstood don't hesitate to reopen or reach out.


OSX10.10.2 MarGo build failed

#cat /etc/profile

export GOOS=darwin
export GOARCH=amd64
export GOROOTPATH=$HOME/program
export GOROOT_BOOTSTRAP=$GOROOTPATH/go1.4.1
export GOROOT=$GOROOTPATH/go
export GOPATH=$HOME/mac/workspace/go
export GOBIN=$GOPATH/bin
export PATH=$GOBIN:$GOROOT/bin:$PATH

| GoSublime error: MarGo build failed
|                > This is possibly a bug or miss-configuration of your environment.
|                > For more help, please file an issue with the following build output
|                > at: https://github.com/DisposaBoy/GoSublime/issues/new
|                > or alternatively, you may send an email to<EMAIL_ADDRESS>|                >
|                >
|                > cmd: ['', 'build', '-v', '-x', '-o', 'gosublime.margo_r14.12.06-1_devel+256116a.exe', 'gosubli.me/margo']
|                > stdout: |                > stderr:
|                > exception: Cannot find command go``
|   install state: busy
| sublime.version: 3065
| sublime.channel: stable
|       about.ann: a14.02.25-1
|   about.version: r14.12.06-1
|         version: r14.12.06-1
|        platform: osx-x64
|            ~bin: ~/Library/Application Support/Sublime Text 3/Packages/User/GoSublime/osx-x64/bin
|       margo.exe: ~bin/gosublime.margo_r14.12.06-1_devel+256116a.exe (ok)
|          go.exe: ~/mac/workspace/go/bin/go (ok)
|      go.version: devel+256116a
|          GOROOT: ~/program/go
|          GOPATH: ~/mac/workspace/go
|           GOBIN: ~/mac/workspace/go/bin (should usually be (not set))
|       set.shell: []
|       env.shell: /bin/bash
|       shell.cmd: ['/bin/bash', '-l', '-c', '${CMD}']

The issue has been resolved,Don't set $GOBIN.But Why?

I had this issue a few weeks ago and since I installed Go directly from src. This json-Blob below demonstrates how I had to adjust my GoSublime User settings.
{
  "env": {
    "GOPATH": "$HOME/.golang",
    "GOROOT": "$HOME/.go"
  }
}

Explanation:
I cloned the Golang git repository to ~/.go and built (installed) it from there.
My Golang projects, packages and binaries reside in ~/.golang/{pkg,src,bin}.
This settings coincide with the settings of my bash environment:
# Setup Go
export GOROOT=$HOME/.go
export GOPATH=$HOME/.golang
export PATH=$GOROOT/bin:$GOPATH/bin:$PATH

I hope this helps.

Run go env to get go env settings, and by doing that, you will find the correct value for $GOROOT.
GOARCH="amd64"
GOBIN=""
GOCHAR="6"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH=""
GORACE=""
GOROOT="/usr/local/homebrew/Cellar/go/1.4.2/libexec"
GOTOOLDIR="/usr/local/homebrew/Cellar/go/1.4.2/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common"
CXX="clang++"
CGO_ENABLED="1"

After that, set "$GOPATH" to the directory you want. Build will work after that.

Had the same issue. My $GOROOT was wrong. :)


Upgrade Cores to SOLR 9

Main things to review are the CKAN and Drupal Searches.
The drupal_portal and search_ cores were copied from already working SOLR 9 configs and schemas. The new stuff is the ckan_ and drupal_<PD Type> ones.

Realizing that I renamed the drupal searches so we cannot really see the diffs between them...I will try to make some other PR to just review those one. And not include so many changes. Closing this one MY BAD


[UX] when editing the integration name the field is not automatically focused

Describe the bug
When clicking the edit button next to the integration name I have to click again the name text field to finally be able to edit the name.
To Reproduce
Steps to reproduce the behavior:

open Kaoto
Click on the edito button next to the integration name
try to type the new name without clicking the text field again

Expected behavior
Clicking the edit button should automatically put the focus on the text field and maybe even autoselect the current name so it can be easily overwritten by just starting to type a new name.
Screenshots

I'd label this as an enhancement, not a bug.. I have the same opinion for #769 too but I digress ;D

I had the choice between feature request and bug :) Not really fitting in any of the 2.


Client Allocation Request for: Humax-EV

Client Allocation Questions
Core Information

Name: Humax-EV
Website / Social Media: https://biz.humaxdigital.com/ev-charging/
Region: Asia excl. Greater China
DataCap Requested: 5TiB
Addresses to be Notarized: f3rlg63jbpkauu4e5pawou5rl2t7zkmidditj6fos7anpmiav4bblqd6u47qwvi4qtbzqw7ytyr3y23gogbw6q
Notary Requested: MasaakiNawatani

@Humax-EV Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Hi @Humax-EV
I currently don't have enough datacap to allocate for you. Please re-submit your request and choose another Notary from the same region. Thank you for your patience. I will now close this request.


Use of threading.local in lock.py can cause token leakage

The use of threading.local()in lock.py appears to have been ported directly from redis-py over to this project. As far as I can tell, this can lead to tokens leaking between asynchronous tasks executed within the same event loop (i.e. on the same thread).
Let's consider the following scenario:

Task A successfully acquires a lock using token a and a timeout of 3 seconds
Task B requests the lock with blocking=True and blocking_timeout=None
Task A takes longer than 3 seconds to finish and so the lock is automatically released
Task B now successfully holds the lock with token b, which is placed in thread local storage
Task A finishes and attempts to release the lock. It retrieves the token b from thread local storage and is successful in releasing the lock, as opposed to getting a LockError due to a token mismatch as would be the correct behavior.

@eirikur-grid Thanks for bug report, i will check it and give my feedback as soon as possible.

@eirikur-grid I am afraid you are right, different coroutines share the same thread, which will break the safety of thread local mechanism. In Python 3.7 i can use contextvars to fix this, i will see if there is a good solution in Python 3.6

@eirikur-grid
I found a backport of contextvars for 3.5/3.6package, this bug will be fixed soon, thanks again for bug report

Just to be additional, I try to reproduce the scene you described and find out that the problem will only take place when one clock is shared between multiple coroutine just like:
async def test():
    r = StrictRedis()
    lock_b = lock_a = r.lock(lock_key, timeout=3)
    print(lock_a.local.token)
    # lock_b = r.lock(lock_key)
    print(lock_b.local.token)
    print(id(lock_b) == id(lock_a))

    res = await lock_a.acquire()
    print('thread a acquire token: {} ts: {} res: {}'.format(lock_a.local.token, time.time(), res))
    print(lock_a.local.__dict__)
    print(lock_b.local.__dict__)
    res = await lock_b.acquire(blocking=True)
    print('thread b acquire token: {} ts: {} res: {}'.format(lock_b.local.token, time.time(), res))
    print(lock_a.local.__dict__)
    print(lock_b.local.__dict__)

    await asyncio.sleep(2)
    try:
        print('thread a release token: {} ts: {}'.format(lock_a.local.token, time.time()))
        print(await r.get(lock_key))
        await lock_a.release()
    except Exception as exc:
        print('thread_a failed to release due to: {} token: {} ts: {}'.format(exc, lock_a.local.token, time.time()))

    try:
        print('thread b release token: {} ts: {}'.format(lock_b.local.token, time.time()))
        print(await r.get(lock_key))
        await lock_b.release()
    except Exception as exc:
        print(exc)

If i initialize another lock instance with the same key, there will be a new threading_local object and lock.local.token will not be covered.
However, i can not limit user the way they use the lock, i will fix it soon

@eirikur-grid The fix is finished, would you like to see it ? It will be merged If there is no other problem :-)

@eirikur-grid Merged, thanks again for bug report~

@eirikur-grid The fix is finished, would you like to see it ? It will be merged If there is no other problem :-)

Sorry for the late reply. I somehow missed the e-mail notification. I'll take a post-merge look and attempt to verify the fix.

@NoneGG I have verified that the fix works as intended. However, I noticed that the newly added test is failing. See: https://github.com/NoneGG/aredis/pull/120/files#r317581785


Tags

I'm thinking we should probably start tagging releases. Thoughts?

Only really makes sense if you plan on offering LTS or something. Every commit generates a nupkg in appveyor. I hooked my work's octopus up to my fork's appveyor build's nuget repo, so I just push new versions when something I care about has been fixed or implement (so, not that often!)

@lukeschafer I'd have to disagree there.If SBManager semver'ed the releases it would allow clients to:

Not have thousands of releases because they are based on every commit
They can upgrade minor revisions with the knowledge that it is backwards compatible

This would also give SbManager the flexibility on deciding when something is ready for release.

I'm all for semver. That said, semver doesn't make a whole lot of sense for websites, though I've been using:


Update Node LTS & Neo4j latest

Superseded by https://github.com/neo4j-examples/movies-java-bolt/pull/57


Support semiauto derivation without recursive derivation

In scala 2, semiauto derivation requires that any nested case classes also have instances defined explicitly, while in scala 3 derivation automatically recurses to perform derivation for the nested case classes (the Mirror.Of branch here), e.g.
case class Foo()
case class Bar(foo: Foo)
// scala 2 - doesn't compile because there's no Decoder[Foo]
io.circe.generic.semiauto.deriveDecoder[Bar]
// scala 3 - compiles
io.circe.Decoder.derived[Bar]

I understand this is convenient in many cases, but I feel like there are a number of reasons it's less then ideal -- for example, I may define a Decoder[Foo] with custom behavior, and then someone later on without context could delete it, see that all code still compiles, and assume that everything is fine when it's not.
Is this behavior by design? If so, would you at least consider alternate derivation methods that skip the recursion?

Gentle nudge to @zarthross and @zmccoy, would you consider a change in this behavior? I would be happy to work on it if so

@Lasering it didn't work because it would require users to define their Configuration values as inline givens, and would silently do the wrong thing if they didn't -- see my comment here: https://github.com/circe/circe/pull/2173#issuecomment-1658900145
I opened another PR, #2183, that would also resolve this

Unfortunately I was not aware of this detail when I implemented #1800. My goal was to have the typeclass derivation in Scala 3 to be a drop-in replacement of the generic (and generic extras) modules. Or in other words by default the typeclass derivation should not recurse, and then the auto derivation (see #2206) would do so. To make things worse, fixing this properly implies a new major version (which I am of the opinion that should be done).

@Lasering I think it should be possible to change the default semantics to NO auto-derivation by default in a way thats binary compatible, but certainly semantically breaking.  We can just announce the change, and while it may break source, it should be possible to be bin-safe.
Is there something that I'm missing there?

In my head this semantic breaking change is big enough to merit a major version (I guess a 0.15.x). Also if you look at https://github.com/circe/circe/issues/1965 the proper fix would be to drop the Configured* classes and to move the derived method from Encoder.AsObject to Encoder, and Codec.AsObject to Codec which also feels like a breaking change to me.
In terms of binary compatibility/MiMa I have very little experience/feel for it. I guess sometimes the are ways of doing things that don't break the binary compatibility, but some times these ways just make things more confusing both for users (because they now see multiple ways of doing things) and for maintainers (because they need to keep track of what is the proper way of doing things and what is part of the bin-safe compatibility shim)


Thanks, it looks a little bit better now :)


[System.ClientModel] Add factory method to create an ApiKeyCredential from an environment variable

Removes the implicit cast from string to ApiKeyCredential
Adds static factory method that create an ApiKeyCredential by retrieving the key from an environment variable

API change check
APIView has identified API level changes in this PR and created following API reviews.
System.ClientModel


API: Remove nested api

IMO, having api as the only sub-package does not pass the sniff test. Also, only return sanitized mongo objects from all find functions.
This will break ophyd and metadatastore dataportal, but those are very easy to fix. I will deal with the changes to both projects if everyone agrees that this PR is a good move.
thoughts @danielballan @tacaswell @arkilic

:+1: from me, need to fix the setup.py to not try to install a package that no longer exists (that is the source of travis failure)

good catch, thanks

:+1:  :+1: from me!

Do we want the insertions to return Document objects too?

I think I vote for yes

So long as it doesn't break the ability to chain them.

How do you mean "chain them"

blc = mds.insert_beamline_config(...)
bre = mds.insert_begin_run_event(blc, ...)

Agreed all around

Hmm... making the insertions return sanitized documents is a pretty large pain and, tbh, I'm not entirely sure how to do it.  Let's leave well enough alone for now

It really is painful! I think I've an idea but have to search the Internet of its the best way to do it.

@arkilic not sure it's high priority right now

No worries. getting rid off api package isn't high priority in the first place :)

Can you also update all of the docstrings?  Should be able to do it via find-replace?

Which docstrings?


Weclient nullreferenceexception

Describe the bug
I am trying to query Azure users with id and it works fine
like https://graph.microsoft.com/v1.0/users/id this works fine when I call webclient.downloadstring(url);
but by Issue is when I use the filter query I always get a nullreferenceexception
https://graph.microsoft.com/v1.0/users?$filter=mail eq<EMAIL_ADDRESS>https://graph.microsoft.com/v1.0/users?$filter=otherMails/any(x:x eq 'emailaddress')
I have looked at this and try many filters and it always work even when it return an empty object
https://developer.microsoft.com/en-us/graph/graph-explorer
any feedback is appreciated
Thanks
Fawzi

this is the message I am getting
System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.

Hey @Fawzissa,
Thanks for raising this.
Any chance you could share more information about the SDK library(version and name) you are using to make the request that results in the NullReference error?

HI Guys
I was able to solve the issue with the errors but now when I get the response for a user filter by email I only able to get JObject json object and I like to know what object will be returned for a user search filter by email
Thanks
@.https://www.tph.ca/
Fawzi Issa
|
Sr. Software Developer
,
Software Development
T
416-538-5409tel:416-538-5409
E
<EMAIL_ADDRESS>77 Auriga Drive,
Unit 3
Ottawa
,
Ontario
K2E 7Z7
Visit us at
TPH.CAhttps://www.tph.ca/
|
Bloghttps://www.tph.ca/blog
Connect with us on
Twitterhttps://twitter.com/tphcanada
|
LinkedInhttps://www.linkedin.com/company/the-printing-house-limited
|
Facebookhttps://www.facebook.com/tphcanada
|
Instagram https://www.instagram.com/tphcanada/
@.
Canada's Greenest Employers (2022)https://www.tph.ca/sustainability/
This e-mail and any attachments may be confidential or legally privileged. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained herein. Please inform us of the erroneous delivery by return e-mail. Thank you for your cooperation.
Le présent courriel et tout fichier joint peuvent contenir des renseignements privilégiés et confidentiels. Si ce envoi ne s'adresse pas à vous, vous devez l'effacer completement. Vous ne pouvez conserver, distribuer, communiquer ou utiliser les renseignements qu'il contient. Nous vous prions de nous signaler l'erreur par courriel. Merci de votre collaboration.
From: Eastman @.>
Sent: May 24, 2022 10:04 AM
To: microsoftgraph/microsoft-graph-explorer-v4 @.>
Cc: Fawzi Issa @.>; Mention @.>
Subject: Re: [microsoftgraph/microsoft-graph-explorer-v4] Weclient nullreferenceexception (Issue #1742)
Hey @Fawzissahttps://github.com/Fawzissa,
Thanks for raising this.
Any chance you could share more information about the SDK library(version and name) you are using to make the request that results in the NullReference error?
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoftgraph/microsoft-graph-explorer-v4/issues/1742#issuecomment-1135972607, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQXWQHMJNKJMSYQLBDE72LLVLTOVHANCNFSM5WF3UR7A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Any chance you could share more information about the SDK library (version and name) you are using to make the request that results in the NullReference error?

Hey @Fawzissa,
Any chance you could share the information above as well as a code sample to help us replicate?

Hey @Fawzissa,
Thanks for the feedback.
Making calls with the Graph SDK, will enable you to get strongly typed objects. However, if you wish to deserialize the object yourself, the response returned from the API /users api should look like the data described in the documentation here.


Add packer build

[ ] I have added the tests to cover my changes.
[ ] I have updated the documentation and CHANGELOG accordingly.
[ ] I have read the CONTRIBUTING document.

sweet!!

@venkatBala handing this off to you to review/complete when you have time

updated to this: https://github.com/AgnostiqHQ/terraform/pull/1

@wjcunningham7 can this one be closed... since all infra related stuff has been moved out of core?

@wjcunningham7 can this one be closed... since all infra related stuff has been moved out of core?

Yes


When a value is already set, then the first data-rejected call is wrong

I think this is a bug. Look at this HTML
<textarea id="toEmailList" name="to" data-ng-model="videomail.to" data-ng-model-options="{allowInvalid:true}" data-rejected="toRejects"></textarea>

Let's assume, there is initial code setting the model first, i.E. videomail.to = fsdfsdfsdf@sdfsd, then a bad array is passed onto this watcher:
$scope.$watch('toRejects', function (badEmails) {
    ...
})

where badEmails is like this:

badEmails: Array[17]
0: "f"
1: "s"
2: "d"
3: "f"
4: "s"
5: "d"
6: "f"
7: "s"
8: "d"
9: "f"
10: "@"
11: "s"
12: "d"
13: "f"
14: "s"
15: "d"
16: "f"

but it shouldn't be.

You're initializing the model value to a string instead of an array. The validation function coerces the string into an array of individual characters. Each character fails the email regex and then gets pushed into the rejected array.
As of 1.1.0, the ng-email-list will now throw an error if you set the ng-model to anything but an array or undefined.

ah, wonderful, good update - works now!


Fix announcing seeding rules on connect

A global variable set during an automod run is not available when en event from the log event loop is processed. Save this shared state in redis instead.
Also make announcement work when only disallowed roles is configured.

Might be preferable to use dependency injection in is_first_run_done and set_first_run_done to make it easier to mock during testing though.

There is not much level we can move this up, but I just go ahead and do it as far as possible (the methods are used in class-less function entrypoints anyway).


Check with John about the API returning empty races

From John:

Greg,
After 6am on election day every race should be initialized with zero votes.
So after that I don't think a valid request should come up empty.
This rings a bell though. Have to think about why we don't 404 when no data is returned.
John

That's good to know.

I think we can close this, open it back up if John returns with additional info