22     -1     -1                                                            -1   8.25      1                               [NASDAQOM]
23     -1     -1                                                            -1   8.97      1                               [NASDAQOM]
24     -1     -1                                                            -1   9.30      1                               [NASDAQOM]
25     -1     -1                                                            -1  10.00      3                               [NASDAQOM]
26     -1     -1                                                            -1  10.49      1                               [NASDAQOM]
2024-06-25 13:14:16.436 | INFO     | icli.lang:run:1015 - SPY :: 18 of 20 :: SPY   241220C00600000 Grouped by Price :: Row count: 28
2024-06-25 13:14:16.439 | FRAME    | icli.lang:run:1015 -
     Bids                                                                        Asks
    price   size                                                   marketMaker  price   size                              marketMaker
0    4.45  1,071  [BATS, CBOE, CBOE2, EDGX, EMERALD, ISE, MEMX, NASDAQOM, PSE]   4.51    867  [BATS, CBOE2, EMERALD, ISE, MEMX, MIAX]
1    4.44    407                       [AMEX, MIAX, NASDAQBX, NASDAQOM, PEARL]   4.52    564       [CBOE, EDGX, NASDAQBX, PEARL, PSE]
2    4.43     64                                                        [PHLX]   4.53    246                   [AMEX, NASDAQOM, PHLX]
3    4.27     10                                                         [ISE]   4.70     99                                    [PSE]
4    4.24     99                                                         [PSE]   4.72     78                                   [AMEX]
5    4.21    227                                                   [AMEX, ISE]   4.74    148                                    [ISE]
6    3.98      1                                                         [PSE]   5.02  1,366                         [AMEX, ISE, PSE]
7    3.91    423                                                         [ISE]   5.90      1                                    [PSE]
8    3.90    471                                                         [PSE]   6.33      1                                    [PSE]
9    3.89    471                                                        [AMEX]   6.34     11                                   [AMEX]
10   3.29      1                                                    [NASDAQOM]   6.48      1                                   [AMEX]
11   2.94      2                                               [NASDAQOM, PSE]   6.62     11                                    [ISE]
12   2.91      1                                                    [NASDAQOM]   6.66      1                               [NASDAQOM]
13   2.58     11                                                        [AMEX]   6.69      1                               [NASDAQOM]
14   2.46      1                                                        [AMEX]   6.72     10                                    [ISE]
15   2.28      1                                                    [NASDAQOM]   6.73      1                               [NASDAQOM]
16   2.27     10                                                         [ISE]   6.77     10                               [NASDAQOM]
17   2.26     10                                                    [NASDAQOM]   6.99      2                               [NASDAQOM]
18   2.00      1                                                    [NASDAQOM]   7.00      1                               [NASDAQOM]
19   1.99      2                                                    [NASDAQOM]   7.31      1                               [NASDAQOM]
20   1.73      1                                                    [NASDAQOM]   7.75      1                               [NASDAQOM]
21   0.01     17                                                    [NASDAQOM]   7.94      1                               [NASDAQOM]
sum    -1  3,302                                                            -1     -1  3,429                                       -1
22     -1     -1                                                            -1   8.25      1                               [NASDAQOM]
23     -1     -1                                                            -1   8.97      1                               [NASDAQOM]
24     -1     -1                                                            -1   9.30      1                               [NASDAQOM]
25     -1     -1                                                            -1  10.00      3                               [NASDAQOM]
26     -1     -1                                                            -1  10.49      1                               [NASDAQOM]
2024-06-25 13:14:17.445 | INFO     | icli.lang:run:1015 - SPY :: 19 of 20 :: SPY   241220C00600000 Grouped by Price :: Row count: 28
2024-06-25 13:14:17.448 | FRAME    | icli.lang:run:1015 -
     Bids                                                                        Asks
    price   size                                                   marketMaker  price   size                              marketMaker
0    4.45  1,071  [BATS, CBOE, CBOE2, EDGX, EMERALD, ISE, MEMX, NASDAQOM, PSE]   4.51    867  [BATS, CBOE2, EMERALD, ISE, MEMX, MIAX]
1    4.44    407                       [AMEX, MIAX, NASDAQBX, NASDAQOM, PEARL]   4.52    564       [CBOE, EDGX, NASDAQBX, PEARL, PSE]
2    4.43     64                                                        [PHLX]   4.53    246                   [AMEX, NASDAQOM, PHLX]
3    4.27     10                                                         [ISE]   4.70     99                                    [PSE]
4    4.24     99                                                         [PSE]   4.72     78                                   [AMEX]
5    4.21    227                                                   [AMEX, ISE]   4.74    148                                    [ISE]
6    3.98      1                                                         [PSE]   5.02  1,366                         [AMEX, ISE, PSE]
7    3.91    423                                                         [ISE]   5.90      1                                    [PSE]
8    3.90    471                                                         [PSE]   6.33      1                                    [PSE]
9    3.89    471                                                        [AMEX]   6.34     11                                   [AMEX]
10   3.29      1                                                    [NASDAQOM]   6.48      1                                   [AMEX]
11   2.94      2                                               [NASDAQOM, PSE]   6.62     11                                    [ISE]
12   2.91      1                                                    [NASDAQOM]   6.66      1                               [NASDAQOM]
13   2.58     11                                                        [AMEX]   6.69      1                               [NASDAQOM]
14   2.46      1                                                        [AMEX]   6.72     10                                    [ISE]
15   2.28      1                                                    [NASDAQOM]   6.73      1                               [NASDAQOM]
16   2.27     10                                                         [ISE]   6.77     10                               [NASDAQOM]
17   2.26     10                                                    [NASDAQOM]   6.99      2                               [NASDAQOM]
18   2.00      1                                                    [NASDAQOM]   7.00      1                               [NASDAQOM]
19   1.99      2                                                    [NASDAQOM]   7.31      1                               [NASDAQOM]
20   1.73      1                                                    [NASDAQOM]   7.75      1                               [NASDAQOM]
21   0.01     17                                                    [NASDAQOM]   7.94      1                               [NASDAQOM]
sum    -1  3,302                                                            -1     -1  3,429                                       -1
22     -1     -1                                                            -1   8.25      1                               [NASDAQOM]
23     -1     -1                                                            -1   8.97      1                               [NASDAQOM]
24     -1     -1                                                            -1   9.30      1                               [NASDAQOM]
25     -1     -1                                                            -1  10.00      3                               [NASDAQOM]
26     -1     -1                                                            -1  10.49      1                               [NASDAQOM]
2024-06-25 13:14:18.454 | INFO     | icli.lang:run:1015 - SPY :: 20 of 20 :: SPY   241220C00600000 Grouped by Price :: Row count: 28
2024-06-25 13:14:18.457 | FRAME    | icli.lang:run:1015 -
     Bids                                                                        Asks
    price   size                                                   marketMaker  price   size                              marketMaker
0    4.45  1,071  [BATS, CBOE, CBOE2, EDGX, EMERALD, ISE, MEMX, NASDAQOM, PSE]   4.51    867  [BATS, CBOE2, EMERALD, ISE, MEMX, MIAX]
1    4.44    407                       [AMEX, MIAX, NASDAQBX, NASDAQOM, PEARL]   4.52    564       [CBOE, EDGX, NASDAQBX, PEARL, PSE]
2    4.43     64                                                        [PHLX]   4.53    246                   [AMEX, NASDAQOM, PHLX]
3    4.27     10                                                         [ISE]   4.70     99                                    [PSE]
4    4.24     99                                                         [PSE]   4.72     78                                   [AMEX]
5    4.21    227                                                   [AMEX, ISE]   4.74    148                                    [ISE]
6    3.98      1                                                         [PSE]   5.02  1,366                         [AMEX, ISE, PSE]
7    3.91    423                                                         [ISE]   5.90      1                                    [PSE]
8    3.90    471                                                         [PSE]   6.33      1                                    [PSE]
9    3.89    471                                                        [AMEX]   6.34     11                                   [AMEX]
10   3.29      1                                                    [NASDAQOM]   6.48      1                                   [AMEX]
11   2.94      2                                               [NASDAQOM, PSE]   6.62     11                                    [ISE]
12   2.91      1                                                    [NASDAQOM]   6.66      1                               [NASDAQOM]
13   2.58     11                                                        [AMEX]   6.69      1                               [NASDAQOM]
14   2.46      1                                                        [AMEX]   6.72     10                                    [ISE]
15   2.28      1                                                    [NASDAQOM]   6.73      1                               [NASDAQOM]
16   2.27     10                                                         [ISE]   6.77     10                               [NASDAQOM]
17   2.26     10                                                    [NASDAQOM]   6.99      2                               [NASDAQOM]
18   2.00      1                                                    [NASDAQOM]   7.00      1                               [NASDAQOM]
19   1.99      2                                                    [NASDAQOM]   7.31      1                               [NASDAQOM]
20   1.73      1                                                    [NASDAQOM]   7.75      1                               [NASDAQOM]
21   0.01     17                                                    [NASDAQOM]   7.94      1                               [NASDAQOM]
sum    -1  3,302                                                            -1     -1  3,429                                       -1
22     -1     -1                                                            -1   8.25      1                               [NASDAQOM]
23     -1     -1                                                            -1   8.97      1                               [NASDAQOM]
24     -1     -1                                                            -1   9.30      1                               [NASDAQOM]
25     -1     -1                                                            -1  10.00      3                               [NASDAQOM]
26     -1     -1                                                            -1  10.49      1                               [NASDAQOM]
2024-06-25 13:14:18.457 | INFO     | icli.cli:dorepl:3299 - [depth] Duration: 19.6659

