Storage mismatch @testnet's block 2400907

file BlockStorage_2500000/dump-block-2401000.json: block 2400907, changes number mismatch: 3 vs 0
To be continued...

Ours:
 {
  "block": 2400907,
  "size": 3,
  "storage": [
   {
    "state": "Added",
    "key": "acdbf5346b59185b0e0df88fead2a7e856df1ab562616c616e63655f0070901d9c6f03be00e2fdcd89104df3d0888d56767900000003",
    "value": "000400ca9a3b00"
   },
   {
    "state": "Changed",
    "key": "acdbf5346b59185b0e0df88fead2a7e856df1ab562616c616e63655f00937d87615f1a9d00839388b88b0692f402262e9cf000000003",
    "value": "000600608bf03f0700"
   },
   {
    "state": "Changed",
    "key": "acdbf5346b59185b0e0df88fead2a7e856df1ab56c6f636b7570735f937d87615f1a9d83009388b88b0692f402262e9cf0af14030001",
    "value": "00fd0f0180040203b014030203af14030205004429353a8219020107000500e40b5402020108000500e40b5402020109000500e40b540202010a000500e40b540202010b000500e40b540202010c000500e40b540202010d000500e40b540202010e000500e40b540202010f000500e40b5402020110000500e40b5402020111000500e40b5402020112000500e40b5402020113000500e40b5402020114000500e40b5402020115000500e40b5402020116000500e40b5402020117000500e40b5402020118000500e40b5402020119000500e40b540202011a000500e40b540202011b000500e40b540202011c000500e40b540202011d000500e40b540202011e000500e40b540202011f000500e40b540200"
   }
  ]
 }

Theirs:
   {
      "block" : 2400907,
      "storage" : [],
      "size" : 0
   }

Ours:
{
   "result" : {
      "txid" : "0x61366ab9fe37e100854446ab30005d7afbb093096670592ed8d499e3b6a6f753",
      "executions" : [
         {
            "stack" : [],
            "contract" : "0x1c56430bf57861cd7244abc9b6ae351f67be989a",
            "trigger" : "Application",
            "vmstate" : "HALT",
            "notifications" : [
               {
                  "contract" : "0xb51adf56e8a7d2ea8ff80d0e5b18596b34f5dbac",
                  "state" : {
                     "value" : [
                        {
                           "type" : "ByteArray",
                           "value" : "7472616e73666572"
                        },
                        {
                           "value" : "937d87615f1a9d839388b88b0692f402262e9cf0",
                           "type" : "ByteArray"
                        },
                        {
                           "type" : "ByteArray",
                           "value" : "70901d9c6f03bee2fdcd89104df3d0888d567679"
                        },
                        {
                           "type" : "ByteArray",
                           "value" : "00ca9a3b"
                        }
                     ],
                     "type" : "Array"
                  }
               }
            ],
            "gas_consumed" : "6.964"
         }
      ]
   },
   "id" : 1,
   "jsonrpc" : "2.0"
}

Theirs:
{
   "result" : {
      "txid" : "0x61366ab9fe37e100854446ab30005d7afbb093096670592ed8d499e3b6a6f753",
      "executions" : [
         {
            "trigger" : "Application",
            "vmstate" : "FAULT",
            "contract" : "0x1c56430bf57861cd7244abc9b6ae351f67be989a",
            "stack" : [],
            "notifications" : [],
            "gas_consumed" : "5.645"
         }
      ]
   },
   "id" : 1,
   "jsonrpc" : "2.0"
}

Execution log: loh.txt.gz.
Execution log with reverse Storage.Find order:
lohrev.txt.gz.
I have a suspicion that it's a friend of #822, even though reversing items sorting doesn't really change the end result (transaction succeeds). Also, we only have one transaction here in the block.
As I see it the execution faults in C# not because of some wrong VM state (we're at regular PICKITEM with 5.645 GAS consumed), but because of transfer (and it's a transfer tx) failure (and subsequent THROWIFNOT in the entry script), empty stack is a hint for that. But it's not easy to tell why it happens so.

As for branching points, the most obvious one is
8589 5.603 JMPIFNOT 4500 "E\x00"

But this one actually tests for receiver hash length (roughly len("70901d9c6f03bee2fdcd89104df3d0888d567679") == 20), so I don't see how it could fail.

Previous one:
2582 4.526 JMPIFNOT 1400 "\x14\x00"

depends on this test:
estack [
    {
        "type": "Integer",
        "value": "7971200000000"
    },
    {
        "type": "ByteArray",
        "value": ""
    }
]
2573 4.52 LTE  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]

where<PHONE_NUMBER>000 is
estack [
    {
        "type": "ByteArray",
        "value": "937d87615f1a9d839388b88b0692f402262e9cf0"
    },
    {
        "type": "ByteArray",
        "value": "002a262c4007"
    },
    {
        "type": "ByteArray",
        "value": "00ca9a3b"
    }
]
9486 4.454 SUB  ""

estack [
    {
        "type": "ByteArray",
        "value": "937d87615f1a9d839388b88b0692f402262e9cf0"
    },
    {
        "type": "Integer",
        "value": "7971200000000"
    }
]

So it's a balance check, transferred amount (0x00ca9a3b) is subtracted from stored balance (and it's can't be wrong as the state matches before this block).

The balance is previously stored here:
 {
  "block": 2401512,
  "size": 2,
  "storage": [
   {
    "state": "Changed",
    "key": "acdbf5346b59185b0e0df88fead2a7e856df1ab562616c616e63655f00937d87615f1a9d00839388b88b0692f402262e9cf000000003",
    "value": "0006002a262c400700"
   },
   {
    "state": "Changed",
    "key": "acdbf5346b59185b0e0df88fead2a7e856df1ab562616c616e63655f006e0fd712b8691f00545a9a0f553358789b434ba19800000003",
    "value": "00050031cce20100"
   }
  ]
 },

One deeper:
2461 4.479 JMPIFNOT 4500 "E\x00"

Depends on

estack [
    {
        "type": "ByteArray",
        "value": "937d87615f1a9d839388b88b0692f402262e9cf0"
    }
]
2447 4.471 ARRAYSIZE  ""

estack [
    {
        "type": "Integer",
        "value": "20"
    }
]
2448 4.472 PUSHBYTES1 14 "\x14"

estack [
    {
        "type": "Integer",
        "value": "20"
    },
    {
        "type": "ByteArray",
        "value": "14"
    }
]
2450 4.472 NUMEQUAL  ""

estack [
    {
        "type": "Boolean",
        "value": true
    }
]
2451 4.473 PUSH0  ""

estack [
    {
        "type": "Boolean",
        "value": true
    },
    {
        "type": "ByteArray",
        "value": ""
    }
]
2452 4.473 NUMEQUAL  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]

So it's yet another length check.

One deeper:
estack [
    {
        "type": "ByteArray",
        "value": ""
    }
]
9460 4.447 JMPIFNOT 1100 "\x11\x00"

It seems to be dependent on
estack []
6212 1.006 PUSH0  ""

estack [
    {
        "type": "ByteArray",
        "value": ""
    }
]

Which comes after conditional:
estack [
    {
        "type": "Boolean",
        "value": true
    }
]
6208 1.005 JMPIFNOT 0d00 "\r\x00"

That depends on
6198 0.999 PUSH0  ""

estack [
    {
        "type": "ByteArray",
        "value": ""
    },
    {
        "type": "ByteArray",
        "value": ""
    }
]
6199 0.999 LTE  ""

estack [
    {
        "type": "Boolean",
        "value": true
    }
]

The first value coming from
estack [
    {
        "type": "ByteArray",
        "value": "6f7463417070726f7665645f0070901d9c6f03bee2fdcd89104df3d0888d567679"
    },
    {
        "type": "InteropInterface",
        "value": null
    }
]
10699 0.891 SYSCALL 4e656f2e53746f726167652e476574 "Neo.Storage.Get"

estack [
    {
        "type": "ByteArray",
        "value": ""
    }
]

So it's a receiver balance check in the end.

Previous branch:
estack [
    {
        "type": "Boolean",
        "value": false
    }
]
9375 4.439 JMPIFNOT 4a00 "J\x00"

Which is the result of this:
estack [
    {
        "type": "ByteArray",
        "value": "00ca9a3b"
    },
    {
        "type": "ByteArray",
        "value": ""
    }
]
9362 4.432 NUMEQUAL  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]

It's a transfer amount positiveness check, nothing bad here.

One deeper, comparing sender and receiver for equality:
estack [
    {
        "type": "ByteArray",
        "value": "937d87615f1a9d839388b88b0692f402262e9cf0"
    },
    {
        "type": "ByteArray",
        "value": "70901d9c6f03bee2fdcd89104df3d0888d567679"
    }
]
9354 4.428 NUMEQUAL  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]
9355 4.429 JMPIF 0b00 "\v\x00"

Another one:
estack [
    {
        "type": "Boolean",
        "value": false
    }
]
9276 4.423 JMPIFNOT 4800 "H\x00"

Results from:
estack [
    {
        "type": "Integer",
        "value": "10000000000"
    },
    {
        "type": "ByteArray",
        "value": "00ca9a3b"
    }
]
9267 4.417 LT  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]

This one is a bit more interesting, there is some magic 100×10⁸ constant, but our transfer amount doesn't exceed it (13277755).

Before that there is some work being done on values from storage like, that might be more interesting:
estack [
    {
        "type": "Boolean",
        "value": false
    }
]
3330 4.39 JMPIFNOT 0d00 "\r\x00"

From:
estack [
    {
        "type": "Integer",
        "value": "7962200000000"
    },
    {
        "type": "ByteArray",
        "value": ""
    }
]
3319 4.384 LT  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]

Prev:
estack [
    {
        "type": "Boolean",
        "value": false
    }
]
3312 4.381 JMPIF ddfd "\xdd\xfd"

From:
estack [
    {
        "type": "InteropInterface",
        "value": null
    }
]
3283 4.375 SYSCALL 4e656f2e4974657261746f722e4e657874 "Neo.Iterator.Next"

estack [
    {
        "type": "Boolean",
        "value": false
    }
]

End of iteration.