BTC.USD (updated the debug formatting a little)
live> depth :7 20
2024-06-25 13:19:07.745 | WARNING  | icli.lang:run:906 - [BTC.USD] Depth not populated. Failing warm-up check 1.
2024-06-25 13:19:07.898 | WARNING  | icli.lang:run:906 - [BTC.USD] Depth not populated. Failing warm-up check 2.
2024-06-25 13:19:08.011 | ERROR    | eventkit.event:emit:205 - API Error [orderId 28119] [code 2152]: Exchanges - Depth: PAXOS;  for Crypto(conId=479624278, symbol='BTC', exchange='PAXOS', currency='USD', localSymbol='BTC.USD', tradingClass='BTC')
OPERATION 0 at position 0 for price 61951.75 at qty 0.53501026
OPERATION 0 at position 1 for price 61948.25 at qty 0.01278939
OPERATION 0 at position 2 for price 61945.5 at qty 0.045
OPERATION 0 at position 3 for price 61945.0 at qty 0.8
OPERATION 0 at position 4 for price 61943.0 at qty 0.08071928
OPERATION 0 at position 5 for price 61939.25 at qty 0.045
OPERATION 0 at position 6 for price 61933.0 at qty 0.045
OPERATION 0 at position 7 for price 61926.0 at qty 0.0563
OPERATION 0 at position 8 for price 61925.75 at qty 0.045
OPERATION 0 at position 9 for price 61921.75 at qty 0.07534474
OPERATION 0 at position 0 for price 61952.0 at qty 0.06932784
OPERATION 0 at position 1 for price 61952.5 at qty 0.18570699
OPERATION 0 at position 2 for price 61961.0 at qty 0.045
OPERATION 0 at position 3 for price 61965.25 at qty 0.08386592
OPERATION 0 at position 4 for price 61967.25 at qty 0.36775176
OPERATION 0 at position 5 for price 61973.5 at qty 0.045
OPERATION 0 at position 6 for price 61976.25 at qty 0.0563
OPERATION 0 at position 7 for price 61976.5 at qty 3.403e-05
OPERATION 0 at position 8 for price 61982.75 at qty 0.04503257
OPERATION 0 at position 9 for price 61986.5 at qty 5.313e-05
OPERATION 0 at position 10 for price 62015.0 at qty 0.176
2024-06-25 13:19:08.053 | INFO     | icli.lang:run:1015 - BTC :: 1 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:08.057 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,951.75  0.53501026     [PAXOS]  61,952.00  0.06932784     [PAXOS]
1    61,948.25  0.01278939     [PAXOS]  61,952.50  0.18570699     [PAXOS]
2    61,945.50       0.045     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.00         0.8     [PAXOS]  61,965.25  0.08386592     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.25  0.36775176     [PAXOS]
5    61,939.25       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
6    61,933.00       0.045     [PAXOS]  61,976.25      0.0563     [PAXOS]
7    61,926.00      0.0563     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,925.75       0.045     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,921.75  0.07534474     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  1.74016367          -1         -1  1.07407224          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 7 for price 61925.75 at qty 0.045
OPERATION 1 at position 8 for price 61921.75 at qty 0.07534474
OPERATION 1 at position 9 for price 61919.5 at qty 0.045
OPERATION 1 at position 4 for price 61967.0 at qty 0.0563
OPERATION 1 at position 5 for price 61967.25 at qty 0.36775176
OPERATION 1 at position 6 for price 61973.5 at qty 0.045
2024-06-25 13:19:09.066 | INFO     | icli.lang:run:1015 - BTC :: 2 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:09.069 | FRAME    | icli.lang:run:1015 -
          Bids                                       Asks
         price                size marketMaker      price        size marketMaker
0    61,951.75          0.53501026     [PAXOS]  61,952.00  0.06932784     [PAXOS]
1    61,948.25          0.01278939     [PAXOS]  61,952.50  0.18570699     [PAXOS]
2    61,945.50               0.045     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.00                 0.8     [PAXOS]  61,965.25  0.08386592     [PAXOS]
4    61,943.00          0.08071928     [PAXOS]  61,967.00      0.0563     [PAXOS]
5    61,939.25               0.045     [PAXOS]  61,967.25  0.36775176     [PAXOS]
6    61,933.00               0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
7    61,925.75               0.045     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,921.75          0.07534474     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,919.50               0.045     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  1.7288636700000002          -1         -1  1.07407224          -1
10          -1                  -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 5 for price 61933.0 at qty 0.045
OPERATION 1 at position 6 for price 61925.75 at qty 0.045
OPERATION 1 at position 7 for price 61921.75 at qty 0.07534474
OPERATION 1 at position 8 for price 61919.5 at qty 0.045
OPERATION 1 at position 9 for price 61914.75 at qty 0.0563
2024-06-25 13:19:10.078 | INFO     | icli.lang:run:1015 - BTC :: 3 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:10.080 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,951.75  0.53501026     [PAXOS]  61,952.00  0.06932784     [PAXOS]
1    61,948.25  0.01278939     [PAXOS]  61,952.50  0.18570699     [PAXOS]
2    61,945.50       0.045     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.00         0.8     [PAXOS]  61,965.25  0.08386592     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.00      0.0563     [PAXOS]
5    61,933.00       0.045     [PAXOS]  61,967.25  0.36775176     [PAXOS]
6    61,925.75       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
7    61,921.75  0.07534474     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,919.50       0.045     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,914.75      0.0563     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  1.74016367          -1         -1  1.07407224          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 1 for price 61951.0 at qty 0.8
OPERATION 1 at position 2 for price 61948.25 at qty 0.01278939
OPERATION 1 at position 3 for price 61945.5 at qty 0.045
OPERATION 1 at position 4 for price 61945.0 at qty 0.8
OPERATION 1 at position 5 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 6 for price 61933.0 at qty 0.045
OPERATION 1 at position 7 for price 61925.75 at qty 0.045
OPERATION 1 at position 8 for price 61921.75 at qty 0.07534474
OPERATION 1 at position 9 for price 61919.5 at qty 0.045
OPERATION 1 at position 0 for price 61952.0 at qty 0.06852884
2024-06-25 13:19:11.085 | INFO     | icli.lang:run:1015 - BTC :: 4 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:11.087 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,951.75  0.53501026     [PAXOS]  61,952.00  0.06852884     [PAXOS]
1    61,951.00         0.8     [PAXOS]  61,952.50  0.18570699     [PAXOS]
2    61,948.25  0.01278939     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25  0.08386592     [PAXOS]
4    61,945.00         0.8     [PAXOS]  61,967.00      0.0563     [PAXOS]
5    61,943.00  0.08071928     [PAXOS]  61,967.25  0.36775176     [PAXOS]
6    61,933.00       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,921.75  0.07534474     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  2.48386367          -1         -1  1.07327324          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
2024-06-25 13:19:12.093 | INFO     | icli.lang:run:1015 - BTC :: 5 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:12.097 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,951.75  0.53501026     [PAXOS]  61,952.00  0.06852884     [PAXOS]
1    61,951.00         0.8     [PAXOS]  61,952.50  0.18570699     [PAXOS]
2    61,948.25  0.01278939     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25  0.08386592     [PAXOS]
4    61,945.00         0.8     [PAXOS]  61,967.00      0.0563     [PAXOS]
5    61,943.00  0.08071928     [PAXOS]  61,967.25  0.36775176     [PAXOS]
6    61,933.00       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,921.75  0.07534474     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  2.48386367          -1         -1  1.07327324          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61951.75 at qty 0.53500952
OPERATION 1 at position 0 for price 61952.0 at qty 0.06693083
2024-06-25 13:19:13.102 | INFO     | icli.lang:run:1015 - BTC :: 6 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:13.104 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price                size marketMaker
0    61,951.75  0.53500952     [PAXOS]  61,952.00          0.06693083     [PAXOS]
1    61,951.00         0.8     [PAXOS]  61,952.50          0.18570699     [PAXOS]
2    61,948.25  0.01278939     [PAXOS]  61,961.00               0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25          0.08386592     [PAXOS]
4    61,945.00         0.8     [PAXOS]  61,967.00              0.0563     [PAXOS]
5    61,943.00  0.08071928     [PAXOS]  61,967.25          0.36775176     [PAXOS]
6    61,933.00       0.045     [PAXOS]  61,973.50               0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,976.50           3.403e-05     [PAXOS]
8    61,921.75  0.07534474     [PAXOS]  61,982.75          0.04503257     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,986.50           5.313e-05     [PAXOS]
sum         -1  2.48386293          -1         -1  1.0716752299999999          -1
10          -1          -1          -1  62,015.00               0.176     [PAXOS]
OPERATION 1 at position 0 for price 61951.75 at qty 0.5349223
OPERATION 1 at position 1 for price 61951.5 at qty 8.722e-05
OPERATION 1 at position 4 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 5 for price 61933.0 at qty 0.045
OPERATION 1 at position 6 for price 61925.75 at qty 0.045
OPERATION 1 at position 7 for price 61921.75 at qty 0.07534474
OPERATION 1 at position 8 for price 61919.5 at qty 0.045
OPERATION 1 at position 9 for price 61914.75 at qty 0.0563
OPERATION 1 at position 1 for price 61951.0 at qty 8.722e-05
OPERATION 1 at position 5 for price 61925.75 at qty 0.045
OPERATION 1 at position 6 for price 61921.75 at qty 0.07534474
OPERATION 1 at position 7 for price 61919.5 at qty 0.045
OPERATION 1 at position 8 for price 61914.75 at qty 0.0563
OPERATION 1 at position 9 for price 61914.5 at qty 0.32302487
2024-06-25 13:19:14.109 | INFO     | icli.lang:run:1015 - BTC :: 7 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:14.112 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price                size marketMaker
0    61,951.75   0.5349223     [PAXOS]  61,952.00          0.06693083     [PAXOS]
1    61,951.00   8.722e-05     [PAXOS]  61,952.50          0.18570699     [PAXOS]
2    61,948.25  0.01278939     [PAXOS]  61,961.00               0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25          0.08386592     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.00              0.0563     [PAXOS]
5    61,925.75       0.045     [PAXOS]  61,967.25          0.36775176     [PAXOS]
6    61,921.75  0.07534474     [PAXOS]  61,973.50               0.045     [PAXOS]
7    61,919.50       0.045     [PAXOS]  61,976.50           3.403e-05     [PAXOS]
8    61,914.75      0.0563     [PAXOS]  61,982.75          0.04503257     [PAXOS]
9    61,914.50  0.32302487     [PAXOS]  61,986.50           5.313e-05     [PAXOS]
sum         -1   1.2181878          -1         -1  1.0716752299999999          -1
10          -1          -1          -1  62,015.00               0.176     [PAXOS]
2024-06-25 13:19:15.118 | INFO     | icli.lang:run:1015 - BTC :: 8 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:15.120 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price                size marketMaker
0    61,951.75   0.5349223     [PAXOS]  61,952.00          0.06693083     [PAXOS]
1    61,951.00   8.722e-05     [PAXOS]  61,952.50          0.18570699     [PAXOS]
2    61,948.25  0.01278939     [PAXOS]  61,961.00               0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25          0.08386592     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.00              0.0563     [PAXOS]
5    61,925.75       0.045     [PAXOS]  61,967.25          0.36775176     [PAXOS]
6    61,921.75  0.07534474     [PAXOS]  61,973.50               0.045     [PAXOS]
7    61,919.50       0.045     [PAXOS]  61,976.50           3.403e-05     [PAXOS]
8    61,914.75      0.0563     [PAXOS]  61,982.75          0.04503257     [PAXOS]
9    61,914.50  0.32302487     [PAXOS]  61,986.50           5.313e-05     [PAXOS]
sum         -1   1.2181878          -1         -1  1.0716752299999999          -1
10          -1          -1          -1  62,015.00               0.176     [PAXOS]
OPERATION 1 at position 0 for price 61951.75 at qty 0.46110365
OPERATION 1 at position 1 for price 61950.5 at qty 8.722e-05
OPERATION 1 at position 0 for price 61952.0 at qty 0.12690178
OPERATION 1 at position 1 for price 61952.5 at qty 0.12570699
2024-06-25 13:19:16.126 | INFO     | icli.lang:run:1015 - BTC :: 9 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:16.128 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,951.75  0.46110365     [PAXOS]  61,952.00  0.12690178     [PAXOS]
1    61,950.50   8.722e-05     [PAXOS]  61,952.50  0.12570699     [PAXOS]
2    61,948.25  0.01278939     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25  0.08386592     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.00      0.0563     [PAXOS]
5    61,925.75       0.045     [PAXOS]  61,967.25  0.36775176     [PAXOS]
6    61,921.75  0.07534474     [PAXOS]  61,973.50       0.045     [PAXOS]
7    61,919.50       0.045     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,914.75      0.0563     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,914.50  0.32302487     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  1.14436915          -1         -1  1.07164618          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61951.75 at qty 0.46118626
OPERATION 1 at position 1 for price 61949.75 at qty 8.722e-05
OPERATION 1 at position 5 for price 61941.75 at qty 0.00010327
OPERATION 1 at position 6 for price 61925.75 at qty 0.045
OPERATION 1 at position 7 for price 61921.75 at qty 0.07534474
OPERATION 1 at position 8 for price 61919.5 at qty 0.045
OPERATION 1 at position 9 for price 61914.75 at qty 0.0563
OPERATION 1 at position 0 for price 61952.0 at qty 0.12695196
2024-06-25 13:19:17.133 | INFO     | icli.lang:run:1015 - BTC :: 10 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:17.135 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,951.75  0.46118626     [PAXOS]  61,952.00  0.12695196     [PAXOS]
1    61,949.75   8.722e-05     [PAXOS]  61,952.50  0.12570699     [PAXOS]
2    61,948.25  0.01278939     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25  0.08386592     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.00      0.0563     [PAXOS]
5    61,941.75  0.00010327     [PAXOS]  61,967.25  0.36775176     [PAXOS]
6    61,925.75       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
7    61,921.75  0.07534474     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,919.50       0.045     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,914.75      0.0563     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  0.82153016          -1         -1  1.07169636          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61952.0 at qty 0.12693744
2024-06-25 13:19:18.141 | INFO     | icli.lang:run:1015 - BTC :: 11 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:18.142 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price                size marketMaker
0    61,951.75  0.46118626     [PAXOS]  61,952.00          0.12693744     [PAXOS]
1    61,949.75   8.722e-05     [PAXOS]  61,952.50          0.12570699     [PAXOS]
2    61,948.25  0.01278939     [PAXOS]  61,961.00               0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25          0.08386592     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.00              0.0563     [PAXOS]
5    61,941.75  0.00010327     [PAXOS]  61,967.25          0.36775176     [PAXOS]
6    61,925.75       0.045     [PAXOS]  61,973.50               0.045     [PAXOS]
7    61,921.75  0.07534474     [PAXOS]  61,976.50           3.403e-05     [PAXOS]
8    61,919.50       0.045     [PAXOS]  61,982.75          0.04503257     [PAXOS]
9    61,914.75      0.0563     [PAXOS]  61,986.50           5.313e-05     [PAXOS]
sum         -1  0.82153016          -1         -1  1.0716818399999999          -1
10          -1          -1          -1  62,015.00               0.176     [PAXOS]
OPERATION 1 at position 1 for price 61950.25 at qty 8.722e-05
OPERATION 1 at position 2 for price 61948.25 at qty 0.01381584
OPERATION 1 at position 6 for price 61939.25 at qty 0.045
OPERATION 1 at position 7 for price 61925.75 at qty 0.045
OPERATION 1 at position 8 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 9 for price 61919.5 at qty 0.045
OPERATION 1 at position 0 for price 61952.0 at qty 0.12854509
OPERATION 1 at position 3 for price 61965.25 at qty 0.07823235
2024-06-25 13:19:19.148 | INFO     | icli.lang:run:1015 - BTC :: 12 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:19.150 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,951.75  0.46118626     [PAXOS]  61,952.00  0.12854509     [PAXOS]
1    61,950.25   8.722e-05     [PAXOS]  61,952.50  0.12570699     [PAXOS]
2    61,948.25  0.01381584     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25  0.07823235     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.00      0.0563     [PAXOS]
5    61,941.75  0.00010327     [PAXOS]  61,967.25  0.36775176     [PAXOS]
6    61,939.25       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,921.75  0.07454748     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  0.81045935          -1         -1  1.06765592          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
2024-06-25 13:19:20.156 | INFO     | icli.lang:run:1015 - BTC :: 13 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:20.158 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,951.75  0.46118626     [PAXOS]  61,952.00  0.12854509     [PAXOS]
1    61,950.25   8.722e-05     [PAXOS]  61,952.50  0.12570699     [PAXOS]
2    61,948.25  0.01381584     [PAXOS]  61,961.00       0.045     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,965.25  0.07823235     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,967.00      0.0563     [PAXOS]
5    61,941.75  0.00010327     [PAXOS]  61,967.25  0.36775176     [PAXOS]
6    61,939.25       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
8    61,921.75  0.07454748     [PAXOS]  61,982.75  0.04503257     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,986.50   5.313e-05     [PAXOS]
sum         -1  0.81045935          -1         -1  1.06765592          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61965.25 at qty 0.01603512
OPERATION 1 at position 1 for price 61967.0 at qty 0.0563
OPERATION 1 at position 2 for price 61967.25 at qty 0.36775176
OPERATION 1 at position 3 for price 61973.5 at qty 0.045
OPERATION 1 at position 4 for price 61976.5 at qty 3.403e-05
OPERATION 1 at position 5 for price 61982.75 at qty 0.04503257
OPERATION 1 at position 6 for price 61986.5 at qty 5.313e-05
OPERATION 1 at position 7 for price 61989.0 at qty 0.045
OPERATION 1 at position 8 for price 61990.0 at qty 0.32230134
OPERATION 1 at position 9 for price 61995.25 at qty 0.045
OPERATION 1 at position 0 for price 61951.75 at qty 0.06118626
OPERATION 1 at position 0 for price 61952.5 at qty 0.06
OPERATION 1 at position 1 for price 61965.25 at qty 0.01603512
OPERATION 1 at position 2 for price 61967.0 at qty 0.0563
OPERATION 1 at position 3 for price 61967.25 at qty 0.045
OPERATION 1 at position 4 for price 61973.5 at qty 0.045
OPERATION 1 at position 5 for price 61976.5 at qty 3.403e-05
OPERATION 1 at position 6 for price 61982.75 at qty 0.04503257
OPERATION 1 at position 7 for price 61986.5 at qty 5.313e-05
OPERATION 1 at position 8 for price 61989.0 at qty 0.045
OPERATION 1 at position 9 for price 61990.0 at qty 0.32230134
OPERATION 1 at position 0 for price 61952.0 at qty 0.06
OPERATION 1 at position 1 for price 61951.75 at qty 0.06118626
OPERATION 1 at position 2 for price 61950.25 at qty 8.722e-05
OPERATION 1 at position 3 for price 61948.25 at qty 0.01381584
OPERATION 1 at position 4 for price 61945.5 at qty 0.045
OPERATION 1 at position 5 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 6 for price 61941.75 at qty 0.00010327
OPERATION 1 at position 7 for price 61939.25 at qty 0.045
OPERATION 1 at position 8 for price 61925.75 at qty 0.045
OPERATION 1 at position 9 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 0 for price 61952.0 at qty 0.46
OPERATION 1 at position 0 for price 61952.25 at qty 0.015
OPERATION 1 at position 1 for price 61952.5 at qty 0.06
OPERATION 1 at position 2 for price 61965.25 at qty 0.01603512
OPERATION 1 at position 3 for price 61967.0 at qty 0.0563
OPERATION 1 at position 4 for price 61967.25 at qty 0.045
OPERATION 1 at position 5 for price 61973.5 at qty 0.045
OPERATION 1 at position 6 for price 61976.5 at qty 3.403e-05
OPERATION 1 at position 7 for price 61982.75 at qty 0.04503257
OPERATION 1 at position 8 for price 61986.5 at qty 5.313e-05
OPERATION 1 at position 9 for price 61989.0 at qty 0.045
OPERATION 1 at position 0 for price 61952.0 at qty 0.06008722
OPERATION 1 at position 1 for price 61951.75 at qty 0.04508261
OPERATION 1 at position 2 for price 61948.25 at qty 0.01381584
OPERATION 1 at position 3 for price 61945.5 at qty 0.045
OPERATION 1 at position 4 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 5 for price 61941.75 at qty 0.00010327
OPERATION 1 at position 6 for price 61939.25 at qty 0.045
OPERATION 1 at position 7 for price 61925.75 at qty 0.045
OPERATION 1 at position 8 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 9 for price 61919.5 at qty 0.045
OPERATION 1 at position 0 for price 61952.5 at qty 0.06
OPERATION 1 at position 1 for price 61955.5 at qty 0.01401701
OPERATION 1 at position 2 for price 61962.25 at qty 0.045
OPERATION 1 at position 3 for price 61965.25 at qty 0.07603512
OPERATION 1 at position 4 for price 61967.0 at qty 0.0563
OPERATION 1 at position 5 for price 61967.25 at qty 0.045
OPERATION 1 at position 6 for price 61973.5 at qty 0.045
OPERATION 1 at position 7 for price 61976.5 at qty 3.403e-05
OPERATION 1 at position 8 for price 61982.75 at qty 0.04503257
OPERATION 1 at position 9 for price 61986.5 at qty 5.313e-05
OPERATION 1 at position 0 for price 61952.25 at qty 0.06
OPERATION 1 at position 1 for price 61952.0 at qty 0.06008722
OPERATION 1 at position 2 for price 61951.75 at qty 0.04508261
OPERATION 1 at position 3 for price 61948.25 at qty 0.01381584
OPERATION 1 at position 4 for price 61945.5 at qty 0.045
OPERATION 1 at position 5 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 6 for price 61941.75 at qty 0.00010327
OPERATION 1 at position 7 for price 61939.25 at qty 0.045
OPERATION 1 at position 8 for price 61925.75 at qty 0.045
OPERATION 1 at position 9 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 4 for price 61967.0 at qty 0.1163
OPERATION 1 at position 0 for price 61952.0 at qty 0.06008722
OPERATION 1 at position 1 for price 61951.75 at qty 0.04508261
OPERATION 1 at position 2 for price 61948.25 at qty 0.01381584
OPERATION 1 at position 3 for price 61945.5 at qty 0.045
OPERATION 1 at position 4 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 5 for price 61941.75 at qty 0.00010327
OPERATION 1 at position 6 for price 61939.25 at qty 0.045
OPERATION 1 at position 7 for price 61925.75 at qty 0.045
OPERATION 1 at position 8 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 9 for price 61919.5 at qty 0.045
OPERATION 1 at position 4 for price 61967.0 at qty 0.0563
OPERATION 1 at position 0 for price 61952.25 at qty 0.06
OPERATION 1 at position 1 for price 61952.0 at qty 0.10508722
OPERATION 1 at position 2 for price 61951.75 at qty 0.04508261
OPERATION 1 at position 3 for price 61948.25 at qty 0.01381584
OPERATION 1 at position 4 for price 61945.5 at qty 0.045
OPERATION 1 at position 5 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 6 for price 61941.75 at qty 0.00010327
OPERATION 1 at position 7 for price 61939.25 at qty 0.045
OPERATION 1 at position 8 for price 61925.75 at qty 0.045
OPERATION 1 at position 9 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 0 for price 61955.5 at qty 0.01401701
OPERATION 1 at position 1 for price 61958.5 at qty 0.045
OPERATION 1 at position 0 for price 61952.0 at qty 0.04508722
OPERATION 1 at position 1 for price 61951.75 at qty 0.04508261
OPERATION 1 at position 2 for price 61948.25 at qty 0.01381584
OPERATION 1 at position 3 for price 61945.5 at qty 0.045
OPERATION 1 at position 4 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 5 for price 61941.75 at qty 0.00010327
OPERATION 1 at position 6 for price 61939.25 at qty 0.045
OPERATION 1 at position 7 for price 61925.75 at qty 0.045
OPERATION 1 at position 8 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 9 for price 61919.5 at qty 0.045
OPERATION 1 at position 0 for price 61952.5 at qty 0.045
OPERATION 1 at position 1 for price 61955.5 at qty 0.01401701
OPERATION 1 at position 2 for price 61958.5 at qty 0.045
OPERATION 1 at position 3 for price 61962.25 at qty 0.045
OPERATION 1 at position 4 for price 61965.25 at qty 0.01603512
OPERATION 1 at position 5 for price 61967.0 at qty 0.0563
OPERATION 1 at position 6 for price 61967.25 at qty 0.045
OPERATION 1 at position 7 for price 61973.5 at qty 0.045
OPERATION 1 at position 8 for price 61976.5 at qty 3.403e-05
OPERATION 1 at position 9 for price 61982.75 at qty 0.04503257
OPERATION 1 at position 0 for price 61952.0 at qty 0.44508722
OPERATION 1 at position 0 for price 61952.25 at qty 0.045
OPERATION 1 at position 1 for price 61952.5 at qty 0.08070699
OPERATION 1 at position 2 for price 61955.5 at qty 0.01401701
OPERATION 1 at position 3 for price 61958.5 at qty 0.045
2024-06-25 13:19:21.162 | INFO     | icli.lang:run:1015 - BTC :: 14 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:21.164 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price                size marketMaker
0    61,952.00  0.44508722     [PAXOS]  61,952.25               0.045     [PAXOS]
1    61,951.75  0.04508261     [PAXOS]  61,952.50          0.08070699     [PAXOS]
2    61,948.25  0.01381584     [PAXOS]  61,955.50          0.01401701     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,958.50               0.045     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,965.25          0.01603512     [PAXOS]
5    61,941.75  0.00010327     [PAXOS]  61,967.00              0.0563     [PAXOS]
6    61,939.25       0.045     [PAXOS]  61,967.25               0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,973.50               0.045     [PAXOS]
8    61,921.75  0.07454748     [PAXOS]  61,976.50           3.403e-05     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,982.75          0.04503257     [PAXOS]
sum         -1   0.8393557          -1         -1  0.5681257200000001          -1
10          -1          -1          -1  62,015.00               0.176     [PAXOS]
OPERATION 1 at position 0 for price 61952.0 at qty 0.50508722
OPERATION 1 at position 0 for price 61952.25 at qty 0.08520599
OPERATION 1 at position 1 for price 61952.5 at qty 0.14070699
OPERATION 1 at position 4 for price 61963.0 at qty 0.32277359
OPERATION 1 at position 5 for price 61965.25 at qty 0.01603512
OPERATION 1 at position 6 for price 61967.0 at qty 0.0563
OPERATION 1 at position 7 for price 61967.25 at qty 0.045
OPERATION 1 at position 8 for price 61973.5 at qty 0.045
OPERATION 1 at position 9 for price 61976.5 at qty 3.403e-05
2024-06-25 13:19:22.170 | INFO     | icli.lang:run:1015 - BTC :: 15 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:22.172 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,952.00  0.50508722     [PAXOS]  61,952.25  0.08520599     [PAXOS]
1    61,951.75  0.04508261     [PAXOS]  61,952.50  0.14070699     [PAXOS]
2    61,948.25  0.01381584     [PAXOS]  61,955.50  0.01401701     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,958.50       0.045     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,963.00  0.32277359     [PAXOS]
5    61,941.75  0.00010327     [PAXOS]  61,965.25  0.01603512     [PAXOS]
6    61,939.25       0.045     [PAXOS]  61,967.00      0.0563     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,967.25       0.045     [PAXOS]
8    61,921.75  0.07454748     [PAXOS]  61,973.50       0.045     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
sum         -1   0.8993557          -1         -1  0.94607273          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61952.0 at qty 0.505
OPERATION 1 at position 1 for price 61951.75 at qty 0.04516983
OPERATION 1 at position 6 for price 61925.75 at qty 0.045
OPERATION 1 at position 7 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 8 for price 61919.5 at qty 0.045
OPERATION 1 at position 9 for price 61914.75 at qty 0.0563
OPERATION 1 at position 5 for price 61964.75 at qty 0.045
OPERATION 1 at position 6 for price 61965.25 at qty 0.01603512
OPERATION 1 at position 7 for price 61967.0 at qty 0.0563
2024-06-25 13:19:23.177 | INFO     | icli.lang:run:1015 - BTC :: 16 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:23.179 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,952.00       0.505     [PAXOS]  61,952.25  0.08520599     [PAXOS]
1    61,951.75  0.04516983     [PAXOS]  61,952.50  0.14070699     [PAXOS]
2    61,948.25  0.01381584     [PAXOS]  61,955.50  0.01401701     [PAXOS]
3    61,945.50       0.045     [PAXOS]  61,958.50       0.045     [PAXOS]
4    61,943.00  0.08071928     [PAXOS]  61,963.00  0.32277359     [PAXOS]
5    61,941.75  0.00010327     [PAXOS]  61,964.75       0.045     [PAXOS]
6    61,925.75       0.045     [PAXOS]  61,965.25  0.01603512     [PAXOS]
7    61,921.75  0.07454748     [PAXOS]  61,967.00      0.0563     [PAXOS]
8    61,919.50       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
9    61,914.75      0.0563     [PAXOS]  61,976.50   3.403e-05     [PAXOS]
sum         -1   0.9106557          -1         -1  0.94607273          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61952.0 at qty 0.50491109
OPERATION 1 at position 0 for price 61952.25 at qty 0.08488639
OPERATION 1 at position 3 for price 61958.25 at qty 0.11585819
OPERATION 1 at position 4 for price 61958.5 at qty 0.045
OPERATION 1 at position 5 for price 61963.0 at qty 0.32277359
OPERATION 1 at position 6 for price 61964.75 at qty 0.045
OPERATION 1 at position 7 for price 61965.25 at qty 0.01603512
OPERATION 1 at position 8 for price 61967.0 at qty 0.0563
OPERATION 1 at position 9 for price 61973.5 at qty 0.045
OPERATION 1 at position 1 for price 61951.75 at qty 0.04508261
OPERATION 1 at position 2 for price 61949.75 at qty 8.722e-05
OPERATION 1 at position 3 for price 61948.25 at qty 0.01381584
OPERATION 1 at position 4 for price 61945.5 at qty 0.045
OPERATION 1 at position 5 for price 61943.0 at qty 0.08071928
OPERATION 1 at position 6 for price 61941.75 at qty 0.00010327
OPERATION 1 at position 7 for price 61925.75 at qty 0.045
OPERATION 1 at position 8 for price 61921.75 at qty 0.07454748
OPERATION 1 at position 9 for price 61919.5 at qty 0.045
2024-06-25 13:19:24.184 | INFO     | icli.lang:run:1015 - BTC :: 17 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:24.187 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,952.00  0.50491109     [PAXOS]  61,952.25  0.08488639     [PAXOS]
1    61,951.75  0.04508261     [PAXOS]  61,952.50  0.14070699     [PAXOS]
2    61,949.75   8.722e-05     [PAXOS]  61,955.50  0.01401701     [PAXOS]
3    61,948.25  0.01381584     [PAXOS]  61,958.25  0.11585819     [PAXOS]
4    61,945.50       0.045     [PAXOS]  61,958.50       0.045     [PAXOS]
5    61,943.00  0.08071928     [PAXOS]  61,963.00  0.32277359     [PAXOS]
6    61,941.75  0.00010327     [PAXOS]  61,964.75       0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,965.25  0.01603512     [PAXOS]
8    61,921.75  0.07454748     [PAXOS]  61,967.00      0.0563     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
sum         -1  0.85426679          -1         -1  1.06157729          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61952.0 at qty 0.50489482
2024-06-25 13:19:25.193 | INFO     | icli.lang:run:1015 - BTC :: 18 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:25.195 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,952.00  0.50489482     [PAXOS]  61,952.25  0.08488639     [PAXOS]
1    61,951.75  0.04508261     [PAXOS]  61,952.50  0.14070699     [PAXOS]
2    61,949.75   8.722e-05     [PAXOS]  61,955.50  0.01401701     [PAXOS]
3    61,948.25  0.01381584     [PAXOS]  61,958.25  0.11585819     [PAXOS]
4    61,945.50       0.045     [PAXOS]  61,958.50       0.045     [PAXOS]
5    61,943.00  0.08071928     [PAXOS]  61,963.00  0.32277359     [PAXOS]
6    61,941.75  0.00010327     [PAXOS]  61,964.75       0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,965.25  0.01603512     [PAXOS]
8    61,921.75  0.07454748     [PAXOS]  61,967.00      0.0563     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
sum         -1  0.85425052          -1         -1  1.06157729          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61952.0 at qty 0.54989482
OPERATION 1 at position 2 for price 61950.75 at qty 8.722e-05
2024-06-25 13:19:26.200 | INFO     | icli.lang:run:1015 - BTC :: 19 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:26.202 | FRAME    | icli.lang:run:1015 -
          Bids                               Asks
         price        size marketMaker      price        size marketMaker