BTW, reversing storage items doesn't affect the value computed, it's still<PHONE_NUMBER>000, albeit at a bit different GAS meter:
estack [
    {
        "type": "Integer",
        "value": "6714336600000"
    },
    {
        "type": "Integer",
        "value": "1247863400000"
    }
]
3272 4.369 ADD  ""

estack [
    {
        "type": "Integer",
        "value": "7962200000000"
    }
]

One Storage.Find item processing (`3283 1.697 SYSCALL 4e656f2e4974657261746f722e4e657874 "Neo.Iterator.Next") looks like this:

get value (2770 1.706 SYSCALL 4e656f2e4974657261746f722e56616c7565 "Neo.Iterator.Value")
deserialize (2791 1.707 SYSCALL 4e656f2e52756e74696d652e446573657269616c697a65 "Neo.Runtime.Deserialize"), typical items looks like this:

estack [
    {
        "type": "Array",
        "value": [
            {
                "type": "Integer",
                "value": "202002"
            },
            {
                "type": "Integer",
                "value": "202001"
            },
            {
                "type": "Integer",
                "value": "1247863400000"
            },
            {
                "type": "Map",
                "value": [
                    {
                        "key": {
                            "type": "Integer",
                            "value": "5"
                        },
                        "value": {
                            "type": "Integer",
                            "value": "1247863400000"
                        }
                    }
                ]
            }
        ]
    }
]

compare the second date with the current one (202001 to 201903, 2829 1.716 LT  "", false for ALL elements, leading to 2838 1.722 JMPIFNOT 4500 "E\x00")
compare them again (2915 1.728 NUMEQUAL  "", false for all elements except one (!!!) leading to 2924 1.734 JMPIFNOT 3d01 "=\x01"), the one equal gets additional processing outlined below
pick the third element (balance?<PHONE_NUMBER>000) and compare it to zero (3247 1.738 LTE  "", always FALSE, leading to 3258 1.744 JMPIFNOT 0600 "\x06\x00")
sum this third value to accumulator (3272 1.75 ADD  "", increasing over time obviously)
move on to the next element

NUMEQUALed element:
            {
                "type": "Array",
                "value": [
                    {
                        "type": "Integer",
                        "value": "201904"
                    },
                    {
                        "type": "Integer",
                        "value": "201903"
                    },
                    {
                        "type": "Integer",
                        "value": "260000000000"
                    },
                    {
                        "type": "Map",
                        "value": [
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "6"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "7"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "8"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "9"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "10"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "11"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "12"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "13"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "14"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "15"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "16"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "17"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "18"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "19"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "20"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "21"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "22"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "23"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "24"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "25"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "26"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "27"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "28"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "29"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "30"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            },
                            {
                                "key": {
                                    "type": "Integer",
                                    "value": "31"
                                },
                                "value": {
                                    "type": "ByteArray",
                                    "value": "00e40b5402"
                                }
                            }
                        ]
                    }
                ]
            }

Additional processing for it:

get a map from element (`2939 1.858 PICKITEM  "")
get its keys (`2940 1.859 KEYS  "")
loop the the keys (3034 1.871 ARRAYSIZE  "" and 3035 1.872 LT  "")
pick Nth key
compare it to previously stored day (2974 1.886 LTE  "", 6 in our case)
the first value (6) has true outcome, so it skips jump on 2983 1.892 JMPIFNOT 1000 "\x10\x00" and this key gets removed from the map (2994 1.898 REMOVE  "")
other keys compare to false at 2974 and jump to 2999 at 2983
map values for these keys get summed up at 3011 1.94 ADD  ""

The end result is that one KV pair is filtered out from the map and we get accumulated value sum that is compared against the one stored previously in array at index 2:
estack [
    {
        "type": "Integer",
        "value": "250000000000"
    },
    {
        "type": "Integer",
        "value": "260000000000"
    }
]
3047 3.018 NUMNOTEQUAL  ""

estack [
    {
        "type": "Boolean",
        "value": true
    }
]

This leads to jump:
estack [
    {
        "type": "Boolean",
        "value": true
    }
]
3056 3.024 JMPIFNOT b800 "\xb8\x00"

and update of the "balance" value in this array. Comparison to zero:
estack [
    {
        "type": "Integer",
        "value": "250000000000"
    }
]
3074 3.034 PUSH0  ""

estack [
    {
        "type": "Integer",
        "value": "250000000000"
    },
    {
        "type": "ByteArray",
        "value": ""
    }
]
3075 3.034 LTE  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]

And update to the storage:
3153 3.041 SYSCALL 4e656f2e53746f726167652e476574436f6e74657874 "Neo.Storage.GetContext"
10440 3.045 PUSHBYTES8 6c6f636b7570735f "lockups_"

prepare key: add key and 201903 ("6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0af1403")
3195 3.057 SYSCALL 4e656f2e52756e74696d652e53657269616c697a65 "Neo.Runtime.Serialize"
3221 3.059 SYSCALL 4e656f2e53746f726167652e507574 "Neo.Storage.Put"

Another comparison:
estack [
    {
        "type": "Integer",
        "value": "250000000000"
    },
    {
        "type": "ByteArray",
        "value": ""
    }
]
3247 4.062 LTE  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]
3258 4.068 JMPIFNOT 0600 "\x06\x00"

And summing it at 3272 (back to original Storage.Find iterator).
I don't see how any of this could be affected by the order of elements. Technically, reverse order experiment proves that. So maybe it's not #822's friend after all.

Also, given the GAS amount spent by C# node it probably has no problems doing all of these iterations too, so something happens afterwards.

Previously computed sum gets compared to zero:
3318 4.384 PUSH0  ""

estack [
    {
        "type": "Integer",
        "value": "7962200000000"
    },
    {
        "type": "ByteArray",
        "value": ""
    }
]
3319 4.384 LT  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]
...
3330 4.39 JMPIFNOT 0d00 "\r\x00"

But that jump point was already analyzed before.

estack [
    {
        "type": "Integer",
        "value": "10000000000"
    },
    {
        "type": "ByteArray",
        "value": "00ca9a3b"
    }
]
9267 4.417 LT  ""

estack [
    {
        "type": "Boolean",
        "value": false
    }
]

This<PHONE_NUMBER>0 value is not a magic actually, it's the result of
estack [
    {
        "type": "ByteArray",
        "value": "002a262c4007"
    },
    {
        "type": "Integer",
        "value": "7962200000000"
    }
]
9254 4.409 SUB  ""

estack [
    {
        "type": "Integer",
        "value": "10000000000"
    }
]

The first value is a balance got from
10424 1.043 PUSHBYTES8 62616c616e63655f "balance_"
...
10679 1.098 CAT  ""

estack [
    {
        "type": "ByteArray",
        "value": "62616c616e63655f00"
    }
]
...
10683 1.101 CAT  ""

estack [
    {
        "type": "ByteArray",
        "value": "62616c616e63655f00937d87615f1a9d839388b88b0692f402262e9cf0"
    }
]
...
10698 1.11 SWAP  ""

estack [
    {
        "type": "ByteArray",
        "value": "62616c616e63655f00937d87615f1a9d839388b88b0692f402262e9cf0"
    },
    {
        "type": "InteropInterface",
        "value": null
    }
]
10699 1.111 SYSCALL 4e656f2e53746f726167652e476574 "Neo.Storage.Get"

estack [
    {
        "type": "ByteArray",
        "value": "002a262c4007"
    }
]

So it's a sender's balance. Looks like we subtract some locked amount out of it and then compare amount to transfer with this unlocked value, it's 10 to transfer vs 100 available, so it should work.

C# node fails here:
      9276 JMPIFNOT    System.Byte[]
      9279 NOP
      9280 39    System.Byte[]
      9320 NOP
      9321 SYSCALL    System.Byte[]

(and then runs to return and THROWIFNOT). Which is
9280     PUSHBYTES39        5472616e73666572206973206661696c65642e2066726f6d42616c616e6365203c2076616c7565 ("Transfer is failed. fromBalance < value")

Though the first difference in execution flow occurs a bit earlier at
Ours:
3308 DUPFROMALTSTACK
3309 PUSHBYTES1
3311 PICKITEM
3312 JMPIF
3315 DUPFROMALTSTACK
3316 PUSH1
3317 PICKITEM
3318 PUSH0
3319 LT
3320 DUPFROMALTSTACK
3321 PUSHBYTES1
3323 PUSH2
3324 ROLL
3325 SETITEM

Theirs:
      3308 DUPFROMALTSTACK
      3309 PUSHBYTES1    System.Byte[]
      3311 PICKITEM
      3312 JMPIF    System.Byte[]
      2765 NOP
      2766 DUPFROMALTSTACK
      2767 PUSH6
      2768 PICKITEM
      2769 NOP
      2770 SYSCALL    System.Byte[]
      2790 NOP
      2791 SYSCALL    System.Byte[]
      2816 DUPFROMALTSTACK
      2817 PUSH7
      2818 PUSH2

C# VM returns nine elements when iterating over lockups_$KEY, while neo-go only returns eight.
Theirs:
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-11-15-03 : 80-04-02-03-12-15-03-02-03-11-15-03-02-06-40-66-74-8A-22-01-82-01-02-01-05-02-06-40-66-74-8A-22-01
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-12-15-03 : 80-04-02-01-00-02-03-12-15-03-02-06-40-66-74-8A-22-01-82-01-02-01-05-02-06-40-66-74-8A-22-01
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-AF-14-03 : 80-04-02-03-B0-14-03-02-03-AF-14-03-02-05-00-28-35-89-3C-82-1A-02-01-06-00-05-00-E4-0B-54-02-02-01-07-00-05-00-E4-0B-54-02-02-01-08-00-05-00-E4-0B-54-02-02-01-09-00-05-00-E4-0B-54-02-02-01-0A-00-05-00-E4-0B-54-02-02-01-0B-00-05-00-E4-0B-54-02-02-01-0C-00-05-00-E4-0B-54-02-02-01-0D-00-05-00-E4-0B-54-02-02-01-0E-00-05-00-E4-0B-54-02-02-01-0F-00-05-00-E4-0B-54-02-02-01-10-00-05-00-E4-0B-54-02-02-01-11-00-05-00-E4-0B-54-02-02-01-12-00-05-00-E4-0B-54-02-02-01-13-00-05-00-E4-0B-54-02-02-01-14-00-05-00-E4-0B-54-02-02-01-15-00-05-00-E4-0B-54-02-02-01-16-00-05-00-E4-0B-54-02-02-01-17-00-05-00-E4-0B-54-02-02-01-18-00-05-00-E4-0B-54-02-02-01-19-00-05-00-E4-0B-54-02-02-01-1A-00-05-00-E4-0B-54-02-02-01-1B-00-05-00-E4-0B-54-02-02-01-1C-00-05-00-E4-0B-54-02-02-01-1D-00-05-00-E4-0B-54-02-02-01-1E-00-05-00-E4-0B-54-02-02-01-1F-00-05-00-E4-0B-54-02
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-B0-14-03 : 80-04-02-03-B5-14-03-02-03-B0-14-03-02-05-00-60-1D-E1-37-82-18-02-01-01-00-05-00-E4-0B-54-02-02-01-02-00-05-00-E4-0B-54-02-02-01-03-00-05-00-E4-0B-54-02-02-01-04-00-05-00-E4-0B-54-02-02-01-05-00-05-00-E4-0B-54-02-02-01-06-00-05-00-E4-0B-54-02-02-01-07-00-05-00-E4-0B-54-02-02-01-08-00-05-00-E4-0B-54-02-02-01-09-00-05-00-E4-0B-54-02-02-01-0A-00-05-00-E4-0B-54-02-02-01-0B-00-05-00-E4-0B-54-02-02-01-0C-00-05-00-E4-0B-54-02-02-01-0D-00-05-00-E4-0B-54-02-02-01-0E-00-05-00-E4-0B-54-02-02-01-0F-00-05-00-E4-0B-54-02-02-01-10-00-05-00-E4-0B-54-02-02-01-11-00-05-00-E4-0B-54-02-02-01-12-00-05-00-E4-0B-54-02-02-01-13-00-05-00-E4-0B-54-02-02-01-14-00-05-00-E4-0B-54-02-02-01-15-00-05-00-E4-0B-54-02-02-01-16-00-05-00-E4-0B-54-02-02-01-17-00-05-00-E4-0B-54-02-02-01-18-00-05-00-E4-0B-54-02
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-B5-14-03 : 80-04-02-03-B6-14-03-02-03-B5-14-03-02-06-80-04-01-CC-20-01-82-01-02-01-05-02-06-80-04-01-CC-20-01
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-B6-14-03 : 80-04-02-03-B7-14-03-02-03-B6-14-03-02-06-80-04-01-CC-20-01-82-01-02-01-05-02-06-80-04-01-CC-20-01
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-B7-14-03 : 80-04-02-03-B8-14-03-02-03-B7-14-03-02-06-40-66-74-8A-22-01-82-01-02-01-05-02-06-40-66-74-8A-22-01
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-B8-14-03 : 80-04-02-03-11-15-03-02-03-B8-14-03-02-06-40-66-74-8A-22-01-82-01-02-01-05-02-06-40-66-74-8A-22-01
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-AF-14-03 : 80-04-02-03-B0-14-03-02-03-AF-14-03-02-05-00-44-29-35-3A-82-19-02-01-07-00-05-00-E4-0B-54-02-02-01-08-00-05-00-E4-0B-54-02-02-01-09-00-05-00-E4-0B-54-02-02-01-0A-00-05-00-E4-0B-54-02-02-01-0B-00-05-00-E4-0B-54-02-02-01-0C-00-05-00-E4-0B-54-02-02-01-0D-00-05-00-E4-0B-54-02-02-01-0E-00-05-00-E4-0B-54-02-02-01-0F-00-05-00-E4-0B-54-02-02-01-10-00-05-00-E4-0B-54-02-02-01-11-00-05-00-E4-0B-54-02-02-01-12-00-05-00-E4-0B-54-02-02-01-13-00-05-00-E4-0B-54-02-02-01-14-00-05-00-E4-0B-54-02-02-01-15-00-05-00-E4-0B-54-02-02-01-16-00-05-00-E4-0B-54-02-02-01-17-00-05-00-E4-0B-54-02-02-01-18-00-05-00-E4-0B-54-02-02-01-19-00-05-00-E4-0B-54-02-02-01-1A-00-05-00-E4-0B-54-02-02-01-1B-00-05-00-E4-0B-54-02-02-01-1C-00-05-00-E4-0B-54-02-02-01-1D-00-05-00-E4-0B-54-02-02-01-1E-00-05-00-E4-0B-54-02-02-01-1F-00-05-00-E4-0B-54-02

Ours:
6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0111503 :<PHONE_NUMBER>1503020311150302064066748a2201820102010502064066748a2201
6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0121503 :<PHONE_NUMBER>020312150302064066748a2201820102010502064066748a2201
6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0af1403 : 80040203b014030203af14030205002835893c821a020106000500e40b5402020107000500e40b5402020108000500e40b5402020109000500e40b540202010a000500e40b540202010b000500e40b540202010c000500e40b540202010d000500e40b540202010e000500e40b540202010f000500e40b5402020110000500e40b5402020111000500e40b5402020112000500e40b5402020113000500e40b5402020114000500e40b5402020115000500e40b5402020116000500e40b5402020117000500e40b5402020118000500e40b5402020119000500e40b540202011a000500e40b540202011b000500e40b540202011c000500e40b540202011d000500e40b540202011e000500e40b540202011f000500e40b5402
6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0b01403 : 80040203b514030203b01403020500601de1378218020101000500e40b5402020102000500e40b5402020103000500e40b5402020104000500e40b5402020105000500e40b5402020106000500e40b5402020107000500e40b5402020108000500e40b5402020109000500e40b540202010a000500e40b540202010b000500e40b540202010c000500e40b540202010d000500e40b540202010e000500e40b540202010f000500e40b5402020110000500e40b5402020111000500e40b5402020112000500e40b5402020113000500e40b5402020114000500e40b5402020115000500e40b5402020116000500e40b5402020117000500e40b5402020118000500e40b5402
6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0b51403 : 80040203b614030203b514030206800401cc200182010201050206800401cc2001
6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0b61403 : 80040203b714030203b614030206800401cc200182010201050206800401cc2001
6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0b71403 : 80040203b814030203b7140302064066748a2201820102010502064066748a2201
6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0b81403 :<PHONE_NUMBER>15030203b8140302064066748a2201820102010502064066748a2201

And the last value:
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-AF-14-03 : 80-04-02-03-B0-14-03-02-03-AF-14-03-02-05-00-44-29-35-3A-82-19-02-01-07-00-05-00-E4-0B-54-02-02-01-08-00-05-00-E4-0B-54-02-02-01-09-00-05-00-E4-0B-54-02-02-01-0A-00-05-00-E4-0B-54-02-02-01-0B-00-05-00-E4-0B-54-02-02-01-0C-00-05-00-E4-0B-54-02-02-01-0D-00-05-00-E4-0B-54-02-02-01-0E-00-05-00-E4-0B-54-02-02-01-0F-00-05-00-E4-0B-54-02-02-01-10-00-05-00-E4-0B-54-02-02-01-11-00-05-00-E4-0B-54-02-02-01-12-00-05-00-E4-0B-54-02-02-01-13-00-05-00-E4-0B-54-02-02-01-14-00-05-00-E4-0B-54-02-02-01-15-00-05-00-E4-0B-54-02-02-01-16-00-05-00-E4-0B-54-02-02-01-17-00-05-00-E4-0B-54-02-02-01-18-00-05-00-E4-0B-54-02-02-01-19-00-05-00-E4-0B-54-02-02-01-1A-00-05-00-E4-0B-54-02-02-01-1B-00-05-00-E4-0B-54-02-02-01-1C-00-05-00-E4-0B-54-02-02-01-1D-00-05-00-E4-0B-54-02-02-01-1E-00-05-00-E4-0B-54-02-02-01-1F-00-05-00-E4-0B-54-02

Is actually the one formed by the script while it's running:
estack [
    {
        "type": "ByteArray",
        "value": "80040203b014030203af14030205004429353a8219020107000500e40b5402020108000500e40b5402020109000500e40b540202010a000500e40b540202010b000500e40b540202010c000500e40b540202010d000500e40b540202010e000500e40b540202010f000500e40b5402020110000500e40b5402020111000500e40b5402020112000500e40b5402020113000500e40b5402020114000500e40b5402020115000500e40b5402020116000500e40b54020
20117000500e40b5402020118000500e40b5402020119000500e40b540202011a000500e40b540202011b000500e40b540202011c000500e40b540202011d000500e40b540202011e000500e40b540202011f000500e40b5402"
    },
    {
        "type": "ByteArray",
        "value": "6c6f636b7570735f937d87615f1a9d839388b88b0692f402262e9cf0af1403"
    },
    {
        "type": "InteropInterface",
        "value": null
    }
]
3221 3.059 SYSCALL 4e656f2e53746f726167652e507574 "Neo.Storage.Put"

Which already was processed as an item number three before (same key):
6C-6F-63-6B-75-70-73-5F-93-7D-87-61-5F-1A-9D-83-93-88-B8-8B-06-92-F4-02-26-2E-9C-F0-AF-14-03 : ...

It's just crazy.

And yes, IT IS in fact a friend of #822. Hooray!

Fixed by #992.


urlrewriter doesn't work

Hi!
I have such issue and i don't know, why it doesn't work.
Urlrewriter yml settings:
`urlrewrite:
  kinozal:
    regexp: 'https://kinozal.tv/details.php\?id=(?P<id>\d+)'
    format: 'https://dl.kinozal.tv/download.php?id=\g<id>'`

the piece of rss feed:
          `
          <item>
              <title>Blue Bloods </title>
              <link>https://kinozal.tv/details.php?id=1936533</link>
              <category>46</category>
              <guid>https://kinozal.tv/details.php?id=1936533</guid>
              <pubDate>Wed, 18 Jan 2023 19:11:42 +0300</pubDate>
          </item>
          `

So when the flexget executes, the debug shows only replacing of guid field and title (because i use the field "guid" as the title) field. No one record with urlrewrite plugin:
DEBUG    manipulate    kinozal         field: `title` from_field: `title` field_value: `1936533`
DEBUG    manipulate    kinozal         field `title` after replace: `1936533`
DEBUG    manipulate    kinozal         field: `guid` from_field: `guid` field_value: `https://dl.kinozal.tv/download.php?id=1936533`
DEBUG    manipulate    kinozal         field `guid` after replace: `https://dl.kinozal.tv/download.php?id=1936533`
<...>
VERBOSE  task          kinozal         REJECTED: `1936533` by retry_failed plugin because waiting before retrying entry which has failed in the past. (failure reason: Unexpected html content received from `https://kinozal.tv/details.php?id=1936533` - maybe a login page?)

I've tried to force the field "guid" as the "link", but with no result.

    format: 'https://dl.kinozal.tv/download.php?id=\g<id>'`

DEBUG    manipulate    kinozal         field `guid` after replace: `https://dl.kinozal.tv/download.php?id=1936533`

Looks like it's working. Maybe urlrewrite is just lacking some log output?

    format: 'https://dl.kinozal.tv/download.php?id=\g<id>'`

DEBUG    manipulate    kinozal         field `guid` after replace: `https://dl.kinozal.tv/download.php?id=1936533`

Looks like it's working. Maybe urlrewrite is just lacking some log output?

Unfortunally, no. This is a result of "manipulate" function, which works with "guid" field. I've made the same transform for this to check my regexp rule for "urlrewrite". So the rule makes the proper transform, but urlrewriter doesn't want to work.
In case of "urlrewriter" there should be "urlrewrite" instead of "manipulate" in the log, but there is no such word in my log.

Maybe the link tag isn't being mapped properly to the url field?
tasks:
  test:
    mock:
      - { title: 'Blue Bloods', url: 'https://kinozal.tv/details.php?id=1936533'}
    accept_all: yes
    urlrewrite:
      kinozal:
        regexp: 'https://kinozal.tv/details.php\?id=(?P<id>\d+)'
        format: 'https://dl.kinozal.tv/download.php?id=\g<id>'

--test execute --dump accepted eval
2023-01-19 00:45:11 INFO     manager                       Test mode, creating a copy from database ...
2023-01-19 00:45:13 VERBOSE  manager                       Creating new database C:\Users\BrutuZ\flexget\test-test.sqlite - DO NOT INTERRUPT ...
2023-01-19 00:45:15 VERBOSE  task_queue                    There are 3 tasks to execute. Shutdown will commence when they have completed.
2023-01-19 00:45:15 VERBOSE  details       test            Produced 1 entries.
2023-01-19 00:45:15 VERBOSE  task          test            ACCEPTED: `Blue Bloods` by accept_all plugin
2023-01-19 00:45:15 INFO     urlrewriter   test            Entry 'Blue Bloods' URL rewritten to https://dl.kinozal.tv/download.php?id=1936533 (with urlrewrite)
2023-01-19 00:45:15 VERBOSE  details       test            Summary - Accepted: 1 (Rejected: 0 Undecided: 0 Failed: 0)
2023-01-19 00:45:15 WARNING  task          test            Task doesn't have any output plugins, you should add (at least) one!
─── Accepted ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
title         : Blue Bloods
url           : https://dl.kinozal.tv/download.php?id=1936533
original_url  : https://kinozal.tv/details.php?id=1936533
accepted_by   : accept_all
media_id      : None
original_title: Blue Bloods
quality       : unknown
task          : test

2023-01-19 00:45:16 INFO     manager                       Removed test database

Thanks for help and reply!
i've tried your test config and my config with the option "accept_all", and urlrewriter changed all urs using my format. So i think, that the problem is in my series list, because as i have understood, urlrewrite works only for accepted series, so i'll try to dig into this way.

I don't know why, but now it's working. Maybe it was a mistake in rss file.


Max File Size

Add details on max file size supported
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f2957a41-0ebd-4f1e-6f9c-d4f9173d4630
Version Independent ID: e92921f7-9899-6a70-412f-f6094e772271
Content: How to use Secure File Exchange to exchange files with Microsoft Support - Azure
Content Source: support/azure/general/secure-file-exchange-transfer-files.md
Service: storage
GitHub Login: @genlin
Microsoft Alias: genli

@danmyhre, Thanks for the question. I will check it with our engineers team.

@danmyhre The file size limit in Secure File Exchange is 100Gb per file. I will also add this information to the article.


Manager folder structure in allure test Ops

It's more likely a evolution rather than a bug, but :
When using Shelex plugin, we have an organization of our test through describe and it.

The folder structure is compose from the different describe and it function :

When switching to your library, we've lost this structure :

To see this structure, you need to use the "Suites" section on a launch (in the "Tree" tab)

Any advice on how to retrieve this type of organization ?

Hello @jeremie-val, the structure should be the same in your allure report
Here is example report: https://mmisty.github.io/cypress-allure-adapter-example/#suites/4cbe1681a5869c86fbcf55b2b7d6abe3/494d8b86f8774008/
For Allure Testops I added tree structure in project like:

To do so:
In administration section -> Custom Fields you need to add Parent suite, Sub suite and Suite
In project administration -> Custom Fields you need to add mapping for these fileds:

And after that you can update tree settings on Trees tab for project to:

@jeremie-val added this into documentation https://github.com/mmisty/cypress-allure-adapter/blob/main/README.pack.md#suites-tree

Thank you @mmisty
So I need to update our tests to add some cy.allure() call to add name for suite, subsuite and parentsuite.

@jeremie-val, no, you don't need to update tests - those labels are being added automatically basing on describe's structure.
You just need to update Allure Testops custom fields as wrote above.

Thanks for your reply.
On my side, if I don't add this call, I don't see the organization.
What you're telling is that if I have some describe inside another one, I should see the organization level ?

@jeremie-val right, like in example report - there is test file attached for current test on the screenshot:

You can also check your configuration  - should be similar to this (for javascript) https://github.com/mmisty/cypress-allure-adapter-example

I've seen my mistake, and now it's perfect !
Thanks :)
We can now upgrade to Cypress V13