0    61,952.00  0.54989482     [PAXOS]  61,952.25  0.08488639     [PAXOS]
1    61,951.75  0.04508261     [PAXOS]  61,952.50  0.14070699     [PAXOS]
2    61,950.75   8.722e-05     [PAXOS]  61,955.50  0.01401701     [PAXOS]
3    61,948.25  0.01381584     [PAXOS]  61,958.25  0.11585819     [PAXOS]
4    61,945.50       0.045     [PAXOS]  61,958.50       0.045     [PAXOS]
5    61,943.00  0.08071928     [PAXOS]  61,963.00  0.32277359     [PAXOS]
6    61,941.75  0.00010327     [PAXOS]  61,964.75       0.045     [PAXOS]
7    61,925.75       0.045     [PAXOS]  61,965.25  0.01603512     [PAXOS]
8    61,921.75  0.07454748     [PAXOS]  61,967.00      0.0563     [PAXOS]
9    61,919.50       0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
sum         -1  0.89925052          -1         -1  1.06157729          -1
10          -1          -1          -1  62,015.00       0.176     [PAXOS]
OPERATION 1 at position 0 for price 61952.0 at qty 0.54970958
OPERATION 1 at position 2 for price 61949.5 at qty 8.722e-05
OPERATION 1 at position 4 for price 61946.75 at qty 0.08071438
OPERATION 1 at position 5 for price 61945.5 at qty 0.045
2024-06-25 13:19:27.207 | INFO     | icli.lang:run:1015 - BTC :: 20 of 20 :: BTC.USD Grouped by Price :: Row count: 12
2024-06-25 13:19:27.209 | FRAME    | icli.lang:run:1015 -
          Bids                                       Asks
         price                size marketMaker      price        size marketMaker
0    61,952.00          0.54970958     [PAXOS]  61,952.25  0.08488639     [PAXOS]
1    61,951.75          0.04508261     [PAXOS]  61,952.50  0.14070699     [PAXOS]
2    61,949.50           8.722e-05     [PAXOS]  61,955.50  0.01401701     [PAXOS]
3    61,948.25          0.01381584     [PAXOS]  61,958.25  0.11585819     [PAXOS]
4    61,946.75          0.08071438     [PAXOS]  61,958.50       0.045     [PAXOS]
5    61,945.50               0.045     [PAXOS]  61,963.00  0.32277359     [PAXOS]
6    61,941.75          0.00010327     [PAXOS]  61,964.75       0.045     [PAXOS]
7    61,925.75               0.045     [PAXOS]  61,965.25  0.01603512     [PAXOS]
8    61,921.75          0.07454748     [PAXOS]  61,967.00      0.0563     [PAXOS]
9    61,919.50               0.045     [PAXOS]  61,973.50       0.045     [PAXOS]
sum         -1  0.8990603800000001          -1         -1  1.06157729          -1
10          -1                  -1          -1  62,015.00       0.176     [PAXOS]
2024-06-25 13:19:27.209 | INFO     | icli.cli:dorepl:3299 - [depth] Duration: 19.4653

actually, we may not even need a proper "sorted dict" anyway.
The IBKR API is always sending "insert" operations in order (0, 1, 2, 3, 4, ....) before any update operations, so a regular dict should be fine too.
The original errors appear to be around shutdown or reset operations where we stop the depth request, clear the depth lists, but then still receive depth updates which crashes the handler because we already deleted all the positions.
The code has two places where it deletes the depth data: when a request starts (to remove any old data), and also when a request ends (to remove any old data). It is a bit redundant two delete it twice, but with at least using a regular dict, we can still accept updates to the deleted data and it'll just write data in the background we ignore.
(technically I guess we could add another flag for "is depth request active" and only update the fields if our current ticker agrees it has a depth request open and we haven't deleted the data; may add that as just a temporary debug check to verify if we are getting updates after we cancel the request. sadly many of these cases can only really be tested during market hours.)

Good information, it would have helped if you added the side to the debug prints. But it does seem like IB first populates the book using inserts and then updates the elements.
There are two ways how IB can add (or remove) an order to the book once it has been initialized with inserts:

Update the order at the correct index based on price, then update all indices after that one
Insert at an index and delete at the end

It seems IB is using only the method 1. I'm surprised they did it like this is as it's inefficient to update the whole book when orders are mostly removed from the top of the book. In theory we should get delete operations in case of less traded stocks, when there are less entries in the book than the client requested. In this case when an order is removed, IB must call delete for one of the entries.
ps. I really appreciate the effort you are putting to this!

I think just implementing the flag should fix this issue (for now).

Thank you! I appreciate the effort you put into this. Even the commit message is top notch. This library is in good hands. I can help in future (if I can find the time).


Fix Logic.Implicit.on haddock format

Hey team- just noticed a missing @ in the haddock string for Logic.Implicit.on, leading to some wonky formatting in the online docs.

Thanks, Will!


Run ANALYZE post COPY and ALTER statements

Since we are copying the data onto a fresh new table,
that looks (structurally) like the original table, its
better to run ANALYZE so planners are up to date.
We do it once after swap, just as good measure, also in case
the duration to replay change is long (true, when working with large
tables and copying a table can take hours, while changes are being accumulated
in the audit table)
cc @jfrost
https://github.com/shayonj/pg-online-schema-change/pull/6#issuecomment-1025198001

We could assume that autovacuum will run if the changes from replay pass the thresholds and the ANALYZE before the replay/swap gets us where we need to be from the initial data load.

yeah thats true, we are also disabling vacuum intentionally to not interfere with the process here. Will restore as part of drop/cleanup, so the second analyze is just good measure I suppose.


Add MPU initiate/complete and putPart for AWS

Adds implementation of MPU basics to AWS backend

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13357 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13495 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13636 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13644 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13658 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13663 for CI status.

@ironman-machine do it

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13666 for CI status.

@ironman-machine

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13670 for CI status.

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13671 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13672 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13698 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13703 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13707 for CI status.

@ironman-machine
SCALITY_INTEGRATION_BRANCH=ft/excludeRubyAwsTests

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"DEFAULT_BRANCH": "master", "SCALITY_INTEGRATION_BRANCH": "ft/excludeRubyAwsTests", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU", "REPO_NAME": "S3"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13718 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13728 for CI status.

@ironman-machine go

Hello @dora-korpar
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "DEFAULT_BRANCH": "master", "SCALITY_S3_BRANCH": "ft/S3C-334-awsBackendMPU"}
Please follow http://ci.ironmann.io/gh/scality/Integration/13745 for CI status.


Create personal details page

Page where users will add their personal and contact details

@Joseaie added an alternative page but can't do the actual lookup for this version

@Joseaie added an alternative page but can't do the actual lookup for this version

You can add the alternative as a separate PR, even if it doesn't actually function?

It's already been pushed to this branch

Ah, I see... you could place this commit (git cherry-pick) on a new branch, revert it from this branch and make a separate PR? Or if that's too much, could you add some screenshots of that too, so we can see it please?

There's less boxes. If I can figure it out then I'll add to it. Thanks