Arrow functions, let/const, and cleanup

This introduces let/const instead of var, moves to arrow functions in some cases, removes explicit 'use strict', and cleans up a few imports.

Codecov Report

Merging #732 into master will decrease coverage by 0.08%.
The diff coverage is 94.91%.

@@            Coverage Diff             @@
##           master     #732      +/-   ##
==========================================
- Coverage   79.58%   79.49%   -0.09%
==========================================
  Files           8        6       -2
  Lines         240      239       -1
  Branches       53       53
==========================================
- Hits          191      190       -1
  Misses         30       30
  Partials       19       19

Impacted Files
Coverage Δ

lib/utils.ts
100% <ø> (ø)
:arrow_up:

lib/generator_utils.ts
60% <ø> (ø)
:arrow_up:

lib/apirequest.ts
97.33% <100%> (+0.03%)
:arrow_up:

lib/googleauth.ts
100% <100%> (ø)

lib/googleapis.ts
78.18% <100%> (ø)
:arrow_up:

lib/discovery.ts
67.64% <89.65%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e22af7...d6dbbe6. Read the comment docs.

Do you plan on switching to ES2015 classes, destructuring, etc. in a separate PR?

@jmdobry Yeah, a basic outline of my plan is in #503.  After this, next step is es6 style imports and classes.