Error when editing code

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/edit
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
I tried to edit my code and now keep running into this error:
"C:\Users\bridg\MyApp\MyApp.csproj(1,1): error MSB4025: The project file could not be loaded. Data at the root level is invalid. Line 1, position 1.
The build failed. Fix the build errors and run again."
Up until this point it had been running fine. Before this, it gave me an error because it expected my code to be found under "MyApp.csporj" so I changed the file name to that, yet it still says Program in the file directory.

The error suggests the project file is corrupted. Please try again starting from https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/install and follow the steps and this should work.


The asset file name is not the same in vite3 and vite4 when use preserveModules: true

Describe the bug
I am using library mode with preserveModules: true.
And I‘d like to change the output folder of asset files, so I rewrite the assetFileNames function.
For example:
assetFileNames: ({ name }) => {
  console.log("==assetFileName==", name);
  return "[name].[ext]";
}

I can't get the full path of asset file with vite4.
Reproduction
https://github.com/kuoruan/vite3-vite4-diff
Steps to reproduce
cd vite3
pnpm install
pnpm run build

cd vite4
pnpm install
pnpm run build

System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
    CPU: (6) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 2.54 GB / 5.79 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v16.19.0/bin/npm
  npmPackages:
    vite: ^3.2.5 => 3.2.5

Used Package Manager
pnpm
Logs
With vite3
==assetFileName== /home/liao/Projects/Github/vite-bug/vite3/src/javascript.svg
==assetFileName== src/style.css
==assetFileName== src/style.css

With vite4
==assetFileName== javascript.svg
==assetFileName== src/style.css
==assetFileName== style.css

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

same as #11424

Closing this, tracking #11424


autoIncrement doesn't work with BIGINT Unsigned on MySQL 8

GORM Playground Link
https://github.com/go-gorm/playground/pull/207
Description
uint64 primaryKey (BIGINT UNSIGNED) doesn't create AUTO_INCREMENT on MySQL 8.0 despite autoIncrement annotation (doesn't work with "auto_increment" key either).
The only way to make it AutoMigrate with AUTO_INCREMENT is to add this annotation :
ID uint64 gorm:"primaryKey;autoIncrement;column:id;type:bigint unsigned AUTO_INCREMENT;" json:"id"
But then, if any Association, it will fail with this error:
"error": "Error occurred when migrating Profile:Error 1075: Incorrect table definition; there can be only one auto column and it must be defined as a key"

https://gorm.io/docs/models.html#Fields-Tags


RestClient::Exceptions::OpenTimeout caught by rescue RestClient::ExceptionWithResponse

This may be intended behavior, but it feels strange. If I am rescuing RestClient::ExceptionWithResponse, I would except that e.response not be nil.
I have logic in various places where our API is calling other services like this
def some_method
  response = RestClient.post('some_url', 'some_payload', 'some_headers')
  do_stuff(response)
rescue RestClient::ExceptionWithResponse => e
  error_message = JSON.parse(e.response.body)
  return_error_to_client
end

If those services return valid error messages, we need to pass them back on to the client that initiated our request. It feels weird that RestClient::Exceptions::OpenTimeout gets caught in this same block, and then has no response. I want to handle that scenario separately, but I can't because all my current rescue blocks will catch that exception.
Maybe this is just semantics, but an Exception "WithResponse" should have a response.

Duplicate of https://github.com/rest-client/rest-client/issues/286
This crazy design is for backwards compatibility. The timeout exceptions inherit from RestClient::RequestTimeout, which inherits from ExceptionWithResponse because RequestTimeout is also used for HTTP 408 responses.
Even the name ExceptionWithResponse is deprecated and would be removed if we ever get a chance to refactor the exception tree.
We would need a major version increment to rework the exception hierarchy, so this would have to wait for 3.0.


partitions in V4?

I'd like to port some existing code from v3 to v4, and hitting a bump. Layouts seem to be gone completely. Is the plan to release these in the future as modules? Is there a timeline for that? (I want to use layout.partition.) I am itching to start using V4 on a current project because of the new Cubehelix space (awesome, BTW).
Thanks in advance for any help.

Start here: https://github.com/d3/d3/blob/master/CHANGES.md#hierarchies-d3-hierarchy

Thanks. Got it.


[PAIShare] Disable and remove Upload from Marketplace in PAIshare v0.0.1

Coverage increased (+2.2%) to 63.523% when pulling c1e189eaf26159ff17b5207bfb7ff8bb14ee549c on yanli2017:paishare into 456df6f41770859126bacc180889134c25d4d29b on Microsoft:paishare.


Composite builds: internal instantiation cosmetics

Cosmetics:

direct instantiation of Java collections without Guava
lambdas
diamond operator

@rieske the public interface IncludedBuild used in the settings is also implemented by DefaultIncludedBuild.
All DSL types should be instantiated by the instantiator for Groovy DSL conveniences we do by instrumenting the class.
At the moment it has no practical advantage, because the interface does not have any Action/Closure taking method or properties method. But if it would have e.g.:
gradle.includedBuild('some-build').task('someTask') {
     taskDetails = 'abc' //this does not exist TaskReference today, but imagine it would
}

Then this would stop working for example and you would have to do:
gradle.includedBuild('some-build').task('someTask') {
     it.taskDetails = 'abc'
}

Another example that would stop working I think tis the prop = 'value' shortcut for prop.set('value') (if that interface would use properties).
I think we should still keep using the instantiator here.

Thanks! I'll revert the commit with instantiator then.

What's the rationale for direct instantiation of Java collections without Guava? Should we apply it everywhere?

What's the rationale for direct instantiation of Java collections without Guava? Should we apply it everywhere?

Those Guava helpers were mostly for Java 6 and became obsolete with Java 7 and later. The javadoc for those factory methods says:

Note for Java 7 and later: this method is now unnecessary and should be treated as deprecated. Instead, use the ArrayList constructor directly, taking advantage of the new "diamond" syntax.

As for whether to apply it everywhere - I think nah, unless it is new code. That's mostly my OCD while I'm blocked waiting for test results.

I see. Thanks, @rieske.


/load is sent as a message to auto_terminal when used.

/load should not be sent as a message to the bot

resolved


Bulk Update: Replace Type Accelerators with Fully Qualified Type Names

Pull Request (PR) description
Replaces Type Accelerators with Fully Qualified Type Names
This Pull Request (PR) fixes the following issues
None
Task list

[x] Added an entry under the Unreleased section of the change log in
CHANGELOG.md. Entry should say what was changed, and how that affects
users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as
appropriate.
[x] Examples appropriately added/updated.
[x] Unit tests added/updated. See
DSC Resource Testing Guidelines.
[x] Integration tests added/updated (where possible). See
DSC Resource Testing Guidelines.
[ ] New/changed code adheres to
DSC Resource Style Guidelines and Best Practices

This change is

Codecov Report

Merging #556 into dev will not change coverage.
The diff coverage is 82%.

@@         Coverage Diff         @@
##            dev   #556   +/-   ##
===================================
  Coverage    74%    74%
===================================
  Files        27     27
  Lines      4029   4029
  Branches      4      4
===================================
  Hits       3009   3009
  Misses     1016   1016
  Partials      4      4

@PlagueHO , I think this one is ready for review. Careful what you wish for :)
@tmeckel , this one is probably going to be fun to rebase with your DSCWebService changes. If you feel you're close to finishing, we can delay checking in this PR until yours has been checked in, and then I'll do the rebase on this one. Just let me know.

Also, @PlagueHO , I left out a bunch of the 'System.Management.Automation' based type accelerators that are also attributes (like CmdletBinding, Parameter, ValidateNotNullOrEmpty, etc). I wasn't sure if we were going that far or not. Let me know what you think we should do.
 I'll have to do some troubleshooting on this later this weekend.

No worries - maybe leave [ref] as is (although using [ref] is usually an indicator of design issues).

@mhendric I just rebased my PR #507 to the latest dev commits with no issues (conflicts). So I guess the changes here haven't been merged into the dev branch. Right? In the meanwhile I saw that you created 34 (!) comments on my PR. I've to see if I can go through all of them over the weekend. Seems not likely though. So before my PR gets a blocker for merging those changes in this PR, go and merge them. I'll cope with the potential conflicts then :-D
oh, by the way: why are those changes are required? I know there're issues with those aliases, like with creating an new PSObject from a hashtable via [pscustomobject]which doesn't work with [psobject], but are there any other reasons why this PR exists?

@PlagueHO , I think this one is ready for a code review again. Thanks.
@tmeckel , this PR is mostly designed to standardize type declarations throughout the module, help prevent conflicting type accelerators, and fix wrong case of letters in types. That being said, if we don't make an actual policy that type accelerators aren't allowed, this module is probably going to eventually drift back into an inconsistent state. Perhaps we should agree on a standard first and get it documented. Or alternately agree that maybe this isn't worth the effort. What do you guys think?

Oh okay now I understand the motivation about this PR. Thanks for the clarifacation @mhendric . I do agree that there might be subtle differences between how the aliases work and therefore it could be useful to remove them from the existing code. But as you said there must be some comments on this in the contribute.md stating that aliases are not allowed inside this module. The probable issue I see might be the fact that people abandon their PR after review or never submit a PR when there are too many rules to follow, because this might let the project look like it's ruled by pedantic people LOL Don't get me wrong I'm the last that don't understand the importance of coding rules but I learned over the last decades that when you overdo it, it won't help anyone.

Oh one more thing @mhendric  ... in the current style guidelines https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md you'll find examples using [string] instead of [System.String] all over the place. So this has to be changed when this PR is merged I guess.

Yeah maybe this one is going too far. Although I do like the idea of at least requiring consistent casing (i.e. [String] vs. [string]). But maybe we should bring these ideas as a discussion over to the DSC Style Guidelines first and get community consensus.

I totally agree with the casing and as I said there are some pitfalls using alias (accelerator), so we should definitly have a broaded discussion about how and if they shoould be used. Not only in this particular module but throughout all DSC modules. I would like to hear @johlju opinion on this for example.
Oh and I "fixed" 25 of your reviews on my PR #507 :-D only 9 to go ... but those relate to the Unit Tests. Important I know but harder to cope with as with those style guides things.

Oh and about adhering to the coding and style guides: will it be feasible to have a VSCode "addin" or somthing that will help people to "correctly contribute".

That would be awesome to have a VSCode plugin that automatically detected and fixed style violations. It would also be cool if we had some custom script analyzer rules for violations. That would at least allow us to have the issues flagged during testing, and take the onus off the reviewers for hunting down style violations.

We already have VSCode detecting some of the style violations and have issues open to add more. You should already be getting underlining for some of custom style rules in VSCode (eg param formats).

@PlagueHO yes I realized this already because as @mhendric and me were talking, I saw that VSCode informed my about some of the style violations that @mhendric commented in his review. So in the end we must enhance .\DSCResource.Tests\DscResource.AnalyzerRules to include all important recommendations from the DSC style guide. However the PSAnalyzer rules in DSCResource.Tests\DscResource.AnalyzerRules are not a submodule currently, but they should be though, so that every DSC module can use them.

We should probably have this discussion over at DSCResources. I'd prefer not using type accelerators, but as you all rightly point out: enforcing this suddenly accumulates a lot of tech debt across all repos. But also, if we don't enforce it with PSSA rules etc then these repos will just drift back.
But I still think it would be worthwhile completing making this repo consistent.
My main goal is to get consistency within a repo - but it was pretty mixed within this one.
@tmeckel - All DSC modules can use the custom rules. I use them in all the ones I maintain. Pretty sure @johlju does too. Every module uses DSCResource.Tests I think.

@plagueho the advantage if having the custom rules in a separate GIT module would be the fact that every DSC module would benefit from improvements and addons to it without having to manually import them into each module and as we're talking about drift... A submodule would guarantee that every DSC module is using the same rules. And on top the module could be overseen by a maintainer.

Oh, right - thought you meant PS Module rather than Git Submodule.
The problem with using Git Submodules though is that they don't point to head - they point to a specific commit. This means every maintainer would have to continuously update the .GitSubmodule file every time the rules update - which really is not likely to happen in many cases (I know I'd forget - just another thing for me to do across the 10+ modules I maintain). And many of the other modules haven't yet managed to meet HQRM standards, so getting them to adopt these rules should maybe start with getting them to HQRM - then it becomes much easier to tweak rules and so on.
I think empowering maintainers is great, but as many repos and maintainers are struggling under the load already, if we add a requirement to continuously update the external style rule modules within their own repos then it'll just not happen. I for one really don't want to add this to any of the modules I maintain.
But I'm not sure it is even necessary because maintainers can opt-in and out of specific PSSA rules by controlling the ScriptAnalyzer.psd1 file in their own repos. We also have the .MetaTestOptIn file to enable maintainers to opt  in to some of more powerful rules when they choose to.
I might of course misunderstand the problem that needs to be solved here :grin: So, I apologize if that is the case :grin:

@tmeckel - one thing I should add: We definitely don't want everyone adding DSCResource.Tests into their module repos directly - this was never the intent - and hopefully no one is doing this :grin:. It is currently Git Cloned when tests are run and updated every time the tests are run (which is why we're quite keen to ensure it is always updated on each users machine in every repo).

 That explains why VSCode started to show issues with the code AFTER I run tge Unit tests tge first time...  Bwahahahahahahaaaa 😂

@tmeckel - you wouldn't be the first to do this - I do this regularly myself :cry:. Ideally we'd have a way to sort this when the module is cloned/updated - as you suggested, Submodules would be a good solution, but because it is pinned to a commit it would rarely be kept-up-to-date. But we couldn't come up with a good solution yet.

@PlagueHO I think the discussion I've started is a good example of not interfering in things that much more intelligent people than oneself have thought about. And TBH I wasn't aware of the fact that the DSCResource.Tests is pull every time the tests got run because I normally run my tests on a VM and not on the computer where I've installed my VSCode, except yesterday because I was in a small hurry to get some of the review stuff fixed from @mhendric. That resulted in the fact that VSCode "suddenly" showed "problems" in my code that relate to the DSC best practices.
After you mentioned the somewhat annoying issues with Git submodules (Subversions externals are so much better :-D) I thought about if subtrees could be a solutions. But they're not stored as metadata to the repo so every developer must add the subtree every time again when the repo got pulled the first time. Impractical and error prone! Than I remembered that Git as of 1.8.2 is able to track branches in submodules so the update to a new (head) version of a submodule is easy but again as you said the update must be manually done. Again error prone!
But how about using the post-merge hook in Git which runs after each pull? Like so
PS> echo "git submodule update --init --recursive" >> .git/hooks/post-merge

This will update all submodules to the latest version automatically every time a pull is done. When we combine this with the ability of a submodule to track branches this could be a way to replace the current implementation of pulling the DSCResource.Tests only when tests run. Or, if we don't wanna go that far, we might separate the VSCode (PSScriptAnalyzer) stuff to a separate repo which is then included as submodule that is always present when the parent repo is pulled.

@PlagueHO sorry pestering you :-D but I made a proposal to use GIT hooks for managing submodules. Whats's your opinion about this?
https://github.com/PowerShell/xPSDesiredStateConfiguration/pull/556#issuecomment-464454524


No prompt for the individual games.

It would be really nice to have a prompt between each game the script successfully identifies that requires a Y/N input if the save transfer should happen for that specific game.
People probably download this for one game, and not for a lot of them at the same time.

Misclicked the comment. Just wanted to add that some games might end up with rather big zip-files of the saves, like my starfield was 500 mb and took quite some time for the script to extract. An option to skip would save some frustration to some one some time.

Good idea, I'll implement this soon.


Opening Device manager in Desktop settings, opens mouse configuration instead

Testing UNSTABLE OS git revision 2a2a3070d, I noticed that clicking on Device manager icon in Desktop settings, opens mouse configuration instead.

just checked my UNSTABLE laptop.
Mine opens device manage as expected.
had you adjusted the cursor before hand?

Nop, nothing changed and I did clean install from USB image.

I have two separate systems, both clean install and they both act same way.

I can confirm this bug.

This was actually a bug in sysadm-ui-qt, but it's been fixed.
https://github.com/trueos/sysadm-ui-qt/commit/21d4a97bbc14ba6901913776d4e4b189ac9f2763


MDL works by accident

MDL allocation, as well as any kernel function call with more than 4 args will work based on pure luck.
Explanation:
x64 calling convention will try to pass any parameters after the 4th via stack, which cannot be possible since the syscall will switch the stack pointer, and the function will use as arguments whatever is on the stack at that point in time.
Possible fix:
add dynamic assembly generation for stack allocation of arguments and use call/ret instead of jump to be able to restore stack state before returning like this

This could also explain the random BSODs some people experience when using MDL allocations since those require functions with more than 4 args.

This is true and will be glad to accept your pull request if you fix it, mdl was done by another contributor and I didn't see that little mistake on that time

This is true and will be glad to accept your pull request if you fix it, mdl was done by another contributor and I didn't see that little mistake on that time

I would suggest opening a branch for the eventual MDL development, or at the very least implement a small stub like the one showed, to set the first 2-3 stack params to 0, which could help make MDL allocations more deterministic while still being broken for any future development involving functions with lots of arguments. If opening a branch doesn't seem like a good idea at the very least a warning should be printed when a KernelCall is being made with any more than 4 params to warn. If branching is possible disable MDL allocations from master and keep it in the second branch. If for any reason I will ever need to implement this correctly I will submit a push request, until then I'll use the same "patch" I showed in the issue since it's enough for me.

auto new_cookie = 0x2B992DDFA232 ^ GetCurrentProcessId() ^ GetCurrentThreadId();   22h2 我该如何修复

Following your suggestion, I have moved mdl allocation to a new branch and added static assert to master


enhancement: Detailed status of the modes.

Current ui

When chill mode is on, it says chill:

When work mode is on, it says work:

Enchancement
While in chill mode, the status text shall say chilling... and on hovering over that it should say work or maybe switch to work  clicking upon which shall switch to work mode and status text should say working... vice versa.
Check the clip below.
https://user-images.githubusercontent.com/58453023/149613234-b5617bdc-d222-41a0-9ca7-0766a68a5ae8.mp4

That's a very good suggestion, @varunmamtora06 .
Infact, it's not even enhancement, it's necessary. But yeah, I do have some UI/UX plans for addressing this. Shall update here later.
Thank you for raising this issue!

Completely revamped the UI for the popup.

Feel like it significantly improves the UX.
Thank you for raising this issue 😄


Default Title Sort option not setting for full library

Steps to reproduce

Select Title
select sort
sort by chapter number
select 3 little dots
select set as default
select check box for "Also apply to all entries in my library"
select OK

Expected behavior
should set default sort style for ALL titles in library
Actual behavior
Set for most but a few sporadically here and there did not change to the default
Crash logs
No response
Mihon version
Stable 0.16.1
Android version
Android 14
Device
Samsung Galaxy S23 Ultra
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.16.1.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Did you try to restart the app after applying that setting and checking again? Maybe it glitched out a bit

OOF didn't even think of that, just spent the time and went through each
title and set it as default and moved on
On Wed, Jan 17, 2024 at 5:57 PM MajorTanya @.***> wrote:

Did you try to restart the app after applying that setting and checking
again? Maybe it glitched out a bit
—
Reply to this email directly, view it on GitHub
https://github.com/mihonapp/mihon/issues/106#issuecomment-1897294449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6PP4PZMAWYBQ4Z4OHDGNWTYPBJNFAVCNFSM6AAAAABB7JSBR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJXGI4TINBUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Remove Zany80 from the list

I've abandoned Zany80, probably indefinitely; it's served its purpose as what was honestly more a research project than a console others could use.

Thanks.

@farvardin it has been abandoned.
From the creator:

I've abandoned Zany80, probably indefinitely; it's served its purpose as what was honestly more a research project than a console others could use.

Ok. But it's a pity to remove it from the list, it might be taken over by someone else, it's open source