Unable to specify a specific import from a specific module

So you provide two options:

moduleName
importName

Used like so:
// moduleName = module
import {x, y} from 'module';
x`test`; // parsed
y`test`; // parsed

// moduleName = module
// importName = y
import {x, y} from 'module';
x`test`; // parsed
y`test`; // parsed
y(whatever)`test`; // parsed
y.whatever`test`; // parsed

Surely this isn't how importName should work. I would expect only tagged templates which use the specified import name to be parsed, rather than ALL imported names and the extra styled-specific stuff.
Like this:
// moduleName = module
// importName = y
import {x, y} from 'module';
x`test`; // NOT parsed
y`test`; // parsed

With this ability we could use the same component on other tagged template css libraries. Something like LitElement. But we can't yet because we over-parse:
css`this is css`; // parsed
html`this is html`; // parsed <- WRONG, it shouldn't be

Agree with your feature request. But importName is there. We have use another option name or try to enhance it. Like single string means the old usage, and an array is used to provide names whitelist.


Changed return value for the Geocoder promise failure.

Not a huge change as mentioned in the issue but I believe it might be easier to track errors.

I am sorry, didn't merge the tests.


What's up Bro!

How's going? Your app looks interesting!

haha, you used issue tracker as a messenger? nice and sorry, it's because I don't have any contact method...indeed, my US number is still alive since I'm using the free google voice/hangout! I finally went back to Korea and working here at a small start-up. I'll call ya sometime. I guess your number isn't changed...?

haha, I'm actually here to point out you still used var once in your app and I recommend that stick to let and const. Also, you don't have to put constructor property in your class, you can do state = {} directly. Anyways, that's just minor things.

Yeah, I didn't know you are still using that number, but I heard you went back so I tried to reach you through Allo. Sorry I've been very busy this year and I haven't contacted you for months until I heard you went back, I hope you were doing well. But I'm glad you got the chance to start coding again and yes I'm still using the same number.

Haha, actually I'm using let and const only these days, this project is actually done quite a long ago, had a permission issue due to my personal account(this one) and my company account of github and gh-pages default settings so that I had to re-init this repo. The current version changed some points with using react PureComponent and etc. I'm working at Korea now cuz couldn't resolved the visa issue. I'll go back to the US sometime later though, definitely. I'll contact you later with your 469 number!


About how to display the title of script panels

Is your feature request related to a problem? Please describe.
I'm always frustrated when I open many panels , many script panels, table panels, it just only can display the connect database.
For example: <Postgre.Em...  <Postgre.Em...  <Postgre.Em...
I can't distinguish between these files.
Describe the solution you'd like
to only display the file name is OK, the connect database has showed in toolbar.
Describe alternatives you've considered
the connected database can appears in the tip or after the filename.

Hello @upaccount,
You can change tab names for scripts here:

Please let me know if it solves your issue.

yes, it can work, thanks a lot


Remove WL_HIDE_DEPRECATED