I have actually started working on it a bit lately, but it's not currently usable. @farvardin If I get it back to the point of usability, I'll open a PR to readd it to the list; for now, there's no reason for it to be mentioned.


Add model doc strings to the api view so they're available through the web interface

I was wanting to document the meaning of the fields somewhere, I thought having it within the data registry might mean it would be kept up-to-date and easily findable. Not sure if there's a nicer way to do this, so consider this a POC that is potentially mergable.

Is the doc attribute displayed automatically by the Django REST framework?

Is the __doc__ attribute displayed automatically by the Django REST framework?
yes - https://www.django-rest-framework.org/topics/documenting-your-api/#self-describing-apis

yes - https://www.django-rest-framework.org/topics/documenting-your-api/#self-describing-apis

Good to know. This is my first time using the REST framework so i'm sure there's plenty I could be doing better. I'm happy to merge this change.

yes - https://www.django-rest-framework.org/topics/documenting-your-api/#self-describing-apis

Good to know. This is my first time using the REST framework so i'm sure there's plenty I could be doing better. I'm happy to merge this change.

I came across it through some fortuitous googling - I wanted to document the fields somewhere, and it seemed like having it closely tied with the database and registry would be the best location for it


Cannot download when the system language is zh-CN

Describe the bug
I have specified ja-JP to download but the local language will still be downloaded ，Then the above problem occurs.
To Reproduce
$ crunchy archive -l ja-JP https://www.crunchyroll.com/series/G9VHN91ZP/legend-of-mana--the-teardrop-crystal-[S1E1] -debug
➞ Failed to parse url 1
➞ An error occurred: failed to get episodes: error for endpoint https://beta-api.crunchyroll.com/cms/v2/FR/M3/crunchyroll/movies?movie_listing_id=G9VHN91ZP&locale=zh-CN&Signature=G9Z~3eRxH..... (400): Unsupported locale zh-CN

Expected behavior
I hope it can be downloaded in the specified language.
Client (please complete the following information):

OS: Debian 11
Version v2.3.5

On Windows :
crunchy-v2.3.5_windows.exe archive -l ja-JP https://www.crunchyroll.com/series/G9VHN91ZP/legend-of-mana--the-teardrop-crystal-[S1E1] -debug
=> Parsed url 1
=> Legend of Mana -The Teardrop Crystal- Season 1
=>      1. Lapis-lazuli (première partie) » 1920x1080px, 23.97 FPS (S01E01)

=> Downloading episode `Lapis-lazuli (première partie)` to `Lapis-lazuli (première partie).mkv` (merging audio for additional formats)
=>      Episode: S01E01
=>      Audio: ja-JP
=>      Subtitle:
=>      Resolution: 1920x1080px
=>      FPS: 23.97

=> An error occurred: error while downloading: crypto/aes: invalid key size 424

Describe the bug I have specified ja-JP to download but the local language will still be downloaded ，Then the above problem occurs.
To Reproduce
$ crunchy archive -l ja-JP https://www.crunchyroll.com/series/G9VHN91ZP/legend-of-mana--the-teardrop-crystal-[S1E1] -debug
➞ Failed to parse url 1
➞ An error occurred: failed to get episodes: error for endpoint https://beta-api.crunchyroll.com/cms/v2/FR/M3/crunchyroll/movies?movie_listing_id=G9VHN91ZP&locale=zh-CN&Signature=G9Z~3eRxH..... (400): Unsupported locale zh-CN

Expected behavior I hope it can be downloaded in the specified language.
Client (please complete the following information):
* OS: Debian 11

* Version v2.3.5

This error originates from Crunchyrolls poor adoption of Chinese (zh-CN). A temporary fix for this is to prefix your command with LANG=en_US. I look into it if / how I can fix it the best way.
Example with the LANG=en_US prefix:
$ LANG=en_US crunchy archive -l ja-JP https://www.crunchyroll.com/series/G9VHN91ZP/legend-of-mana--the-teardrop-crystal-[S1E1]

On Windows :
crunchy-v2.3.5_windows.exe archive -l ja-JP https://www.crunchyroll.com/series/G9VHN91ZP/legend-of-mana--the-teardrop-crystal-[S1E1] -debug
=> Parsed url 1
=> Legend of Mana -The Teardrop Crystal- Season 1
=>      1. Lapis-lazuli (première partie) » 1920x1080px, 23.97 FPS (S01E01)

=> Downloading episode `Lapis-lazuli (première partie)` to `Lapis-lazuli (première partie).mkv` (merging audio for additional formats)
=>      Episode: S01E01
=>      Audio: ja-JP
=>      Subtitle:
=>      Resolution: 1920x1080px
=>      FPS: 23.97

=> An error occurred: error while downloading: crypto/aes: invalid key size 424

This is, once again, an error on the Crunchyroll servers. Video streams are encrypted with a key which differs for every episode and Crunchyroll fails to deliver the decryption key for the episode you want to download. Waiting is the only option here, and hoping that this issue is fixed soon.
Crunchyroll provides two ways how videos can be streamed / downloaded, HLS and DASH. While crunchyroll.com uses DASH and it works flawless with this episode, crunchy-cli uses HLS (which caused this issue). The decision to use HLS for crunchy-cli was made because it is widely used and the protocol is way cleaner than DASH. Just in case you were wondering why it's working on the website but not here.
As far as I can see this error only occurs on this one episode, so I don't see an urgent need to change how to receive video stream. But I might add a fallback to DASH if HLS does not work in the future.

Locale used can be manipulated with the --lang flag beginning with release v2.3.6.


Usage with gtest/gmock not working as expected

I am trying to use the library with google test/google mock. It seems gtest is not able to print the json value out with its universal printer.
Example that fails:
#include <gtest/gtest.h>
#include <nlohmann/json.hpp>

using json = nlohmann::json;
using namespace testing;

TEST(EnsureJsonComparesCorrectly)
{
   auto test1 = R"BLA(
{
    "event" : "test",
    "description" : "Test description"
}
)BLA"_json;

   auto test2 = R"BLA(
{
    "description" : "Test description",
    "event" : "test"
}
)BLA"_json;
    EXPECT_THAT(test1, Eq(test2));
}

I am using 3.1.2 of nlohmann and 1.8.0 of google test/mock. I am compiling and running on macOS.
I also tried to use it with gmock, but it also fails. The myCall function is defined as:
void myCall(std::string url, nlohmann::json message);

So this is in gmock:
MOCK_METHOD2(myCall, void(std::string url, nlohmann::json message));

And then in the test I set an expectation, like this:
 EXPECT_CALL(*myMock, myCall(_, test1));

but every time gtest tries to print, in this case the "test1" object, then it crashes.
So what could causing this? Gtest is normally able to use a custom PrintTo function but I could not get that to work. Any pointers on how to solve it?
I have a "workaround" but it goes against the "json as first-class citizen" philosophy :)
Workaround for EXPECT_THAT:
EXPECT_THAT(test1.dump(), Eq(test2.dump()));

That is more or less acceptable, but not really.
And then for gmock it is really too much :) see:
json tmp;
json test;
EXPECT_CALL(*myMock, myCall(_, _)).WillOnce(SaveArg<1>(&tmp));
EXPECT_THAT(tmp.dump(), Eq(test.dump()));

But of course it should be as easy as:
EXPECT_CALL(*myMock, myCall(_, test));

I am not using Google Mock myself, so I have no idea what to do here.

It seems I am hitting this situation: #709
And the solution is in googletest itself, however they still need to do a release of their current master as 1.8.1 which I hope is very soon.
The workaround suggested in #709 is not working for me unfortunately.

Initially the workaround in #709 only worked for me, but some time later it seemed to stop working. I wasn't able to find out why but I suspect it was related to the problem discussed in google/googletest#1149
Eventually I fixed it by adding overloads for my other types that are based off nlohmann::basic_json<>, e.g.
namespace nlohmann
{
  void PrintTo(const json& j, std::ostream* os)
  {
    *os << j.dump();
  }

  void PrintTo(const ordered_json& j, std::ostream* os)
  {
    *os << j.dump();
  }
}

where ordered_json is
using ordered_json = nlohmann::basic_json<ifo_map>;


Add giscus custom theme

Feature Description

There was no option for setting giscus theme. So I added a feature to be able to set giscus theme by hugo.yaml file for customization.
Problem/Solution

Problem:
Just toggled light or dark. These options originally using for Hextra light/dark theme.
Solution:
giscus has pair of themes. (e.g. noborder_light, noborder_dark)

Finding out current theme of Hextra, and then replacing light to dark in the string could be the solution.
Also, I add an option to hugo.yaml file so that users could custom giscus theme easily.
params:
  comments:
    giscus:
      theme: noborder_light

completed in #522


Remove omitempty for fields that need be encoded

if feel the omitempty confuse the app logic, why not remove all field?


Quick device menu

Hi @tananaev
I have started working on the device quick menu PR. Please review the initial draft.
Can you please tell me how to pass the event(which we pass to onMarkerClick function), on clicking the list item to show the quick menu?

Also don't forget to rebase. You have a merge conflict.

Overall looks good, I think. Can you please also attach a screenshot.

Can you please tell me how to pass the event(which we pass to onMarkerClick function), on clicking the list item to show the quick menu?

Maybe through props? Why do you need to pass the event?

To show the StatusView on clicking device in the list.

To show the StatusView on clicking device in the list.

I see what you mean. I think the best option is to tell map that a device needs to selected. Then map can get coordinates to display popup.

Hi @tananaev
Please review now.

Merged, thank you.


Return orderer error text to client

If a call from the gateway to an orderer node returns an error in the BroadcastResponse message, then it is appended to the details field of the rpc error that gets returned to the client application.  However, the Info field of that message is not getting passed on, so the client could be lacking valuable information on the underlying cause of the error.  This commit fixes that.
Signed-off-by: andrew-coleman<EMAIL_ADDRESS>

@Mergifyio backport release-2.5


geojson data?

is it possible to load and use external geojson data with this plugin?

not supported.

there is no way to use it?

no

thank you

You need to parse the geojson, then add the overlays by yourself.