From the wayland-devel mailing list: [RFC wayland] wayland-server: Finally remove deprecated struct wl_buffer definition
We don't use it anyway, so we should remove WL_HIDE_DEPRECATED from the build options.

Damn, I misunderstood what this WL_HIDE_DEPRECATED is for. It's actually hiding struct definitions, i was thinking it was exposing us more structs.


Can't build Material.Core

Hi there,
Don't know how to get MaterialColor.Core to compile as of 9/18 from dev branch, is it based off a different version? I haven't looked at the commits to compare, feel free to criticize me for trying to compile it on build 232512 if it isn't compatible. :disappointed:
Thanks for this great tool. :grinning:
I've got this error here in VS 2017:
------ Build started: Project: MaterialColor.Core, Configuration: Release Any CPU ------
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\InjectionEntry.cs(111,34,111,47): error CS1061: 'BlockTileRenderer' does not contain a definition for 'highlightCell' and no extension method 'highlightCell' accepting a first argument of type 'BlockTileRenderer' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\InjectionEntry.cs(113,33,113,45): error CS1061: 'BlockTileRenderer' does not contain a definition for 'selectedCell' and no extension method 'selectedCell' accepting a first argument of type 'BlockTileRenderer' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\Helpers\ColorHelper.cs(44,60,44,75): error CS1061: 'StorageLocker' does not contain a definition for 'filteredStorage' and no extension method 'filteredStorage' accepting a first argument of type 'StorageLocker' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\Helpers\ColorHelper.cs(52,33,52,42): error CS1061: 'Ownable' does not contain a definition for 'ownedTint' and no extension method 'ownedTint' accepting a first argument of type 'Ownable' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\Helpers\ColorHelper.cs(53,33,53,44): error CS1061: 'Ownable' does not contain a definition for 'unownedTint' and no extension method 'unownedTint' accepting a first argument of type 'Ownable' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\Helpers\ColorHelper.cs(54,33,54,43): error CS1061: 'Ownable' does not contain a definition for 'UpdateTint' and no extension method 'UpdateTint' accepting a first argument of type 'Ownable' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\Helpers\ColorHelper.cs(62,64,62,79): error CS1061: 'RationBox' does not contain a definition for 'filteredStorage' and no extension method 'filteredStorage' accepting a first argument of type 'RationBox' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\Helpers\ColorHelper.cs(70,65,70,80): error CS1061: 'Refrigerator' does not contain a definition for 'filteredStorage' and no extension method 'filteredStorage' accepting a first argument of type 'Refrigerator' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\Helpers\ColorHelper.cs(97,21,97,31): error CS1061: 'FilteredStorage' does not contain a definition for 'filterTint' and no extension method 'filterTint' accepting a first argument of type 'FilteredStorage' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\Helpers\ColorHelper.cs(98,21,98,33): error CS1061: 'FilteredStorage' does not contain a definition for 'noFilterTint' and no extension method 'noFilterTint' accepting a first argument of type 'FilteredStorage' could be found (are you missing a using directive or an assembly reference?)
C:\Program Files (x86)\Steam\steamapps\common\OxygenNotIncluded\OxygenNotIncluded_Data\MaterialColor.Core\InjectionEntry.cs(143,41,143,50): error CS0117: 'INPUT_BINDINGS.ROOT' does not contain a definition for 'OVERLAY12'
For those whom are trying to build the tool, barring MaterialColor.Core of the dev branch until more information is recieved, here's my convoluted way :fried_egg: :
I had a lot of difficulty figuring out the layout needed to build this all, putting the files from the master into the data folder, then copying the managed folder and renaming it to GameManaged (or change it to Managed in the csproj files.) then also copying the original Assembly-CSharp.dll & UnityEngine.dll and creating a folder "libs/original" in the "tools" folder which you extracted from the master into the data folder, copy those .dll's into that folder. Also, you will need to download the onion-patcher source and extract it (the root files, keep the folder with it, do not paste files without maintaining the folder structure in the source), then you need to go to "onion-hooks/onionhooks" and edit "OnionHooks.csproj" change the hintpaths with the .dll's to include "....\Managed\dllname.dll" OR if you didn't change the  of MaterialColor's various .csproj files, you would have made a copy of "Managed" and renamed it to "GameManaged" so you would need to change in "OnionHooks,csproj to be "....\GameManaged\dllname.dll", for anyone wondering how. :8ball:

@L-a-n-g-o-l-i-e-r-s You should have first checked https://github.com/fistak/MaterialColor/blob/master/BUILDING.md.
Yeah the help pages are not ready yet, I need to clean up a little. As I can see the most errors if not all are caused by wrong .dll in the GameManaged.
If you follow the building guide, you can see it requires a patched libraries to work, It's like that because I need to make several fields and methods public and then I build against that.
I'm glad someone is actually interested in the code. Feel free to ask if you still have any issues ;)


Page demos problems in Firefox 44

When using the first input in the page https://leaverou.github.io/awesomplete/ it shows as this (double tooltip):

then after selecting the first item:

and down with the combobox dropdown, the toggle is misaligned

Awesomplete was included twice by mistake. This created 2 completer instances. Fixed in 6c20ebe

Closing this one since the first bug is fixed and second one is in separate issue now #16838

:+1:

This brings up an issue though.
Should Awesomplete check if an input is already initialized before
initializing?
Could be done by checking the Awesomplete.all array
On Sun, Jan 31, 2016, 12:34 Vladislav Zarakovsky<EMAIL_ADDRESS>wrote:

Closing this one since the first bug is fixed and second one is in
separate issue now #16838
https://github.com/LeaVerou/awesomplete/issues/16838
—
Reply to this email directly or view it on GitHub
https://github.com/LeaVerou/awesomplete/issues/16836#issuecomment-177461281
.

Yes.

I’m not so sure. It introduces a performance overhead on every use for little benefit (since including it twice is essentially the author's bug).
I'm not necessarily saying no, I'm saying "yes" is not that obvious to me.

Not necessarily performance overhead. Including script twice is an obvious error. Creating new instance for input, which already has awesomplete maybe not.
Anyways, won't implement if it adds significant performance overhead or complicates code to much.

I think the easiest way to do this is to check is input is the same as
one of the inputs in _.all just before element creation.
I don't think the performance overhead should be significant, as everything
is already cached, so there is no unneeded DOM querying.
I think the check can probably be done pretty neatly with _.all.reduce()
On Mon, Feb 1, 2016, 18:50 Vladislav Zarakovsky<EMAIL_ADDRESS>wrote:

Not necessarily performance overhead. Including script twice is an obvious
error. Creating new instance for input, which already has awesomplete maybe
not.
Anyways, won't implement if it adds significant performance overhead or
complicates code to much.
—
Reply to this email directly or view it on GitHub
https://github.com/LeaVerou/awesomplete/issues/16836#issuecomment-178064050
.

Why reduce and not indexOf?

  Stop emailing me
Thank you,
Stacey

On Feb 4, 2016, at 7:23 PM, Lea Verou<EMAIL_ADDRESS>wrote:
Why reduce and not indexOf?
—
Reply to this email directly or view it on GitHub.

LOL, Stacey, nobody is emailing you. You (or someone using your email) has subscribed to this conversation. Just press unsubscribe.

I would have 3,823 emails ago.  There is no unsubscribe.  And thank you for not taking my message personally.  Apple should allow blocking of email rather than just junk
Thank you,
Stacey

On Feb 4, 2016, at 7:25 PM, Lea Verou<EMAIL_ADDRESS>wrote:
LOL, Stacey, nobody is emailing you. You (or someone using your email) has subscribed to this conversation. Just press unsubscribe.
—
Reply to this email directly or view it on GitHub.

The notifications you are getting are automated for every message posted on this conversation. It's not an email conversation, the emails are just notifications that you can reply to. The actual conversation is on the website. Note the "View it on Github" link under every message? That takes you to the website.
However, to unsubscribe, I imagine you need to log in, so if you didn't register, you need to figure out who did using your email.

Lea you radiate professionalism left and right! Well done.

You could either use reduce or all.map().indexOf().
You can't use indexOf() directly, because Awesomplete.all is an array of objects, each with a property of input, which is the HTML element

Yes, that's what I meant. I think it would be more readable than reduce.

Sure thing. Want me to submit a PR?

Eh, why not. :)

The short answer would be - tests. I need to figure out a clean way to test Awesomplete's addition via script tag to the page. This is pretty much the only part not covered by tests yet.


Support dilated convolutions in converter

What do these changes do?
@koenhelwegen noticed that we currently do not correctly convert dilated convolutions since they may be represented using SpaceToBatchND on the TF side instead of properly set dilation arguments.
This PR copies the ConvertTFDilatedConvOp pattern from the TFPass to the LCEPass so it happens earlier which allows us to properly convert dilated binary convolutions.
How Has This Been Tested?
mlir tests

Agreed, LGTM when an end2end test is added. Ideally two of them, one for which TF uses SpaceToBatch and one where TF doesn't. Would that be possible, or can we not control when TF does that?

I don't think that adding an end2end test will help much in this case since even before that PR the network ran properly with TFLite (just without our op) so dilated binary convolutions would just translate Bsign and Conv2D which wouldn't be caught by the end2end tests. I manually verified that with this PR I can properly convert BinaryDenseNet37Dilated though.

Ah okay I see what you mean, interesting. I guess you could hackily verify this by asserting a max length of the flatbuffer, as if it's not all bconvs the weights will be much bigger. But that's ugly and brittle, and as this isn't an issue that would affect accuracy I think you're right that manual verification is fine for now.

Rebased and resolved the merge conflicts 🚀


Fix clicking on the ingredient analysis view

Description
Fix clicking on the ingredient analysis view
Related issues

#4224

can we merge @naivekook @VaiTon ?

@teolemon yeap, ship it


HTTP proxy support

currently, HTTP_PROXY, HTTPS_PROXY and NO_PROXY env variables are not passed from steampipe's environment to the plugin. is there a way to incorporate that in, or have a configuration item to set the proxy.
Thanks.

Hi.
Thanks for your quick response.
I'm keen to run steampipe behind a HTTP proxy by setting HTTP_PROXY environment variable in bash. At the moment, I'm seeing that steampipe itself (eg updating plugins etc) works fine but each plugin's connection doesn't go through the same HTTP proxy and the attempts are always direct.
if the plugins can inherit the environment variables of steampipe itself, that could potentially solve the issue.
hopefully that clarifies :)

Apologies for the radio silence on this issue @mosajjal.
The idea sounds good, I think this needs more design-level discussion in the https://github.com/turbot/steampipe repo, hence transferring the issue 👍.
@kaidaguerre @johnsmyth thoughts?


Camera tweaks, models update, money

Just a update

Looks good to me. Might be worth finishing the command functionality before the pull request though.


Write tests for LocalGcdHelper and RemoteGcsHelper

Since these classes were moved into production, it'd be good to write tests for these classes.  Users may have more expectations for this code since it was moved to the production package.  Also, our test coverage may be limited without these tests.

@ajkannan Makes sense, if you want I would be happy to help unit-testing RemoteGcsHelper.

That'd be great @mziccard, thanks!


Update wbb.p4info.pb.txt

Pull Request Functional Test Report for #2146 / 7209fd021abedc08e5e03a415e97aee6fcaa1328
No tests identified for validation.
Help


ACM-16131: add back the clusterclaim kind and api version for the provisioner annotation

https://issues.redhat.com/browse/ACM-16131

/cc @xiangjingli @zhujian7 @fxiang1

It looks good to me
@zhujian7  could you double review it
@dtthuynh  Please verify the klusteraddonconfig CR is created along with the managed cluster creation. That could be handled in a e2e manual test after the PR is merged. It would be better to add a e2e test automation to cover this critical case

LGTM

/assign @xiangjingli

/approve

/lgtm


Update config-settings for rate limiting

There's a followup Jira ticket to add an explanation of how the rate limiting settings affect the Mattermost instance https://mattermost.atlassian.net/browse/PLT-4406
Discussed with Christopher, and we felt that would be nice to add, particularly with our performance testing recently.

+1

@jasonblais Is that coming in separately or should we mark this PR as WIP?

It'll be separate, not part of this PR


SL Review: Remove entries of SL review form from task tab

User Story
As an ADM, I don't need to see any entries of the SL review form in the tasks tab as it adds more confusion.
Tasks

[ ] Remove entries of SL review form in the tasks tab, leave the Telework Agreements

Acceptance Criteria
when the task above is complete

SL review submitted from 24th Oct and onwards won't be displayed in the tasklist under the task tab. Changes Pushed to DEV.

Approved

tested successfully in TEST


only the 1st color setting affect

Version 1.3.1 on Chorme 113.0.5672.126, MacOS 13.3.1 (a)
the color setting seems only works the first line.
e.g. the title color only change in Development account

{
".Development.": "green",
".Production.": "red"
}

btw, no issue the same version on Firefox

@hellsp
Fixed and released it as v1.3.2. Thanks!


Too Many & Too Few End Calls

Im trying to create this exact stack however I getting an error saying:
Callback has too many calls to Iris.End() or To Few calls to Iris.End()
I tried to follow the demo you have on the docs page and then diagnose by looking at your source but I dont know why this is an issue.
Iris.Init()

	Iris:Connect(function()
		Iris.Window({"MENU", [Iris.Args.Window.NoResize] = true}, {size = Vector2.new(100, 100)})

		if Iris.Button({"Spawn"}).clicked() then

			RemotesManager.Client:Get("SpawnPlayer"):SendToServer()
			Iris.End()
		end

		Iris.End()
	end)

Iris.Button doesnt require an end.

even so, I still end up with a too many end calls error

In the case that the button is clicked, Iris.End() is called twice, instead:
		if Iris.Button({"Spawn"}).clicked() then
			   -- call server
   end
   Iris.End()
	end)

Iris.End in branching code should only happen when a branch uses break, return, continue, etc.
there is another problem, though, sendToServer yields. If the yield lasts longer than an Iris cycle, The same error will pop up.
		if Iris.Button({"Spawn"}).clicked() then
        task.spawn(function()
			        -- call server
        end)
   end
   Iris.End()
	end)

I'm going to keep this issue opened because I think the behavior when attempting to yield should be improved, and should have an intuitive error.

I'm going to keep this issue opened because I think the behavior when attempting to yield should be improved, and should have an intuitive error.

Ive made this change now: https://github.com/Michael-48/Iris/commit/e7bedd35d71196bae664f73375e6332040f6fb6e, closing the issue


Issue: ghdl:error: bound check failure at xpm_memory_base.vhd:75

You are right about this. some complex math was done to calculate the address width, while the generic is just available.


Adding events to the hero image

Promoting teacher training events alongside the hero image, and pointing to Train to teach page.
https://trello.com/c/ajUIVPWs/1722-content-update-homepage-hero-copy-to-reflect-events

@peteryates looks like a bug:


Computable links validation

In EdgeDB a computable link is indistinguishable in behavior from a regular link. Which means that just like a regular link a computable link must point to distinct targets. This means that if we cannot prove that a computable link target only contains distinct objects, we must raise a compile time error.
E.g. the following is an error:
SELECT Issue {
    foo := Issue.owner UNION User
};

To resolve the error, an explicit DISTINCT can be added:
SELECT Issue {
    foo := DISTINCT (Issue.owner UNION User)
};

In particular, Views with some defined computable links are indistinguishable from Concepts with those same links for the purposes of querying. For example, a path involving a View is guaranteed to produce distinct objects.

@elprans are we ready to close this?

This is still outstanding.

@elprans please lay out the plan to fix this for @vpetrovykh or others.

The plan would be to introduce the new inferer for distinctness and enforce it like we do cardinality.


Partially observable update

There should be three files: povec_env.py, hello_world_po.py, ppo_pogridnet.py

Merging the PR for quick edits


Refactor return type for SeriesSet

We'll build the stochastic sensitivity around this, so makes sense to change it here too. We'll need to make some minor changes to wodin to cope with this

WODIN ticket: https://mrc-ide.myjetbrains.com/youtrack/issue/mrc-3743/Use-refactored-SeriesSet-from-odin-js

Cool - bear in mind that this does not update anything in odin.api, so shout out if you start on that work so I can make that available


Can't add 3D animation event

Godot 3.1 alpha 1
I tried to add some event within a 3D animation, but there is no event button to create an event and name it , so the function name could be called in script.
Something like Unity can do for example
https://docs.unity3d.com/uploads/Main/AnimationEditorEventLine.png

Godot has a function track which is a more flexible version of what Unity provides with animation events.

Closing as the feature already exists as described by @mysticfall


Resolve AppConfiguration Test Failures

Starting on 12/12/19 Azure AppConfiguration live tests have been consistently failing. The MacOS test runs are failing consistently will deserialization issues and there are occasional failures in Linux and Windows which appear to be more transient.

Issues fixed at https://github.com/Azure/azure-sdk-for-java/pull/7837


CollapseRepartition physical optimizer

Which issue does this PR close?

Closes #41
Rationale for this change

Add repartition elimination as suggested by #41
What changes are included in this PR?

New physical optimizer to eliminate adjacent RepartitionExec nodes
Are there any user-facing changes?

Unsure if this is what is meant by #41, but I gave it a shot
There's probably more to the optimization that could be done, such as dealing with cases like having a Projection sandwiched between two repartition nodes, or cases like this:
HashJoinExec: mode=Partitioned, join_type=Inner, on=[(Column { name: "int_col", index: 0 }, Column { name: "int_col3", index: 0 })]
 *RepartitionExec: partitioning=Hash([Column { name: "int_col", index: 0 }], 12)
    HashJoinExec: mode=Partitioned, join_type=Inner, on=[(Column { name: "int_col", index: 0 }, Column { name: "int_col2", index: 0 })]
     *RepartitionExec: partitioning=Hash([Column { name: "int_col", index: 0 }], 12)
        ProjectionExec: expr=[int_col@2 as int_col, double_col@3 as double_col, CAST(date_string_col@4 AS Utf8) as alltypes_plain.date_string_col]
          FilterExec: id@0 > 1 AND CAST(tinyint_col@1 AS Float64) < double_col@3
            ParquetExec: limit=None, partitions=[home/jeffrey/Code/arrow-datafusion/parquet-testing/data/alltypes_plain.parquet], predicate=id_max@0 > 1 AND true, projection=[id, tinyint_col, int_col, double_col, date_string_col]
      RepartitionExec: partitioning=Hash([Column { name: "int_col2", index: 0 }], 12)
        ProjectionExec: expr=[int_col@0 as int_col2]
          ProjectionExec: expr=[int_col@2 as int_col, double_col@3 as double_col, CAST(date_string_col@4 AS Utf8) as alltypes_plain.date_string_col]
            FilterExec: id@0 > 1 AND CAST(tinyint_col@1 AS Float64) < double_col@3
              ParquetExec: limit=None, partitions=[home/jeffrey/Code/arrow-datafusion/parquet-testing/data/alltypes_plain.parquet], predicate=id_max@0 > 1 AND true, projection=[id, tinyint_col, int_col, double_col, date_string_col]
  RepartitionExec: partitioning=Hash([Column { name: "int_col3", index: 0 }], 12)
    ProjectionExec: expr=[int_col@0 as int_col3]
      ProjectionExec: expr=[int_col@2 as int_col, double_col@3 as double_col, CAST(date_string_col@4 AS Utf8) as alltypes_plain.date_string_col]
        FilterExec: id@0 > 1 AND CAST(tinyint_col@1 AS Float64) < double_col@3
          ParquetExec: limit=None, partitions=[home/jeffrey/Code/arrow-datafusion/parquet-testing/data/alltypes_plain.parquet], predicate=id_max@0 > 1 AND true, projection=[id, tinyint_col, int_col, double_col, date_string_col]

Where could potentially collapse the two marked RepartitionExec nodes? Unsure if that is correct.
Appreciate any feedback on this

There is a general implementation in below PR,  please take a look.
https://github.com/apache/arrow-datafusion/pull/3855
I working on split this PR to small ones now.

@Jefffrey the physical nodes have information on them (output_partitioning) that enables retrieving the child partitioning and seeing that an extra repartitioning will not change it, doing it in a more generic way wether there is a filter, projection, aggregate, join in between.
See PR from @mingmwang

I see, so should https://github.com/apache/arrow-datafusion/issues/41 be linked to https://github.com/apache/arrow-datafusion/pull/3855 as well then, if I'm understanding correctly?


beyond-identity: 2.45.0-0 -> 2.49.0-0

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Please also update source sha512 and retest the update :-)

Please also update source sha512 and retest the update :-)

Sorry for this. I changed it in my local environment, but forgot to add it here :sweat_smile:


Texture Corrupted

When i convert the texture it coverts it and its corrupted here's a example i tried to convert jd2020_logo.tga.ckd from the wii versio

n

should be fixed now


Abstract transports

As discussed in #54, this pull request takes a step in the right direction by adding an abstraction for session transports. I decided not to go for a full message based transport implementation at this time. Instead I took the first step forward which is to simply abstract out the transport and keep it stream based which is effectively what it was already being used as inside the session object. More details can be found in the commit message.
2 commits show up here. I am still trying to find the best workflow for working with github, branches, and pull requests. If you merge PR #55 first then you should be fine. Was trying to avoid piggy backing pull requests with multiple commits.

@davidchappelle I think the right way to abstract WAMP transports is not abstracting streams, but message channels. Also, I'm not sure if Sessions should be templated with the Transport they use. Since that means, Sessions are tied to Transports: eg you can't have a Session not yet know via what Transport it'll connect. Both AB JS and Py are able to use "the first working transport" from a list of transports (fallbacks). Hence I think Transport (not streams, not message channels) could be provided to a Session using ITransport like pointers.
Rgd components: yes, I agree, reducing boilerplate is a goal. FWIW, we are currently incubating a newer API in AutobahnPython (eg https://github.com/tavendo/AutobahnPython/blob/master/examples/twisted/wamp/work/newapi/test_newapi12.py) with the stated goal of bringing Python and JS in Autobahn very close, and I think it would be possible with C++ too. Means: we are looking for an Autobahn API that looks very similar (as far as possible) across different languages.
In above Python example test_newapi12, you'll recognize the use of a functional/compositional style rather than inheritance. I could imagine a C++ API where the user simply provides a function roughly like future<> my_main(_asio-loop_, Session) and just uses the provided session. The new Py API currently being finalized. We will roll out the API to Py, then JS. And then I want to give C++ another iteration.

@oberstet I think getting an abstraction in place for transports is the first step forward. Even with message channels you will need to abstract transports such that you can have message channel operate over different transports. i.e. TCP/UDS. So tackling transports first is a step forward in that direction.
I am sure that moving forward the API will continue to adapt which is to be expected. However, in the meantime the community needs to be able to use AutobahnCpp without waiting for longer term goals of the project. We are using it on a very large project and have deadlines to meet in 6 weeks time. This is why I am trying to make incremental improvements to the existing project. If the API changes date later date that is fine and we can work with that. In the meantime though we need to get it into a state where it can be used in our project.

Getting rid of the template constraint on the session is actually a big help. For example, if you have 20, 30, 40, etc components and you want to deploy them in a flexible way, having the session depend on template parameters makes this very difficult. The project I am working on is quite large which is why I am running into these types of issues. There are many ways we can make this work for small examples where templates aren't a nuisance but in my case it becomes problematic.

Even with message channels you will need to abstract transports such that you can have message channel operate over different transports.

This "stream of bytes" abstraction already exists .. it's std streams, and concrete stream transports like boost::asio::ip::tcp::socket. IMO, there is no need to wrap this again.
I think the following would be a good approach:

remove the IStream/OStream template parameters from Session
create a WAMP message-based transport abstraction

We are using it on a very large project and have deadlines to meet in 6 weeks time

I see. Our top focus is getting the API right. I suggest you move forward in your fork as you see fit for now, as I simply don't have time right now, and the API design takes time and iterations.


Links in errors

Completing the links invasion by eradicating the last remaining href outside of links.
@ethanresnick, I think about is a better relation name for this.

:+1: from me

Good call @hhware :+1:


Add support uint8, uint16, uint32, uint64 and []byte types

Thanks for proposing a new feature!
Motivation
I would like to have support of all types, which are present at the same time in Wasm and Go. No I see error: only accept int32, int64, float32, and float64.
Proposed solution
Change switches in func (imports *Imports) Append etc

WebAssembly currently only supports int32, int64, float32 and float64. There is an effort to support more types with WIT (WebAssembly Interface Types), and we are actively working on it. Since then, you have to be patient :-).

Well thank you.
Maybe for someone this link is useful:
http://webassembly.github.io/spec/core/syntax/types.html#syntax-valtype

Integers are not inherently signed or unsigned, their interpretation is determined by individual operations.


Report Grid: add support for complexity scores

Description
similar to costs
Resourcing
We intend to contribute this feature

Prematurely marked as complete


⚠ Bofrost.es has degraded performance

In 4819a06, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1548 ms

Resolved: Bofrost.es performance has improved in 93b9b6c after 6 minutes.


Map visualization

Using Mapbox GL JS.
Features:

plotting lat/long points on a map
optional dynamic clustering of points as you zoom in and out
various options to customize label on clusters and points
various ways to customize look & feel with color, style, opacity, etc.

Coverage decreased (-0.1%) to 81.286% when pulling aaa1a57ff175360f78930594569f94174e183a39 on georgeke:maps_v1 into 30da408ace200e98acb810200dc169e032f565ac on airbnb:master.

Coverage decreased (-0.1%) to 81.304% when pulling e40e68838675b2ec4c962d99d61e515f5fb1f2e9 on georgeke:maps_v1 into 30da408ace200e98acb810200dc169e032f565ac on airbnb:master.

Coverage decreased (-0.1%) to 81.298% when pulling d35d97d24e121fd0ec189d30a7d833b531b7401a on georgeke:maps_v1 into 30da408ace200e98acb810200dc169e032f565ac on airbnb:master.

Coverage decreased (-0.1%) to 81.298% when pulling 06ca7969272dd1975b15797df2913791700f19da on georgeke:maps_v1 into 30da408ace200e98acb810200dc169e032f565ac on airbnb:master.

Coverage decreased (-0.003%) to 81.294% when pulling 1fee43317d35315ecb8bf07f1f9d0475c13783e9 on georgeke:maps_v1 into 914f23432fed91c877eecc5f1a4f88c6957677b1 on airbnb:master.


WIP: [BEAM-5806] Update PubsubIO to be able to change the PubsubClientFactory

Just allow to change the PubsubClient used by PubsubIO by adding a new withClientFactory(PubsubClient.PubsubClientFactory factory) function  on PubsubIO.Read and PubsubIO.Write to set an alternative PubsubClientFactory

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

retest this please

retest this please

New commits on my branch seems to not trigger new build on this PR.

New commits on my branch seems to not trigger new build on this PR.
So I close this PR to reopen or create a new one.

It was a problem with Github:

@chamikaramj Could you please take a look at this PR? Thanks.

@chamikaramj It looks like the original author hasn't performed the update. Do you want to resolve the conflicts and squash the commit?

@lukecwik  I finally squashed my commits and merge conflicts.
I let you merge this PR when you're available.
Sorry for the time 😖
Thank's in advance.

LGTM. Thanks for the update.

Run Dataflow ValidatesRunner


Implementing mulhiui & test

Test is from the original triton core language suite modified to activate CPUBackend.

@nhat-nguyen please take a look once you have a chance, thank you!


Suggestion: Proxy Plausible Events

We are likely losing analytics data due to visitors using ad / tracker blockers.
It is possible to proxy events to plausible analytics via a proxy on the site's domain. They have a guide specifically for vercel as well.

If we agree this is okay to do, we can merge #1626


feat: add limit option to influx bucket list

Closes https://github.com/influxdata/influxdb/issues/19490
Describe your proposed changes here.

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[ ] Well-formatted commit messages
[ ] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Feature flagged (if modified API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[ ] Signed CLA (if not already signed)

I agree we should add this to all list commands. I'm not skilled enough to do that very well though.

i'm going to add this in a few more places, and add an offset option as well

Closing this since https://github.com/influxdata/influx-cli/pull/307 implemented bucket pagination in the CLI.


Implement an end-user interface to stop/start/configure/reload GoodbyeDPI

This ticket is to implement a very simple end-user interface to stop/start/configure/reload GoodbyeDPI to go in companion with #22 in order to provide a broader end-user audience.

http://rgho.st/7fDCJ2MmF

@shikulja nice.
Are you the author? Is it open source?
I translate it for you if you if you want.

i found in the forum
https://rutracker-zerkalo.appspot.com/forum/viewtopic.php?sid=hx8rmK6NuK3&t=5403670&start=240
autor is debiloid79
I'm sure that the author will not be against the translation

I implemented GUI in C++ Qt. Its features dnscrypt, schedule working hours etc. (software lang is english)
https://github.com/cheytacllc/GUI-for-GoodbyeDPI


⚠ ClamAV has degraded performance

In 339ec51, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in 1e348c2.


Translations

It's already set up to create a source strings a file for Transifex.  I just need to add a project for it and type up docs.

For most resources there is a priority language for translation (for some regions there may be two or more priority languages). It would help a lot if people can see translation requirements on transifex for each language for resources where the language is considered priority separated from other translation requirements.

For most resources there is a priority language for translation (for some regions there may be two or more priority languages). It would help a lot if people can see translation requirements on transifex for each language for resources where the language is considered priority separated from other translation requirements.

This is a good suggestion - I will see if I can push these priority languages in comments, similarly to how we push the preset terms in iD.

I'll do this after we figure out #20  (what to put in the description field)

#20 was closed via https://github.com/osmlab/osm-community-index/commit/6ec3f2a443322c7c4ac1de7789174fb31884d8e5 already.

Thanks for the reminder @manfredbrandl
I put the new translation resource here:
https://www.transifex.com/openstreetmap/id-editor/community/


Fix : Overlapping of inline codes #472

You can see one of the problem at https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-client/generating-prisma-client#the-prisma-client-npm-module
Now it's showing this way

After applying the change

Good eye - the Design team approves! 🙏 💚


The captcha error message is truncated

Issue description
When you validate the captcha and leave it to expire the error message appears truncated

Environment
Live and Development environment

OS name and version: Windows 10
Browser name and version: Chrome Version 69.0.3497.92

Reproducing the issue
https://anuas.associationadmin.org/ContactUs/index/portal/organization
User steps

Click on link
Check: I am not a robot
Switch the tab so the website is not visible
When you go back to the inactive page the captcha error will be truncated

Getting same issue :(

Could you please fix this issue?

+1

+1 still an issue

+1 this is still an issue, could we please fix this?

still

any fix for this yet?

+1

I had this issue when it expires and give that error message. I did a workaround but still is not the best solution. I have added the onExpired function and when it fires, I increased the height like so. Hope it helps anyone out there.
<ReCAPTCHA
onExpired={() => this.onExpired()}
ref={this.recaptchaRef}
/>
onExpired() {
//  I am refering to the ReCAPTCHA  iframe
const frameElement = document.getElementsByTagName('iframe');
if (frameElement && frameElement[0]) {
setTimeout(() => {
frameElement[0].height = 100;
}, 500);
}
}

Closing old issues that are not related to the PHP client code.


allow uppercase first letter for severity in GRC policies

Signed-off-by: Will Kutler<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/19496

/approve


improve validation of llm_config

Why are these changes needed?
The current llm_config validation is too restricted and excludes valid configs like #1863
Related issue number
close #1863
Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
Attention: Patch coverage is 37.50000% with 5 lines in your changes are missing coverage. Please review.

Project coverage is 13.39%. Comparing base (b0a8e6e) to head (25f328a).

Files
Patch %
Lines

autogen/agentchat/conversable_agent.py
28.57%
5 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1946       +/-   ##
===========================================
- Coverage   37.33%   13.39%   -23.95%
===========================================
  Files          64       64
  Lines        6913     6915        +2
  Branches     1519     1650      +131
===========================================
- Hits         2581      926     -1655
- Misses       4109     5976     +1867
+ Partials      223       13      -210

Flag
Coverage Δ

unittests
13.39% <37.50%> (-23.95%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@doganaktar could you test whether this PR solves your issue?

@sonichi I fixed test_register_for_llm_without_LLM()

@sonichi I fixed test_register_for_llm_without_LLM()

Thanks!

Meta point here - this issue is an argument I would use for requiring the user to actually pass in the ModelClient they want to use into the constructor of ConversableAgent. We're trying to make a generic configuration scheme fit models with varying configuration requirements.
What if instead it looked like:
from autogen import AssistantAgent, DefaultModelClientFactory
import os

llm_config = {
    "config_list": [{"model": "gpt-4", "api_key": os.environ["OPENAI_API_KEY"]}],
}
model_client = DefaultModelClientFactory.create_from_config(llm_config)

assistant = AssistantAgent("assistant", model_client=model_client)

Meta point here - this issue is an argument I would use for requiring the user to actually pass in the ModelClient they want to use into the constructor of ConversableAgent. We're trying to make a generic configuration scheme fit models with varying configuration requirements.
What if instead it looked like:
from autogen import AssistantAgent, DefaultModelClientFactory
import os

llm_config = {
    "config_list": [{"model": "gpt-4", "api_key": os.environ["OPENAI_API_KEY"]}],
}
model_client = DefaultModelClientFactory.create_from_config(llm_config)

assistant = AssistantAgent("assistant", model_client=model_client)

I am not opposed to having the model client passed in the constructor, I proposed this during the original design of the custom model feature and happy to have that be the case

Meta point here - this issue is an argument I would use for requiring the user to actually pass in the ModelClient they want to use into the constructor of ConversableAgent. We're trying to make a generic configuration scheme fit models with varying configuration requirements.
What if instead it looked like:
from autogen import AssistantAgent, DefaultModelClientFactory
import os

llm_config = {
    "config_list": [{"model": "gpt-4", "api_key": os.environ["OPENAI_API_KEY"]}],
}
model_client = DefaultModelClientFactory.create_from_config(llm_config)

assistant = AssistantAgent("assistant", model_client=model_client)

I'd like to keep user's code simple for now.

Merging for unblocking the release that many users demanded.


documentation update for splade++ huggingface -> onnx

Updated documentation for up to date e2e splade conversion to onnx (huggingface -> onnx)

@cadurosar can you please take a look at this?

@AndreSlavescu Can you also add a blurb on how to test the newly generated SPLADE++ ED model e2e? E.g., point to the repro, "swap in" the new model in ~/.cache/, etc.


Search by clicking any tech stack

On clicking any Tech stack it need to show all the projects based on that stack

I would like to take this issue. can you please assign this to me

Assigned


ERROR: Dependency "libevdev" not found, tried pkgconfig and cmake

Hi, I got an error:
Run-time dependency libevdev found: NO (tried pkgconfig and cmake)

../showmethekey-cli/meson.build:7:0: ERROR: Dependency "libevdev" not found, tried pkgconfig and cmake

A full log can be found at /tmp/showmethekey-1.7.3/build/meson-logs/meson-log.txt

But they are installed:
❯ sudo dnf install libevdev meson python3-libevdev

Last metadata expiration check: 2:20:25 ago on Sat 08 Oct 2022 11:46:39 AM WIB
.
Package libevdev-1.13.0-1.fc36.x86_64 is already installed.
Package meson-0.62.2-1.fc36.noarch is already installed.
Package python3-libevdev-0.10-1.fc36.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete

OS: Fedora Linux 36 (Workstation Edition) x86_64
Kernel: 5.19.12-200.fc36.x86_64
Shell: zsh 5.8.1
DE: GNOME 42.5
WM: Mutter

If you wants to compile some project, you also need the -devel/-dev package, which contains the headers used to compile. In Fedora I think you need libevdev-devel instead of python3-libevdev, this program does not use python.

Run-time dependency libevdev found: YES 1.13.0
Found CMake: /usr/bin/cmake (3.22.2)
Run-time dependency libudev found: NO (tried pkgconfig and cmake)

../showmethekey-cli/meson.build:8:0: ERROR: Dependency "libudev" not found, tried pkgconfig and cmake

A full log can be found at /tmp/showmethekey/build/meson-logs/meson-log.txt

❯ sudo dnf install meson libevdev libevdev-devel
Last metadata expiration check: 3:30:50 ago on Sat 08 Oct 2022 11:46:39 AM WIB.
Package meson-0.62.2-1.fc36.noarch is already installed.
Package libevdev-1.13.0-1.fc36.x86_64 is already installed.
Package libevdev-devel-1.13.0-1.fc36.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

Run-time dependency libudev found: NO (tried pkgconfig and cmake)

You may also need libudev-devel (or maybe it's in some systemd package)

Just for the record, here is everything I needed to install in order to be able to build showmethekey on Fedora:
$ sudo dnf install libevdev libudev-devel libevdev-devel libinput-devel gtk4-devel json-glib-devel

I might have missed a thing or two in between though...

@AlynxZhou if you'd be interested, I guess I could put together a corp package together, so that installing it is a bit easier for Fedora users :slightly_smiling_face:

@AlynxZhou if you'd be interested, I guess I could put together a corp package together, so that installing it is a bit easier for Fedora users slightly_smiling_face

have you created?


Romanian Accents in QuickAccent

Description of the new feature / enhancement
Quick Accent is missing the romanian diacritics for the following letters:
[ă]
[ș]
[ț]
Scenario when this would be used?
Whenever typing words in Romanian that require these sounds.
Supporting information
https://en.wiktionary.org/wiki/Appendix:Romanian_alphabet

@pcrules Romanian has already been added, can you please update to the latest version and close this issue

Hi @pcrules could you confirm if you see Romanian accents in the latest version of PowerToys?

Yes yes they've been added a long time ago.
Sorry for not acting on this earlier but I had lost access to this account and only now managed to regain it

No problem, @pcrules! Thanks for getting back to us! :)


Python 3 support

It will be great add python 3 support. I think enough add 3.3+ support.

@tbicr: Working port available at https://github.com/tpievila/imposm-parser. If you find any problems, I'd appreciate any feedback.

@hukka did you take down that repo?

@danvk I'm afraid I did. I was doing some spring cleaning, and thought that nobody was really interested in it, given the lack of activity. You can still catch the changes from https://github.com/HSLdevcom/imposm-parser, though.


BUG(delete): "-DELETED" suffix is not added in deletion output

Describe the bug
When using the --delete flag to remove unused resources, and running it successfully, the output displays all the unused resources the batch prior to the deletion, instead of appending -DELETED suffix to their names upon deletion.
To Reproduce
Use --delete flag to remove resources review deletion output.
Expected behavior
The -DELETED suffix will be appended to the deleted resources' names upon deletion and be displayed in output.
Screenshots

OS version, architecture and kor version
e.g. Windows 10
Kor version: 0.5.1
Additional context
Add any other context about the problem here.

/assign
WIP in #323


How to respond to a client with 404 error?

When a client sends a message to a event name which the server doesn't listen,I want to respond to the client with a 404 error. So I wonder whether there is a event handler dealing with this situation? I've checked the source code finding it just return when the event name doesn't exist.Am I right?
`
public void onEvent(NamespaceClient client, String eventName, List args, AckRequest ackRequest) {
    EventEntry entry = eventListeners.get(eventName);
    if (entry == null) {
        return;
    }
    try {
        Queue<DataListener> listeners = entry.getListeners();
        for (DataListener dataListener : listeners) {
            Object data = getEventData(args, dataListener);
            dataListener.onData(client, data, ackRequest);
        }
    } catch (Exception e) {
        exceptionListener.onEventException(e, args, client);
        if (ackMode == AckMode.AUTO_SUCCESS_ONLY) {
            return;
        }
    }
    sendAck(ackRequest);

}`

Yes you're.


Push current registry to dev namespace

The new registry API and front end need to be pushed to the dev namespace in order to test the application. This is also the only way we can test the nats pub-sub ervice and make sure that we are able to provision OC projects through the API.
Dod:

[x] Registry API is pushed to dev namcespace

Done with the help of @w8896699 and @IanKWatts , registry API is available here: https://registry-new-api-platform-registry-dev.apps.silver.devops.gov.bc.ca/graphql