Found 0 valid plots -> chia  plots check -g xxx

Testet with switch -compress 0 and without... Plots are not valid.
.\bladebit_cuda.exe -n 100 -t 24 --compress 0 -f XXX -c XXX cudaplot G:\Chia
source bladebit_cuda.exe -> https://downloads.chia.net/bladebit/
Bladebit Chia Plotter
Version      : 3.0.0-alpha1-dev
Git Commit   : f269db0a7ad307514e993c335897cea7ebf46eda
Compiled With: msvc 19.33.31630
System:
3960x 256GB RAM 3060 12GB

chia gui sees plots? My farm sees plots and farms.
bladebit_cuda.exe -n 1 --compress 0 -f -c cudaplot H:
The -t parameter is not needed.

It is currently a known bug on Windows. It will yield bad plots. Fix is pending for next release

It is currently a known bug on Windows. It will yield bad plots. Fix is pending for next release

Thx for the information. Is there a schedule for the next onenext release

made 70tb of plots, and it turns out in vain. does not send proofs of the pool.

There's a beta/alpha keybase channel, where all the info is being shared (for those who signed up). It was shared there a while back. It would be good to keep an eye there for the latest info.
Regardless of which, it's a good idea to check all the plots until after out of beta, even if it's checking with a low -n count.

There's a beta/alpha keybase channel, where all the info is being shared (for those who signed up). It was shared there a while back. It would be good to keep an eye there for the latest info.
Regardless of which, it's a good idea to check all the plots until after out of beta, even if it's checking with a low -n count.

bladebit-cuda-v3.0.0-alpha2
who installed? fixed on the proofs?

bladebit-cuda-v3.0.0-alpha2 who installed? fixed on the proofs?

Yesterday i checkt it with two plots. Version ae066d3 and it not work on windows. Compiled at VS 2022

sad( I waited so long, but alas... I'm going to cry

ubuntu 22.04 bladebit_cuda alpha1 plots is good!
alpha2 error cuda(

Ubuntu 22.1  bladebit_cuda alpha1 OK. Plots are valid.
Ubuntu 22.1  bladebit_cuda alpha2 does not start plotting:  CUDA error: 13 (0xd ) cudaErrorInvalidSymbol : invalid device symbol
Ubuntu 22.1  bladebit_cuda alpha3 does not start plotting:  CUDA error: 13 (0xd ) cudaErrorInvalidSymbol : invalid device symbol
--.
Windows 10  bladebit_cuda alpha1 plots are invalid
Windows 10  bladebit_cuda alpha3 plots are invalid

CUDA error: 13 (0xd ) cudaErrorInvalidSymbol : invalid device symbol
Update to CUDA 12.1 to resolve this issue.

I get sad when I see that plots are not valid in Windows

Me too. But it's being worked on. I can't currently reproduce it as  they come out valid in my windows machine. Will need a bit of a deeper dive.

3.0.0-alpha3-dev on win10x64 plot not valid

To confirm: These plots were made also with **3.0.0-alpha3-dev **?

3.0.0-alpha3-dev on win10x64 plot not valid

To confirm: These plots were made also with 3.0.0-alpha3-dev?

Yes, I used https://download.chia.net/bladebit/bladebit_cuda-windows-alpha3.exe
and "chia plots check" always says is invalid

`
Bladebit Chia Plotter
Version      : 3.0.0-alpha3-dev
Git Commit   : eb6df030b555fb35addc3d6762424d52826a5d82
Compiled With: msvc 19.33.31630
[Global Plotting Config]
Will create 3 plots.
Thread count          : 48
Warm start enabled    : false
NUMA disabled         : false
CPU affinity disabled : false
Farmer public key     : XXXX
Pool contract address : XXX
Benchmark mode        : disabled
[Bladebit CUDA Plotter]
Selected cuda device 0 : NVIDIA GeForce RTX 4070 Ti
CUDA Compute Capability   : 8.9
SM count                  : 60
Max blocks per SM         : 24
Max threads per SM        : 1536
Async Engine Count        : 5
L2 cache size             : 48.00 MB
L2 persist cache max size : 36.00 MB
Stack Size                : 1.00 KB
Memory:
Total                    : 11.99 GB
Free                     : 10.79 GB
Allocating buffers (this may take a few seconds)...
Kernel RAM required       :<PHONE_NUMBER>8  bytes ( 86060.07  MiB or 84.04  GiB )
Intermediate RAM required :<PHONE_NUMBER>   bytes ( 2860.07   MiB or 2.79   GiB )
Host RAM required         :<PHONE_NUMBER>40 bytes ( 160640.00 MiB or 156.88 GiB )
Total Host RAM required   :<PHONE_NUMBER>28 bytes ( 246700.07 MiB or 240.92 GiB )
GPU RAM required          :<PHONE_NUMBER>   bytes ( 5855.79   MiB or 5.72   GiB )
Allocating buffers
Generating plot 1 / 3: c6ceae09a77fef4d570c958c7efa37edc8679eec413a1d70630fb388bdad4547
Plot temporary file: E:\ChiaBB\plot-k32-2023-03-12-15-02-c6ceae09a77fef4d570c958c7efa37edc8679eec413a1d70630fb388bdad4547.plot.tmp
Generating F1
Finished F1 in 123.57 seconds.
Table 2 completed in 169.84 seconds with<PHONE_NUMBER> entries.
Table 3 completed in 29.11 seconds with<PHONE_NUMBER> entries.
Table 4 completed in 26.20 seconds with<PHONE_NUMBER> entries.
Table 5 completed in 34.58 seconds with<PHONE_NUMBER> entries.
Table 6 completed in 21.17 seconds with<PHONE_NUMBER> entries.
Table 7 completed in 53.94 seconds with<PHONE_NUMBER> entries.
Finalizing Table 7
Finalized Table 7 in 10.09 seconds.
Completed Phase 1 in 468.69 seconds
Marked Table 6 in 9.35 seconds.
Marked Table 5 in 17.08 seconds.
Marked Table 4 in 15.95 seconds.
Marked Table 3 in 59.42 seconds.
Marked Table 2 in 19.91 seconds.
Completed Phase 2 in 121.72 seconds
Compressing Table 1 and 2...
Step 1 completed step in 112.00 seconds.
Step 2 completed step in 9.25 seconds.
Completed table 1 in 121.25 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 79.84% ).
Compressing tables 2 and 3...
Step 1 completed step in 3.81 seconds.
Step 2 completed step in 3.51 seconds.
Step 3 completed step in 8.96 seconds.
Completed table 2 in 16.28 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.09% ).
Compressing tables 3 and 4...
Step 1 completed step in 5.01 seconds.
Step 2 completed step in 3.49 seconds.
Step 3 completed step in 8.87 seconds.
Completed table 3 in 17.36 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.69% ).
Compressing tables 4 and 5...
Step 1 completed step in 44.05 seconds.
Step 2 completed step in 3.48 seconds.
Step 3 completed step in 9.17 seconds.
Completed table 4 in 56.70 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 82.25% ).
Compressing tables 5 and 6...
Step 1 completed step in 53.04 seconds.
Step 2 completed step in 3.66 seconds.
Step 3 completed step in 9.00 seconds.
Completed table 5 in 65.70 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 86.45% ).
Compressing tables 6 and 7...
Step 1 completed step in 66.53 seconds.
Step 2 completed step in 3.81 seconds.
Step 3 completed step in 17.62 seconds.
Completed table 6 in 87.96 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 100.00% ).
Serializing P7 entries
Completed serializing P7 entries in 2.23 seconds.
Completed Phase 3 in 367.49 seconds
Completed Plot 1 in 957.90 seconds ( 15.97 minutes )
E:\ChiaBB\plot-k32-2023-03-12-15-02-c6ceae09a77fef4d570c958c7efa37edc8679eec413a1d70630fb388bdad4547.plot.tmp -> E:\ChiaBB\plot-k32-2023-03-12-15-02-c6ceae09a77fef4d570c958c7efa37edc8679eec413a1d70630fb388bdad4547.plot
Completed writing plot in 14.37 seconds
Final plot table pointers:
Table 1:<PHONE_NUMBER> ( 0x000000004cd3b3ec )
Table 2:<PHONE_NUMBER>4 ( 0x00000003c1473b76 )
Table 3:<PHONE_NUMBER>9 ( 0x0000000702a12377 )
Table 4:<PHONE_NUMBER>4 ( 0x0000000a4a40f362 )
Table 5:<PHONE_NUMBER>4 ( 0x0000000da1f11616 )
Table 6:<PHONE_NUMBER>9 ( 0x00000011252921b5 )
Table 7:<PHONE_NUMBER>4 ( 0x0000001534c2d0e0 )
C 1    :             4096 ( 0x0000000000001000 )
C 2    :          1720396 ( 0x00000000001a404c )
C 3    :          1720572 ( 0x00000000001a40fc )
Final plot table sizes:
Table 1: 14151.22 MiB
Table 2: 13333.62 MiB
Table 3: 13433.99 MiB
Table 4: 13691.01 MiB
Table 5: 14387.50 MiB
Table 6: 16633.61 MiB
Table 7: 16879.36 MiB
C 1    : 1.64 MiB
C 2    : 0.00 MiB
C 3    : 1227.59 MiB
Generating plot 2 / 3: cbfed61caa519329aa8b1782924da233f2a6804308156ca07650b86510403048
....
`

@lokus77 if you could provide a full log like the one mech2you provided above, I'd appreciate it. Trying to gather all info I can on this issue.

SystemName="ADAM-PC-THREADR"
OS="Microsoft Windows 10 Pro 10.0.19045"
SystemVendor/Model="Gigabyte Technology Co., Ltd./TRX40 AORUS PRO WIFI"
CPU="AMD Ryzen Threadripper 3960X 24-Core Processor  (C:24|T:48)"
GPU="NVIDIA GeForce RTX 4070 Ti"
GPUSKU="Lovelace"
GPUArch="N/A"
DriverVersion="528.49"
PCIeLink="PCIe 4 x16"
DRAM="256GB, 8x32GB , 2666MT/s"

Hardware:
-2x Xeon 2650V4  (12c/24T)
-256Gb DDR4 2400CL17 ecc (samsung 8x32gb M386A4G40EM2-CRC  32GB 4DRx4 PC4-2400T-LD2-11  )
-Nvidia Geforce 3080Founder 10Gb Vram conected in Pcie3.0 X16 riser
-Nvme pcie 3.0 samsung 980 pro 1tb
-Huawei RH2288h V3 server (pcie3).
Soft:

Windows 10 Pro  22H2  Build 19045.2603  "Windows 10 pro for workstations"
Nvidia 528.49 drivers.

Cmd used:
bladebit_cuda-windows-alpha3.exe -v -c xxxxxxxxxxxxxx -f xxxxxxxxx -z 0 -n 1 -t 8 cudaplot g:/chia
plots in ubuntu 22.10 (kernel 5.19) Alpha1:  About 165 secs

(XFS) P1 66.83s P2 11.13s P3 87.4s  Copy time 14.92s
Plots in win10:  About 310 secs, or 355s in verbose
(NTFS) P1 192 P2 34 P3 129 Copy time 9,5s

============
=LOG verbose -v =
Bladebit Chia Plotter
Version      : 3.0.0-alpha3-dev
Git Commit   : eb6df030b555fb35addc3d6762424d52826a5d82
Compiled With: msvc 19.33.31630
[Global Plotting Config]
Will create 1 plots.
Thread count          : 8
Warm start enabled    : false
NUMA disabled         : false
CPU affinity disabled : false
Farmer public key     : 93b561exxxxxxxxxxxxxxxxxxxx
Pool contract address : xch1fxxxxxxxxxxxxxxxxxx
Benchmark mode        : disabled
[Bladebit CUDA Plotter]
Selected cuda device 0 : NVIDIA GeForce RTX 3080
CUDA Compute Capability   : 8.6
SM count                  : 68
Max blocks per SM         : 16
Max threads per SM        : 1536
Async Engine Count        : 5
L2 cache size             : 5.00 MB
L2 persist cache max size : 3.75 MB
Stack Size                : 1.00 KB
Memory:
Total                    : 10.00 GB
Free                     : 8.87 GB
Allocating buffers (this may take a few seconds)...
Kernel RAM required       :<PHONE_NUMBER>8  bytes ( 86060.07  MiB or 84.04  GiB )
Intermediate RAM required :<PHONE_NUMBER>   bytes ( 2860.07   MiB or 2.79   GiB )
Host RAM required         :<PHONE_NUMBER>40 bytes ( 160640.00 MiB or 156.88 GiB )
Total Host RAM required   :<PHONE_NUMBER>28 bytes ( 246700.07 MiB or 240.92 GiB )
GPU RAM required          :<PHONE_NUMBER>   bytes ( 5855.79   MiB or 5.72   GiB )
Allocating buffers
Generating plot 1 / 1: 3d6a764cd3ba1be7fd28215e6db12e8850b43ea92af0d836dae94771a5a25e13
Plot temporary file: g:/chia/plot-k32-2023-03-13-22-27-3d6a764cd3ba1be7fd28215e6db12e8850b43ea92af0d836dae94771a5a25e13.plot.tmp
Generating F1
Finished F1 in 2.92 seconds.
Table 2 completed in 8.44 seconds with<PHONE_NUMBER> entries.
Table 3 completed in 37.03 seconds with<PHONE_NUMBER> entries.
Table 4 completed in 35.40 seconds with<PHONE_NUMBER> entries.
Table 5 completed in 36.03 seconds with<PHONE_NUMBER> entries.
Table 6 completed in 31.72 seconds with<PHONE_NUMBER> entries.
Table 7 completed in 26.73 seconds with<PHONE_NUMBER> entries.
Finalizing Table 7
Finalized Table 7 in 13.61 seconds.
Completed Phase 1 in 192.19 seconds
Marked Table 6 in 6.93 seconds.
Marked Table 5 in 6.67 seconds.
Marked Table 4 in 6.62 seconds.
Marked Table 3 in 6.85 seconds.
Marked Table 2 in 6.95 seconds.
Completed Phase 2 in 34.03 seconds
Compressing Table 1 and 2...
Step 1 completed step in 7.81 seconds.
Step 2 completed step in 9.11 seconds.
Completed table 1 in 16.92 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 79.84% ).
Compressing tables 2 and 3...
Step 1 completed step in 6.27 seconds.
Step 2 completed step in 6.07 seconds.
Step 3 completed step in 8.98 seconds.
Completed table 2 in 21.33 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.09% ).
Compressing tables 3 and 4...
Step 1 completed step in 6.18 seconds.
Step 2 completed step in 6.10 seconds.
Step 3 completed step in 9.04 seconds.
Completed table 3 in 21.32 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.69% ).
Compressing tables 4 and 5...
Step 1 completed step in 5.95 seconds.
Step 2 completed step in 6.19 seconds.
Step 3 completed step in 9.06 seconds.
Completed table 4 in 21.21 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 82.25% ).
Compressing tables 5 and 6...
Step 1 completed step in 5.96 seconds.
Step 2 completed step in 6.42 seconds.
Step 3 completed step in 9.39 seconds.
Completed table 5 in 21.76 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 86.45% ).
Compressing tables 6 and 7...
Step 1 completed step in 6.00 seconds.
Step 2 completed step in 7.11 seconds.
Step 3 completed step in 10.42 seconds.
Completed table 6 in 23.54 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 100.00% ).
Serializing P7 entries
Completed serializing P7 entries in 3.00 seconds.
Completed Phase 3 in 129.10 seconds
Completed Plot 1 in 355.32 seconds ( 5.92 minutes )
g:/chia/plot-k32-2023-03-13-22-27-3d6a764cd3ba1be7fd28215e6db12e8850b43ea92af0d836dae94771a5a25e13.plot.tmp -> g:/chia/plot-k32-2023-03-13-22-27-3d6a764cd3ba1be7fd28215e6db12e8850b43ea92af0d836dae94771a5a25e13.plot
Completed writing plot in 9.43 seconds
Final plot table pointers:
Table 1:<PHONE_NUMBER> ( 0x000000004cd6e954 )
Table 2:<PHONE_NUMBER>6 ( 0x00000003c14df4ea )
Table 3:<PHONE_NUMBER>6 ( 0x0000000702abcd06 )
Table 4:<PHONE_NUMBER>1 ( 0x0000000a4a4fee9b )
Table 5:<PHONE_NUMBER>1 ( 0x0000000da20afdfd )
Table 6:<PHONE_NUMBER>6 ( 0x0000001125581fda )
Table 7:<PHONE_NUMBER>1 ( 0x00000015351cffa9 )
C 1    :             4096 ( 0x0000000000001000 )
C 2    :          1720676 ( 0x00000000001a4164 )
C 3    :          1720852 ( 0x00000000001a4214 )
Final plot table sizes:
Table 1: 14151.44 MiB
Table 2: 13333.87 MiB
Table 3: 13434.26 MiB
Table 4: 13691.69 MiB
Table 5: 14388.82 MiB
Table 6: 16636.30 MiB
Table 7: 16882.10 MiB
C 1    : 1.64 MiB
C 2    : 0.00 MiB
C 3    : 1227.79 MiB

Can you guys try creating a compressed level 1 -z 1 plot, please? You can then run the simulator against it or I think the validate command ought to work fine as well, as long as you don't use -u.
I am trying to determine if it's happening w/ compressed as well. Only common denominator I see so far is 256G of RAM

I am still unable to reproduce anything on my side, using the same published alpha3 executable. I used your plot id, @lokus77 and got the same output:
...
Serializing P7 entries
Completed serializing P7 entries in 2.03 seconds.
Completed Phase 3 in 86.85 seconds
Completed Plot 1 in 205.53 seconds ( 3.43 minutes )

D:/plot-k32-2023-03-13-18-40-3d6a764cd3ba1be7fd28215e6db12e8850b43ea92af0d836dae94771a5a25e13.plot.tmp -> D:/plot-k32-2023-03-13-18-40-3d6a764cd3ba1be7fd28215e6db12e8850b43ea92af0d836dae94771a5a25e13.plot
Completed writing plot in 5.74 seconds
Final plot table pointers:
 Table 1:<PHONE_NUMBER> ( 0x000000004cd6e954 )
 Table 2:<PHONE_NUMBER>6 ( 0x00000003c14df4ea )
 Table 3:<PHONE_NUMBER>6 ( 0x0000000702abcd06 )
 Table 4:<PHONE_NUMBER>1 ( 0x0000000a4a4fee9b )
 Table 5:<PHONE_NUMBER>1 ( 0x0000000da20afdfd )
 Table 6:<PHONE_NUMBER>6 ( 0x0000001125581fda )
 Table 7:<PHONE_NUMBER>1 ( 0x00000015351cffa9 )
 C 1    :             4096 ( 0x0000000000001000 )
 C 2    :          1720676 ( 0x00000000001a4164 )
 C 3    :          1720852 ( 0x00000000001a4214 )

Final plot table sizes:
 Table 1: 14151.44 MiB
 Table 2: 13333.87 MiB
 Table 3: 13434.26 MiB
 Table 4: 13691.69 MiB
 Table 5: 14388.82 MiB
 Table 6: 16636.30 MiB
 Table 7: 16882.10 MiB
 C 1    : 1.64 MiB
 C 2    : 0.00 MiB
 C 3    : 1227.79 MiB

But the validation looks good on mine:
[ 33]     228428..235347     ( 0.03% ) C3 Park Validated in 10.70 seconds | Proofs Failed: 0
[ 49]     339173..346091     ( 0.03% ) C3 Park Validated in 10.73 seconds | Proofs Failed: 0
[ 35]     242272..249191     ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[  1]       6924..13843      ( 0.03% ) C3 Park Validated in 10.73 seconds | Proofs Failed: 0
[ 31]     214584..221503     ( 0.03% ) C3 Park Validated in 10.71 seconds | Proofs Failed: 0
[ 26]     179974..186893     ( 0.03% ) C3 Park Validated in 10.71 seconds | Proofs Failed: 0
[ 30]     207662..214581     ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[ 14]      96910..103829     ( 0.03% ) C3 Park Validated in 10.71 seconds | Proofs Failed: 0
[  9]      62300..69219      ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[ 29]     200740..207659     ( 0.03% ) C3 Park Validated in 10.73 seconds | Proofs Failed: 0
[ 40]     276882..283801     ( 0.03% ) C3 Park Validated in 10.70 seconds | Proofs Failed: 0
[ 23]     159208..166127     ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[ 37]     256116..263035     ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[ 52]     359936..366854     ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[ 16]     110754..117673     ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[ 50]     346094..353012     ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[ 12]      83066..89985      ( 0.03% ) C3 Park Validated in 10.72 seconds | Proofs Failed: 0
[ 20]     138442..145361     ( 0.03% ) C3 Park Validated in 10.75 seconds | Proofs Failed: 0
[  0]          2..6921       ( 0.03% ) C3 Park Validated in 10.80 seconds | Proofs Failed: 0
[ 44]     304568..311486     ( 0.03% ) C3 Park Validated in 10.77 seconds | Proofs Failed: 0
[ 59]     408383..415301     ( 0.03% ) C3 Park Validated in 11.03 seconds | Proofs Failed: 0
[ 19]     131521..138439     ( 0.04% ) C3 Park Validated in 7.26 seconds | Proofs Failed: 0
...

Z1 plot
bladebit_cuda-windows-alpha3.exe -v -c xxxxxxxx -f xxxxxxxx -z 1 -n 1 -t 8 cudaplot g:/chia
Bladebit Chia Plotter
Version      : 3.0.0-alpha3-dev
Git Commit   : eb6df030b555fb35addc3d6762424d52826a5d82
Compiled With: msvc 19.33.31630
[Global Plotting Config]
Will create 1 plots.
Thread count          : 8
Warm start enabled    : false
NUMA disabled         : false
CPU affinity disabled : false
Compression Level     : 1
Benchmark mode        : disabled
[Bladebit CUDA Plotter]
Selected cuda device 0 : NVIDIA GeForce RTX 3080
CUDA Compute Capability   : 8.6
SM count                  : 68
Max blocks per SM         : 16
Max threads per SM        : 1536
Async Engine Count        : 5
L2 cache size             : 5.00 MB
L2 persist cache max size : 3.75 MB
Stack Size                : 1.00 KB
Memory:
Total                    : 10.00 GB
Free                     : 8.87 GB
Allocating buffers (this may take a few seconds)...
Kernel RAM required       :<PHONE_NUMBER>8  bytes ( 86060.07  MiB or 84.04  GiB )
Intermediate RAM required :<PHONE_NUMBER>   bytes ( 2860.07   MiB or 2.79   GiB )
Host RAM required         :<PHONE_NUMBER>68 bytes ( 135168.00 MiB or 132.00 GiB )
Total Host RAM required   :<PHONE_NUMBER>56 bytes ( 221228.07 MiB or 216.04 GiB )
GPU RAM required          :<PHONE_NUMBER>   bytes ( 5855.79   MiB or 5.72   GiB )
Allocating buffers
Generating plot 1 / 1: caf327b4f5d96e452afae7749ef105c5035181bcff0d2275df04df60b63afa7b
Plot temporary file: g:/chia/plot-k32-c01-2023-03-14-00-20-caf327b4f5d96e452afae7749ef105c5035181bcff0d2275df04df60b63afa7b.plot.tmp
Generating F1
Finished F1 in 2.85 seconds.
Table 2 completed in 10.79 seconds with<PHONE_NUMBER> entries.
Table 3 completed in 12.30 seconds with<PHONE_NUMBER> entries.
Table 4 completed in 34.84 seconds with<PHONE_NUMBER> entries.
Table 5 completed in 33.87 seconds with<PHONE_NUMBER> entries.
Table 6 completed in 29.84 seconds with<PHONE_NUMBER> entries.
Table 7 completed in 24.96 seconds with<PHONE_NUMBER> entries.
Finalizing Table 7
Finalized Table 7 in 12.93 seconds.
Completed Phase 1 in 162.67 seconds
Marked Table 6 in 7.24 seconds.
Marked Table 5 in 7.01 seconds.
Marked Table 4 in 6.81 seconds.
Marked Table 3 in 6.46 seconds.
Completed Phase 2 in 27.52 seconds
Compressing Table 2 and 3...
Step 1 completed step in 7.29 seconds.
Step 2 completed step in 7.86 seconds.
Completed table 2 in 15.15 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.09% ).
Compressing tables 3 and 4...
Step 1 completed step in 5.86 seconds.
Step 2 completed step in 6.08 seconds.
Step 3 completed step in 8.35 seconds.
Completed table 3 in 20.30 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.70% ).
Compressing tables 4 and 5...
Step 1 completed step in 6.17 seconds.
Step 2 completed step in 6.16 seconds.
Step 3 completed step in 8.51 seconds.
Completed table 4 in 20.84 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 82.25% ).
Compressing tables 5 and 6...
Step 1 completed step in 6.31 seconds.
Step 2 completed step in 6.39 seconds.
Step 3 completed step in 8.85 seconds.
Completed table 5 in 21.56 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 86.46% ).
Compressing tables 6 and 7...
Step 1 completed step in 6.33 seconds.
Step 2 completed step in 7.08 seconds.
Step 3 completed step in 9.81 seconds.
Completed table 6 in 23.22 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 100.00% ).
Serializing P7 entries
Completed serializing P7 entries in 2.98 seconds.
Completed Phase 3 in 104.07 seconds
Completed Plot 1 in 294.27 seconds ( 4.90 minutes )
g:/chia/plot-k32-c01-2023-03-14-00-20-caf327b4f5d96e452afae7749ef105c5035181bcff0d2275df04df60b63afa7b.plot.tmp -> g:/chia/plot-k32-c01-2023-03-14-00-20-caf327b4f5d96e452afae7749ef105c5035181bcff0d2275df04df60b63afa7b.plot
Completed writing plot in 4.94 seconds
Final plot table pointers:
Table 1:                0 ( 0x0000000000000000 )
Table 2:<PHONE_NUMBER> ( 0x000000004cd9a964 )
Table 3:<PHONE_NUMBER>6 ( 0x000000038f574004 )
Table 4:<PHONE_NUMBER>6 ( 0x00000006d706f0e0 )
Table 5:<PHONE_NUMBER>6 ( 0x0000000a2ecf7754 )
Table 6:<PHONE_NUMBER>1 ( 0x0000000db22fa71f )
Table 7:<PHONE_NUMBER>1 ( 0x00000011c219bf27 )
C 1    :             4096 ( 0x0000000000001000 )
C 2    :          1720916 ( 0x00000000001a4254 )
C 3    :          1721092 ( 0x00000000001a4304 )
Final plot table sizes:
Table 1: 0.00 MiB
Table 2: 13351.85 MiB
Table 3: 13434.98 MiB
Table 4: 13692.53 MiB
Table 5: 14390.01 MiB
Table 6: 16638.63 MiB
Table 7: 16884.46 MiB
C 1    : 1.64 MiB
C 2    : 0.00 MiB
C 3    : 1227.96 MiB

Validations:
I've tried to test it with:
bladebit_cuda-windows-alpha3.exe -t 12 validate -m G:/chia/z1/plot-k32-c01-2023-03-14-00-20-caf327b4f5d96e452afae7749ef105c5035181bcff0d2275df04df60b63afa7b.plot
Reading plot file into memory...
but i cant see in taskmanager any is reading the file in G disk.
8 of my 48 threads get 100% ussage  but does not show more info, it stay in:
Validating plot G:/chia/z1/plot-k32-c01-2023-03-14-00-20-caf327b4f5d96e452afae7749ef105c5035181bcff0d2275df04df60b63afa7b.plot
K               : 32
Unpacked        : false
Maximum C3 Parks: 429204
[  0] Park range:          0..35767       Park count: 35767
[  2] Park range:      71534..107301      Park count: 35767
[  4] Park range:     143068..178835      Park count: 35767
[ 11] Park range:     393437..429204      Park count: 35767
[  7] Park range:     250369..286136      Park count: 35767
[ 10] Park range:     357670..393437      Park count: 35767
[  6] Park range:     214602..250369      Park count: 35767
[  8] Park range:     286136..321903      Park count: 35767
[  3] Park range:     107301..143068      Park count: 35767
[  5] Park range:     178835..214602      Park count: 35767
[  1] Park range:      35767..71534       Park count: 35767
[  9] Park range:     321903..357670      Park count: 35767
does not show more text after +5 mins. Still testing.

With Chia plots check:
The Z0 plot from log on top:
chia plots check -n 50
2023-03-14T00:38:59.097  chia.plotting.check_plots        : INFO     Loading plots in config.yaml using plot_manager loading code (parallel read: True)
2023-03-14T00:38:59.207  chia.plotting.cache              : INFO     Loaded 427834 bytes of cached data
2023-03-14T00:38:59.363  chia.plotting.cache              : INFO     Parsed 564 cache entries in 0.16s
2023-03-14T00:38:59.425  chia.plotting.check_plots        : INFO     event: started, loaded 0 plots, 1 remaining
2023-03-14T00:38:59.425  chia.plotting.manager            : WARNING  Plot G:\chia\z0\plot-k32-2023-03-13-22-27-2023-03-14T00:38:59.425  chia.plotting.check_plots        : INFO     event: batch_processed, loaded 1 plots, 0 remaining
2023-03-14T00:38:59.425  chia.plotting.check_plots        : INFO     event: done, loaded 1 plots, 0 remaining
2023-03-14T00:39:00.441  chia.plotting.check_plots        : INFO
2023-03-14T00:39:00.441  chia.plotting.check_plots        : INFO
2023-03-14T00:39:00.441  chia.plotting.check_plots        : INFO     Starting to test each plot with 50 challenges each
2023-03-14T00:39:00.441  chia.plotting.check_plots        : INFO     Testing plot G:\chia\z0\plot-k32-2023-03-13-22-27-3d6a764cd3ba1be7fd28215e6db12e8850b43ea92af0d836dae94771a5a25e13.plot k=32
2023-03-14T00:39:00.441  chia.plotting.check_plots        : INFO        Pool contract address:  xch1fqq6pzznk0fcda6cnejayv9lXXXXXXXXXXX
2023-03-14T00:39:00.441  chia.plotting.check_plots        : INFO        Farmer public key:      93b561e3666f2776d446fb4237fa5bXXXXXXXXXXXXXXX
2023-03-14T00:39:00.441  chia.plotting.check_plots        : INFO        Local sk:               <PrivateKey 5b7ab83e63db6c70f06fe06ee29XXXXXXXXXXXXXX>
2023-03-14T00:39:00.472  chia.plotting.check_plots        : ERROR       Proofs 0 / 50, 0.0
2023-03-14T00:39:00.472  chia.plotting.check_plots        : INFO
2023-03-14T00:39:00.472  chia.plotting.check_plots        : INFO
2023-03-14T00:39:00.472  chia.plotting.check_plots        : INFO     Summary
2023-03-14T00:39:00.472  chia.plotting.check_plots        : INFO     Found 0 valid plots, total size 0.00000 TiB
2023-03-14T00:39:00.472  chia.plotting.check_plots        : WARNING  1 invalid plots found:
2023-03-14T00:39:00.472  chia.plotting.check_plots        : WARNING      1 bad plots:
2023-03-14T00:39:00.472  chia.plotting.check_plots        : WARNING  G:\chia\z0\plot-k32-2023-03-13-22-27-3d6a764cd3ba1be7fd28215e6db12e8850b43ea92af0d836dae94771a5a25e13.plot
The Z1  plot log.  Normal error: Standard chia/harvester does not recognize compressed plots.
chia plots check -n 50
2023-03-14T00:45:03.051  chia.plotting.check_plots        : INFO     Loading plots in config.yaml using plot_manager loading code (parallel read: True)
2023-03-14T00:45:03.160  chia.plotting.cache              : INFO     Loaded 427834 bytes of cached data
2023-03-14T00:45:03.300  chia.plotting.cache              : INFO     Parsed 564 cache entries in 0.14s
2023-03-14T00:45:03.363  chia.plotting.check_plots        : INFO     event: started, loaded 0 plots, 1 remaining
2023-03-14T00:45:03.379  chia.plotting.manager            : ERROR    Failed to open file G:\chia\z1\plot-k32-c01-2023-03-14-00-20-caf327b4f5d96e452afae7749ef105c5035181bcff0d2275df04df60b63afa7b.plot. Invalid plot header magic Traceback (most recent call last):
File "chia\plotting\manager.py", line 274, in process_file
ValueError: Invalid plot header magic
2023-03-14T00:45:03.379  chia.plotting.check_plots        : INFO     event: batch_processed, loaded 0 plots, 0 remaining
2023-03-14T00:45:03.379  chia.plotting.check_plots        : INFO     event: done, loaded 0 plots, 0 remaining
2023-03-14T00:45:04.394  chia.plotting.check_plots        : INFO
2023-03-14T00:45:04.394  chia.plotting.check_plots        : INFO
2023-03-14T00:45:04.394  chia.plotting.check_plots        : INFO     Summary
2023-03-14T00:45:04.394  chia.plotting.check_plots        : INFO     Found 0 valid plots, total size 0.00000 TiB
2023-03-14T00:45:04.394  chia.plotting.check_plots        : WARNING  1 invalid plots found:
2023-03-14T00:45:04.394  chia.plotting.check_plots        : WARNING      1 unopenable plots:
2023-03-14T00:45:04.394  chia.plotting.check_plots        : WARNING  G:\chia\z1\plot-k32-c01-2023-03-14-00-20-caf327b4f5d96e452afae7749ef105c5035181bcff0d2275df04df60b63afa7b.plot

Thank you for taking the time to get me this info. Does querying a few f7 result in challenges from a compressed plot?
Could you try validate --f7 <value> <path_to_compressed_plot> where <value> is a number between 0 and 1^32. It's normal for it to return a message like "f7 not found". But if it has an error looking it up, it will exit with an error. You could try fetching a few (maybe around 0-20)?
I spent all day yesterday experimenting on windows to no avail. All plots continue to come out valid on my side, however I am on windows 11. I might try setting up a windows 10 machine.
Downgrading to 256G of RAM also did not yield any issues, so it seems like it is not related to that.
As table entry count and pruned entry count appear to be exactly the same when I use one of your plot ids, it seems like the issue happens at the very end during phase 3, at the point of compressing to parks plot serialization. However, I've no findings yet. I apologize for the inconvenience.

Like that yes. But could you try with a sequence from 0-20? It ought to at least have 1. If you get the same error from 0-20, then this might indicate that the C tables are the ones that are corrupted.

Installed windows 11 and alpha 3 and was pleasantly surprised. Plots are valid. A great reason to switch to w11.

Well that's the second confirmation today we've got that plots under win11 work fine. I will have to indeed investigate on a win10 machine

Could not find f7 1 in plot.
Could not find f7 2 in plot.
Could not find f7 3 in plot.
Could not find f7 4 in plot.
Could not find f7 5 in plot.
Could not find f7 6 in plot.
Could not find f7 7 in plot.
Could not find f7 8 in plot.
Could not find f7 9 in plot.
Could not find f7 10 in plot.
Could not find f7 11 in plot.
Could not find f7 12 in plot.
Could not find f7 13 in plot.
Could not find f7 14 in plot.
Could not find f7 15 in plot.
Could not find f7 16 in plot.
Could not find f7 17 in plot.
Could not find f7 18 in plot.
Could not find f7 19 in plot.
Could not find f7 20 in plot.
Could not find f7 21 in plot.
Could not find f7 22 in plot.
Could not find f7 23 in plot.
Could not find f7 24 in plot.
Could not find f7 25 in plot.

That should be enough for now, I appreciate it. At the very least the C tables (initially written to plot file right after phase 1), are faulty.

Microsoft Windows Server 2019 Datacenter 17763.4131 is bad plots

That should be enough for now, I appreciate it. At the very least the C tables (initially written to plot file right after phase 1), are faulty.

I've updated to Windows 11.
Same scripts/keys.
Z0 uncompressed plots are Valid
Z1 compressed plots are Valid
(I have yet win10 in another SSD if you need some more test)

BBC Validate -m /x/x.plot
Park (xxxxx) proof fetch failed for f7 (xxxxxxx) local (0) = xxxxxxx (0x000000 ...
Compressed Plots C6 & C7 the same output.
Ubuntu 22.1

I have a slightly different validation error...
created one compressed plot on a Linux machine with compression level 7 (-z 7) then moved that file into my current plots directory with some uncompressed plots.
when I ran - chia plots check -g xxxxx    --- chia blew an error. (Invalid plot header magic Traceback)
Does the newest non-beta release of chia not support farming compressed plots yet?
Side note.. I have one full node server that runs the full node and farmer.
and 2 harvester servers that have the plots and run the harvester only... the chia check plots was run on the harvester.
all my servers are Linux machines.
bladebit validation runs just fine

No, current Chia releases do not support farming compressed plots.

Have somebody testet to create a plot in Linux and valdiate it on windows 10? I have no resources for this test... Maybe the plots on windows are good and the probleme is the validation.

In Linux, the made plots are valid, and are checked in Windows. The problem is that the plots made in windows (except w11) are bad.

i also use Linux and when i Validate , i came out ( proof fetch failed for f7 ) so how we know these plots are valid?

share a beta that supports already compressed plots

share a beta that supports already compressed plots

There's an alpha build for compressed CPU farming available in the beta program.

I build my Farm since Febuary 2023 and cant wait to fill 274 TB with Compressed Plots!
@harold-b Will erveryone get the Chance to use the beta programm ?
Thank you!
S.S

Yes, you can sign up on the link I posted above. Everything is open source, so anyone can build it themselves also.
Please keep in mind that we're still in alpha stage, so things may be subject to change. Meaning, some parameters might still change for generating compressed plots, rendering old ones incompatible if we do.

Yes, that would be a risk to plot all 274tb but for testing a good experience!
Thank you @harold-b

Upgrade to Win 11 an the problem near the same.
SystemInfo.ps1
SystemName="ADAM-PC-THREADR"
OS="Microsoft Windows 11 Pro 10.0.22621"
SystemVendor/Model="Gigabyte Technology Co., Ltd./TRX40 AORUS PRO WIFI"
CPU="AMD Ryzen Threadripper 3960X 24-Core Processor  (C:24|T:48)"
GPU="NVIDIA GeForce RTX 4070 Ti"
GPUSKU="Lovelace"
GPUArch="N/A"
DriverVersion="531.18"
PCIeLink="PCIe 4 x16"
DRAM="256GB, 8x32GB , 2666MT/s"
PLOTTER______________________________________________________________________________________
bladebit_cuda-windows-alpha3.exe -n 1 --compress 1 -f XXX-c XXX cudaplot E:\ChiaBB\
Bladebit Chia Plotter
Version      : 3.0.0-alpha3-dev
Git Commit   : eb6df030b555fb35addc3d6762424d52826a5d82
Compiled With: msvc 19.33.31630
[Global Plotting Config]
Will create 1 plots.
Thread count          : 48
Warm start enabled    : false
NUMA disabled         : false
CPU affinity disabled : false
Farmer public key     : XXX
Pool contract address : XXX
Compression Level     : 1
Benchmark mode        : disabled
[Bladebit CUDA Plotter]
Selected cuda device 0 : NVIDIA GeForce RTX 4070 Ti
CUDA Compute Capability   : 8.9
SM count                  : 60
Max blocks per SM         : 24
Max threads per SM        : 1536
Async Engine Count        : 1
L2 cache size             : 48.00 MB
L2 persist cache max size : 36.00 MB
Stack Size                : 1.00 KB
Memory:
Total                    : 11.99 GB
Free                     : 10.79 GB
Allocating buffers (this may take a few seconds)...
Kernel RAM required       :<PHONE_NUMBER>8  bytes ( 86060.07  MiB or 84.04  GiB )
Intermediate RAM required :<PHONE_NUMBER>   bytes ( 2860.07   MiB or 2.79   GiB )
Host RAM required         :<PHONE_NUMBER>68 bytes ( 135168.00 MiB or 132.00 GiB )
Total Host RAM required   :<PHONE_NUMBER>56 bytes ( 221228.07 MiB or 216.04 GiB )
GPU RAM required          :<PHONE_NUMBER>   bytes ( 5855.79   MiB or 5.72   GiB )
Allocating buffers
Generating plot 1 / 1: 2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336
Plot temporary file: E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot.tmp
Generating F1
Finished F1 in 1.58 seconds.
Table 2 completed in 6.75 seconds with<PHONE_NUMBER> entries.
Table 3 completed in 13.36 seconds with<PHONE_NUMBER> entries.
Table 4 completed in 18.78 seconds with<PHONE_NUMBER> entries.
Table 5 completed in 19.33 seconds with<PHONE_NUMBER> entries.
Table 6 completed in 16.59 seconds with<PHONE_NUMBER> entries.
Table 7 completed in 14.38 seconds with<PHONE_NUMBER> entries.
Finalizing Table 7
Finalized Table 7 in 8.00 seconds.
Completed Phase 1 in 98.92 seconds
Marked Table 6 in 4.78 seconds.
Marked Table 5 in 4.39 seconds.
Marked Table 4 in 4.30 seconds.
Marked Table 3 in 4.28 seconds.
Completed Phase 2 in 17.76 seconds
Compressing Table 2 and 3...
Step 1 completed step in 4.99 seconds.
Step 2 completed step in 4.99 seconds.
Completed table 2 in 9.98 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.09% ).
Compressing tables 3 and 4...
Step 1 completed step in 4.54 seconds.
Step 2 completed step in 4.90 seconds.
Step 3 completed step in 5.38 seconds.
Completed table 3 in 14.82 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 80.69% ).
Compressing tables 4 and 5...
Step 1 completed step in 4.52 seconds.
Step 2 completed step in 4.94 seconds.
Step 3 completed step in 5.44 seconds.
Completed table 4 in 14.90 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 82.25% ).
Compressing tables 5 and 6...
Step 1 completed step in 4.56 seconds.
Step 2 completed step in 5.04 seconds.
Step 3 completed step in 5.66 seconds.
Completed table 5 in 15.26 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 86.45% ).
Compressing tables 6 and 7...
Step 1 completed step in 4.59 seconds.
Step 2 completed step in 5.36 seconds.
Step 3 completed step in 6.29 seconds.
Completed table 6 in 16.25 seconds with<PHONE_NUMBER> /<PHONE_NUMBER> entries ( 100.00% ).
Serializing P7 entries
Completed serializing P7 entries in 2.17 seconds.
Completed Phase 3 in 73.38 seconds
Completed Plot 1 in 190.06 seconds ( 3.17 minutes )
E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot.tmp -> E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Completed writing plot in 4.65 seconds
Final plot table pointers:
Table 1:                0 ( 0x0000000000000000 )
Table 2:<PHONE_NUMBER> ( 0x000000004cd41d88 )
Table 3:<PHONE_NUMBER>0 ( 0x000000038f492e78 )
Table 4:<PHONE_NUMBER>0 ( 0x00000006d6e69484 )
Table 5:<PHONE_NUMBER>0 ( 0x0000000a2e92a698 )
Table 6:<PHONE_NUMBER>0 ( 0x0000000db1c88962 )
Table 7:<PHONE_NUMBER>5 ( 0x00000011c167cf69 )
C 1    :             4096 ( 0x0000000000001000 )
C 2    :          1720432 ( 0x00000000001a4070 )
C 3    :          1720608 ( 0x00000000001a4120 )
Final plot table sizes:
Table 1: 0.00 MiB
Table 2: 13351.32 MiB
Table 3: 13433.84 MiB
Table 4: 13690.75 MiB
Table 5: 14387.37 MiB
Table 6: 16633.95 MiB
Table 7: 16879.72 MiB
C 1    : 1.64 MiB
C 2    : 0.00 MiB
C 3    : 1227.62 MiB

PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe -t 4 validate -m  E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Reading plot file into memory...
Validating plot E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
K               : 32
Unpacked        : false
Maximum C3 Parks: 429083
[  0] Park range:          0..107271      Park count: 107271
[  3] Park range:     321813..429083      Park count: 107270
[  1] Park range:     107271..214542      Park count: 107271
[  2] Park range:     214542..321813      Park count: 107271
[  0] Park 0 proof fetch failed for f7[127] local(127) = 125 ( 0x000000000000007d )
[  2] Park 214542 proof fetch failed for f7[2145420368] local(368) =<PHONE_NUMBER> ( 0x000000007fffe1dc )
[  1] Park 107271 proof fetch failed for f7[1072711197] local(1197) =<PHONE_NUMBER> ( 0x00000000400015b5 )

after 1 hour i abortet this
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe -t 4 validate -m  --f7 1 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe -t 4 validate -m --f7 1 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe -t 4 validate -m --f7 2 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe -t 4 validate --f7 2 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 2 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 3 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 4 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 5 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Could not find f7 5 in plot.
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 6 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 7 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 8 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Could not find f7 8 in plot.
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 9 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 10 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Could not find f7 10 in plot.
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 11 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Could not find f7 11 in plot.
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 12 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 13 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 14 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 15 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Could not find f7 15 in plot.
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 16 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 17 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Could not find f7 17 in plot.
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 18 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
Could not find f7 18 in plot.
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 19 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads> .\bladebit_cuda-windows-alpha3.exe validate --f7 20 E:\ChiaBB\plot-k32-c01-2023-03-18-13-26-2753974b49bdafafcecfd5f834ac37b10bb1a732476b287543c1ff050a8f4336.plot
PS C:\Users\micro\Downloads>

I checked the old plots made by MM, there is also an if the --f7 parameter is up to 20 (Could not find f7 13 in plot)

Now plots made in Windows 11 send proofs to the pool. Everything is fine.

bladebit_cuda-windows-alpha3.exe validate --f7 123 C:\hdd\18tbSegSAS\bb\plot-k32-2023-03-16-03-06-3a76176d8b31b63831b66d2d44a9bd1ee8c2de4d68a0d101e9ab6a705a1a0906.plot
64f250e4d4e39dfbf228d261f4a1fa84e204284653f8fc81926b9034041351311fe4559c702753214039a4826cae1226c1c0e6706fd6dcdbe0ae2da96ae1c622da3e299e5c1df6ad6d81035a02ff4f59c3fa468c8c17bb26ca83789925e225b52a96bc9c4e47732fe3d65dfdd282d232f08df31792d95b1b30b3d0f5ff400b951a19c74a84f6c388bef0e53177da2eb39db52b14c0e977badaf136502233edc53a33a43aa582b747b3b5fd7c8bf51f9ad7cf97a53924830df5f7610ca26cd25fbc13fdfce3031dea3eb7b35cdc0daf6ac16e9b36e7ccf2a1f9e6d7098a10a5f45ced640935ee569c2b14222b663aaa00e03f939bda7dda45f40992523d0a9bd8

bladebit_cuda-windows-alpha3.exe validate --f7 13 C:\hdd\18tbSegSAS\bb\plot-k32-2023-03-16-03-06-3a76176d8b31b63831b66d2d44a9bd1ee8c2de4d68a0d101e9ab6a705a1a0906.plot
Could not find f7 13 in plot.

bladebit_cuda-windows-alpha3.exe validate --f7 13 C:\hdd\18tbWD1\mm\plot-k32-2023-02-04-10-31-d4dacf936a6c6349105e8f0145960180a3774bfadba08e49120c7b8388ac5703.plot
Could not find f7 13 in plot.

I see this is somewhat of an old thread, but the problem appears to be persisting for Windows even in the newer builds.
I'm seeing all my compressed plots (c7) being invalid even with the latest 4.3 alpha on Windows Server 2019. No errors when plotting, no errors when harvesting them with the v2 alpha software, but they all fail the plot check and are noticeably absent from pooling stats. Stupidly I plotted about 24 18TB disks before doing the plot check, not a good plot among them.
Switched the machine over to Linux and it's creating valid plots.
I've also commented on this in the bladebit-alpha discord channel (same username), hopefully not many people as silly as me! It's easy to think the problems was fixed and bladebit would be making valid plots on Windows as the last comment on here being nearly 3 months ago, and new builds for Windows are being pushed out.
The machine is "dual boot" (sadly that it involves changing cables and that involves getting it out of a rack), but if you would like me to try some things out or need some extra information let me know.

By now (alpha 4.3), still occurs on some Windows 10.

Work is being done on the disk hybrid that might fix this. Unfortunately we are still not able to reproduce on our machines, but hopefully soon when we have the code ready some folks can test on machines where the issue does occur to see if it is solves it.
I appreciate the patience you've all have had.

Hello, is there a solution to this problem now, I upgraded to win11 and still can't p out the effective field

Would love too see this fixed.


Dynamic DNS entries should support HA via CARP tracking

Title says most of it here. For many common configurations where the WAN IP is dynamic (DHCP, SLAAC, etc.) and an HA cluster is implemented, each side of the HA cluster will have a different IP address.
The simplest fix that I can think of is to add a checkbox "Track active cluster member" and a CARP selection drop-down. Then for the entry to basically be 'disabled' on the backup side, and to use devd to trigger save and force update.
e.g. devd action:
notify 100 {
    match "system" "CARP";
    match "type" "MASTER";
    action "/usr/local/etc/rc.dyndns"
}

However, it is not at all clear to me where the enable/disable is or if there is any sort of API method.

Shouldn't hooking into https://github.com/opnsense/core/blob/master/src/etc/rc.carpmaster be enough?

I don't believe so, at least not with the current setup of Dynamic DNS. I actually cannot find in the code (I am not a PHP guy) where it is doing the enable/disable. And for certain dynamic services - especially HE Tunnelbroker - an accidental update, partial failover, or split-brain scenario causes problems for both the user and provider.
The alternative would be to do something like a 'check my IP' on CARP actions for all Dynamic DNS entries with a 'follow HA' option set, but I definitely do not have the php-fu required for that degree of refactoring.

Well, in a nutshell you want to update DynDNS when MASTER event occurs on carp(4) devices, no?
I wrote a bit to make this fully pluggable https://github.com/opnsense/core/commit/177ca719093f so you can even try to register your own events on master.
Ideally, if this only pertains to dyndns (and possibly rfc2136) we can add plugin files for it.

More accurately, it needs to update on both MASTER and BACKUP events to prevent potential conflict. So the flow actually looks like this:
MASTER State -> Transition -> for ha in DynDNS_Entries where ha=true, Disable DynDNS entry on BACKUP -> for ha in DynDNS_Entries where ha=true, Enable and Force Update on MASTER -> Transition Complete
The HA flag is particularly important, because one would presume most folks running HA are running mixed entries where each host has one or more uniques plus a shared. Or they may have certain BGP-aware tunnel configurations. So only DynDNS entries that are enabled for HA should be failed over. That also means the replication of those DynDNS entries needs to be sync'd between nodes - no idea at all how to go about implementing that.

There is a framework now to pull this off by adding files to /usr/local/rc.syshook.d/carp to take care of additional requirements, which can be used by plugins directly without the need to modify core.
This docs page needs updates, but it's the same facility slightly improved: https://docs.opnsense.org/development/backend/autorun.html
I'm leaving this up for grabs, ZFS and syslog-ng is still on my shortlist for 18.7.

@AdSchellevis @fichtner I noticed there's been some poking at dyndns very recently. I'm actually hoping to start making some progress on this very shortly. Would either of you be available for any questions that come up?
While I am here, I have come up with a rough outline of the proposal to expand on the POC I did elsewhere.

Add "Failover this entry" checkbox to DynDNS entry configuration page
Add configuration element $dynFailover = $conf['dynFailover'] type boolean
Add function dyndns_xmlrpc_sync to perform synchronization

One element that is hanging me up is that I (and others) do have a requirement for both 'stay with the firewall' and 'follow the failover' entries at the same time. That I am not really a PHP guy does not help matters. Would this be roughly correct to limit the sync'd entries to those marked for failover, or is this going to overwrite local as well?
function dyndns_xmlrpc_sync()
{
    $result = array();
    foreach( $config['dyndnses']['dyndns'] as $dyn_index => $dummy_dyn ) {
        if( (string)$config['dyndnses']['dyndns'][$dyn_index]['dynFailover'] === "1" ) {
            $result['id'] = 'dyndns';
            $result['section'] = 'OPNsense.DynDNS';
            $result['description'] = gettext('Dynamic DNS');
        }
    }
    return array($result)
}

That's more @AdSchellevis area than mine (HA). That may be a viable solution to selectively sync shared entries. The only issue is to be able to avoid backup nodes updating these entries when they aren't MASTER. Not sure what the quickest way is to check this.

@rootwyrm the code shifts are a result of cleanups, I don't use dyndns myself, but I gladly answer questions about HA topics if I can.
The section in your example function probably should be dyndnses.dyndns by the way, OPNsense.DynDNS doesn't exist.

@AdSchellevis thankfully, having already proved the concept (mostly successfully no less) most of the questions are about how the HA actually works. (Also, thanks, wasn't sure if that was still named that. Is this something worth renaming in the same pass?)
The actual failover handling needs to be implemented using rc.syshook.d/carp which actually makes it easier since all that is required is to iterate over dyndnses.dyndns and force update.
My biggest concern is the sync problem. OPNsense doesn't have the concept of selective sync within a plugin itself. This is actually a pretty gnarly problem that crops up in frr, since each HA member should have a unique router ID (and FRR should, arguably, always run on both in many configurations.)
Dynamic DNS is simply the 'best and worst of worlds' here. The user must specify in the plugin that they want an entry to fail over, and that's nicely self contained (in theory.) However, it's the worst in that how do we preserve entries NOT being sync'd? Will they be left alone on the sync (append-if-not-exist, overwrite-if-exist) or will it wipe all entries?
To give a clear example of this scenario:
**Firewall One**
ids0.example.com        noFailover      NameCheap
ids0.internal.pvt       noFailover      RFC
vpnaccess.example.com   Failover        NameCheap
12345678                Failover        HE.net Tunnelbroker (IPv6 Tunnel)

**Firewall Two**
ids1.example.com        noFailover      NameCheap
ids1.internal.pvt       noFailover      RFC
vpnaccess.example.com   Failover        NameCheap
12345678                Failover        HE.net Tunnelbroker (IPv6 Tunnel)

ids1.* would stay with the firewall (no sync flag set, so no configuration passing over?) vpnaccess and 12345678 are failover, and may not exist on Firewall Two. Would syncing them destroy the ids1.* entries on Firewall Two or would it append?

I'm not using dyndns myself, the plugin is quite old and likely needs quite some maintenance (not planned at our end).
Without knowing if it is actually possible what you want to achieve, to me it sounds quite challenging to serve both active and inactive nodes from the same machine using the same provider.
Usually (for most other protocols), you would use outbound NAT to use the carp address on both machines, for which there's always only one active at the same time.
I think this should already work out of the box for most dyndns providers, but since I don't use dyndns myself, I'm not 100% sure.
It might already be possible to use different providers for carp and non-carp addresses if these services have easy to detect addresses (outbound nat failover using carp, the other service using its other address).

No question that some serious TLC is required here, but I probably don't have the PHP-fu to do what's required, which really is a total rewrite. DynDNS is an extremely critical feature for a lot of users.
As far as the model, you're actually getting the DynDNS model a bit backwards. DynDNS is always associated to one or more WAN IPs which are specific to the host regardless of CARP state or interface similarity. That is unless you want to switch to the FreeWALL model which uses allocated OUI to do MAC spoofing so the WAN IP follows the master firewall at all times. But as I mentioned on IRC, that model necessitates digging tentacles deep into devd and significant kernel patches to alter IPv6 LL duplicate detection handling.
Without the WAN IP following the master, the more correct way to look at plugins like DynDNS is to consider each entry with regards to the syncing, and CARP as purely a pivot point. So a combination of switching from Master/Slave 'all-in' to Host A/B, Entry [0-999], and on-off. Basically, a much more granular model.  This is something that is going to increasingly required with more logically complex plugins such as DynDNS, FRR, and so on. Examples of the contrary - simple plugins - would be HAProxy and Tor. (It's way easier for me to explain in person, I assure you.)
It's definitely easier to understand visually. Here is the existing XMLRPC sync model:

To achieve what end-users will require with DynDNS, the model has to look like this:

Of particular note here is the IPv6 GIF dynamic (gif(4) already follows master, which breaks HE.net tunnels on failover unless the DynDNS update to HE follows it as well.) Doing the discard from master in the plugin itself is the easy part; the outbound filter is the if( (string)$config['dyndnses']['dyndns'][$dyn_index]['dynFailover'] === "1" ). So it is solved by simply not sending the non-HA entries over the XMLRPC sync.
The biggest problem here upon digging in, is dyndnses.dyndns.id which is a sequence. So collisions will arise even with the outbound filter. As I recall, XMLRPC has a significant shortcoming (or advantage in this case) in that it does not zero out an array on sync. It will only overwrite and append. I think this might provide a reasonable compromise as it only requires the user delete entries on the slave side.
Long term, I think the real solution here will require some XMLRPC changes. However, I think the correct change there is to add support for something like plugin_xmlrpc_parse which runs on the receiver side. That would enable any plugin to selectively synchronize any/all elements.
If this sounds good to everyone, I think the route to take here is going to be this:

Change dyndnses.dyndns.id from integer to uuid and validate that this does not cause any negative impacts
Add configuration element dyndnses.dyndns.failover as boolean
Implement dyndnses.dyndns.failover filter in dyndns_xmlrpc_sync() function as described
Revisit if/when plugin_xmlrpc_parse is implemented

When both machines require different settings for a module, we usually don't sync these settings. (or sync on setup, then disable sync and change backup node).
Adding a marker in dyndns which reacts on being slave/failover could also work (maybe just read the xmlrpc peer, if none, then slave), in which case you can easily setup all on master.
I rather don't see a lot of logic going into the xmlrpc sync itself, but it you have some code, I'll happily take a look.

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


Add property autocomplete to Modus components Autocomplete and Text Input

Description
Adding a new property to set the autocomplete attribute for text inputs and the autocomplete input.
The property follows https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete.
Adding e2e tests to ensure changes on the property are honored.
References #1985
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

How Has This Been Tested?
Tested manually and in Storybook. Added e2e tests.
Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[X] I have checked my code and corrected any misspellings

Remove autocomplete property from modus-autocomplete.  Keep it on modus-text-input and default to off from inside the modus-autocomplete component.  If later on there is a use case to enable autocomplete for this modus-autocomplete then we can address how to update modus-autocomplete

Remove autocomplete property from modus-autocomplete. Keep it on modus-text-input and default to off from inside the modus-autocomplete component. If later on there is a use case to enable autocomplete for this modus-autocomplete then we can address how to update modus-autocomplete

These changes have been completed.  Thanks!


Wrong logic in write_small_response

write_small_response lacks check for request.content not None

Corrected in https://github.com/RobertoPrevato/BlackSheep/commit/d7c6a8bcca75fadcec986852fa4d1e5f92a06a9f


remove ibm packages

remove the two ibm packages to hopefully use less resources

Looks good to me, this doesn't break anything right?

Looks good to me, this doesn't break anything right?

I've tested on repl.it and I didn't see any problems... so hope not
If there are problems we could always just restore the poetry.lock file to before


Disable "Anonymous usage stats"

How can I set send_anonymous_usage_stats=False?
https://docs.getdbt.com/reference/global-configs/usage-stats

This is a great issue you brought up @ykuc since any cosmos profiles that are mapped from Airflow connections won't have the following block for dbt usage stats in the profiles.yml:
config:
  send_anonymous_usage_stats: False

which means it defaults to True when not used.
There are 2 workarounds you could have at the moment for preventing anonymous usage stats tracking:

Supply your own profiles.yml file to cosmos, see docs here on using your own file where you could add the config above. Though the limitation of this is that you won't be able to use Airflow connections.
As noted in dbt docs linked above you could also use the environment variables: DO_NOT_TRACK=1 or DBT_SEND_ANONYMOUS_USAGE_STATS=False. With cosmos currently you would have to use operator_args with either "append_env": True if you have the env var already set, or use "env": {"DO_NOT_TRACK": "1"}.

In Cosmos to add support for not sending usage stats, I think this could be added to BaseProfileMapping args and then it could be added to profile contents in the method below:
https://github.com/astronomer/astronomer-cosmos/blob/e1f34ea424b8940f1c06660554298008876ea11b/cosmos/profiles/base.py#L175-L180


Rename *patron_pid to patron_id

In Invenio, users are not records, and they don't have a Persistent Identifiers, but they have a user ID.

@jma @iGormilhit is this something that you agree to start working on it?

On our side, this does not make sense anymore. Patron are "kind of" records.


Sending Title Launch Message all of a sudden ignored by console

HI guys,
The SmartGlass client seems to be having issues getting through to the xbox console when sending Title Launch requests.
I noticed that the smartglass app was updated the other day on my android device. I'm not sure if there was a console update, however, this issue seemed to begin around the same time.
All other messages seem to be retrieved/sent  successfully.
Should mention that after a TitleLaunch Message is sent, the CLI will no longer update with Messages.

Yep, same with Python, think it has been patched (tested both versions on the same console today).
Working console ver: 10.0.17763.4086
Patched console ver: 10.0.11763.4088

Let's just wait and see if it gets fixed ;) Thanks for the reports.

@4reeeal is it possible to downgrade the xbox OS version to test? I'm experiencing the same failure (404 in the logs when fetching titlehub.xbox.com, and the official SmartGlass app likewise fails to launch titles/"Play on Xbox"). My console is on the .4088 version as well, evidently having updated itself 2 days ago.

Nope, it is not possible to downgrade the Xbox OS.
titlehub returning 404 indicates a change in their XBL API

Boy, I hope this gets resolved my M$ soon. It's been a week and my entire custom alexa skill revolves around this feature... LOL

Are we really saying "M$" on a project written in C# for a Microsoft product that we should be happy Microsoft doesn't take issue with? What year is this?

Are we really saying "M$" on a project written in C# for a Microsoft product on a free Microsoft owned open source platform, that we should be happy Microsoft doesn't take issue with? What year is this?

I know, it's a force of habit. LOL. Let us not forget they did give away their last operating system for free and have kept our wonderful Github running the same way it has always ran after its acquisition too. I'm a fanboy. :)

Has the situation possibly changed (for the better?) with a recent systemupdate?

No changes (still broken) here. Have received no console updates since the one that coincided with this breaking, and the "Xbox App" on phone or Windows laptop likewise fails to switch apps via "Play on Xbox" ... same symptoms that nothing at all occurs. Haven't taken the time to intercept the traffic yet and see whether the apps are calling through the same broken API.

I filled out a bug report for the Smartglass app with MS the other day. I'm sure they know about the issue and I bet it'll be resolved in the next system update/App update.
Of course, I get these great libraries working in my service application, and then this happens...
At least I can still feed my Machine learning dataset with the content that is still provided by these libraries... So Bonus!

Is the bug report filed anywhere publicly that other impacted folks should go upvote?

Is the bug report filed anywhere publicly that other impacted folks should go upvote?

Trying to find the thread, I think it was sent via message. The xbox website seems to get you running in circles. Hope this issue gets fixed soon :)

Has anyone else been able to send launch requests through the API with any of the recent console updates? :)

No, no luck. :(
Have you had success?
My Xbox One was updated April 17 to 10.0.18362.2018 (19h1_release_xbox_dev_1904.190410-1845). No chnage in behavior, though.

A new update tonight for Xbox Insiders, still no joy.
Waiting for a new Smartglass update on my phone to see if that changes anything.

Fingers crossed a new version of smartglass was just released on Android. I have faith that the launch commands are fix.
Testing now

No! It's not fixed. Smartglass will not launch titles... Even from the Android app. 😐
That is just not good. 😞

Sadly this feature HAS been disabled by Microsoft. I would venture to say that this was due to potential security issues. Launching Titles via code allowed you to launch a title via string URI or with uint TitleId. When launching as uint Titled, you had the ability to pass parameters with the call. I played with this doing some Fuzzing and strange things happened on the console to the point that that there could be a exploit somewhere. Someone may have beat me to it as this was patched very quickly and quietly. So.... where can we go from here. I have developed two work around's that still work.  So for those that would like to try their hand here you go.

(Ugly, but simple) Launch a Title via pre-defined button combos. It works but you have to see the results happening on the console.

Create a UWP bridge app that is REST enabled (or WebSockets) that accepts the title launch command and converts it to a local app URI and calls it locally on the console. Create a store package and submit the app to the store (you can hide it from the public, don't worry) this way you can get your bridge installed on the console in RETAIL mode. This method seems to work fine for now, until I'm sure MS will eventually lock this down too. Whatever happened to actually owning the things you buy? For the general consumer this is good, but not advanced users.

Confirmed that all title launch features of the iOS Xbox app are also non-functional now.

Tux, Joel, should we not exclude the Launch call now? Looking at MS new API's this is definitely a no-no anymore. Basics functions will still work, but this library is going to need some refreshment on the new API's, as it all depends on the consoles OS which has changed. Basically now we're locked down to just key/button presses, and thankfully, Nano for now but that is changing also. This project is dead unless all sub repos are updated with new API and get to a standard. (One library refers to token as this and another repo refer to token as x. Get common. and it breaks shit) The new API support the basic still but coming in the future MS is going to RemoteDevicesAPI. So unless this project gets together and Updates  accordingly it is a dead project. Might as well just use the winmd's that MS provides. Sad, but true.

Joel, Sorry I know your in a fit right now. God-forbid you say something bad about Ms. Sure they offer alot for free, and 'try' to be opensource but their efforts are disguised. Wolf in sheep clothing. But i will tell you this... When xCloud and Project Scarlett are official, this library will be just what you get in the winmd. It's just a wrapper. How's it feel to be spitted by Ms changes? that's what i thought, Exactly.

I just want my Alexa to start apps on my Xbox. It's more of an Amazon thing because they haven't released the skill in Canada, so I rolled my own OWIN service which accepts Amazon Alexa requests and sends them to the Xbox.
At least I can turn the Xbox on and off.
I guess I can call on Cortana for the rest.

Project rome can launch protocols (ie netflix://) however it is native UWP /com library only and does not seem to talk directly to the device (looking at packet capture).  Not a great substitute.  There is the graph API but it does not seem to be able to do the same.


Akamai nodestream catchup

Many updates for Akamai logic and nodestream architecture

@stuart-macleod-akamai was there an issue using the !config values? We will need to use these to pass in values otherwise there can be conflicting env's for multiple nodestream plugins in the future.

Yes, the !config values caused the following error, so I removed them temporarily until we could pin it down
could not determine a constructor for the tag '!config'
  in "C:\Users\smacleod\AppData\Local\pypoetry\Cache\virtualenvs\test1-WxuTdTEg-py3.11\Lib\site-packages\nodestream_akamai\cps.yaml", line 3, column 15****

Nodestream is 0.8.14, Windows. Any ideas?

@stuart-macleod-akamai did you add in the plugin-config section to your pipeline.yaml?
https://nodestream-proj.github.io/nodestream/0.9.0/docs/guides/project-plugins/?h=plugin#configuration-for-project-plugins


Get-OneloginEvent filtering doesn't work right

using a filter and the -since and -until parameters doesn't seem to work right - filtering to a user seems to return events for all users.

-Since and -Until are not in the "Filter" parameter set, and this appears to set the parameter set to "Since." Fixed.


[tiny-build] Bump up promtool, amtool, cortextool

https://github.com/prometheus/prometheus/releases/tag/v2.39.1
https://github.com/prometheus/alertmanager/releases/tag/v0.24.0
https://github.com/grafana/cortex-tools/releases/tag/v0.10.7

Hi, and thanks for contributing!
Note: If you are part of Qlik:
follow the process outlined on the internal developer portal instead.
Reach out to<EMAIL_ADDRESS>if you do not have access to that developer portal.

Before we can handle your pull request we need you to sign our contributor license agreement.
This is a one-time process and enables you to contribute without hassle to any of the qlik-oss repositories in the future.
And it only takes a few minutes! Here are some useful links to get you started:

Sign the CLA
Rationale behind the CLA
Qlik Open Source repository
Official Slack team

Having troubles? Feel free to reach out to us either here or on Slack!
Note: Once the CLA is sorted, you should rebase/touch this pull request to trigger an update of this CLA status.


Add focal loss tutorial.

Related issue: #361

IIRC, focal loss is specifically formulated to help out for detection tasks (like PASCAL). It was also originally introduced for RetinaNet which wasn't doing simple classification.
From the paper:

The Focal Loss is designed to address the one-stage object detection scenario in which there is an extreme imbalance between foreground and background classes during training (e.g., 1:1000).

A tutorial on MNIST classification isn't suitable. It's better to do a simple detection task using a single short detector, or if that's too complex, we can artificially imbalance the dataset to show where focal loss really shines.

Can we try on mnist that is labels are 1 or not.

I agree with @squadrick. I think an easy single stage anchor free object detector could be simple enough for a focal loss tutorial.
I.e. see focal loss in https://github.com/xuannianz/keras-CenterNet

@Squadrick @bhack I changed the dataset, now MNIST have just 3 categories 0, 1, and others, so dataset is imbalanced and loss graph are same as graph on paper.
Training bigger model will cost more time and colab is inefficient for this.(continuous timeout errors, etc.)

Tbh I feel like this is may be an unnecessary tutorial.

From a 'code-point-of-view' the usage of the focal loss is essentially just swapping sigmoid_cross_entropy_with_logits against sigmoid_focal_crossentropy anyways. The mathematical intricacies which justify using the focal loss over regular crossentropy are not addressed besides the copy of the SigmoidFocalCrossentropy docstring.
The tfa.__version__ is outdated by over half a year.
IMO one of the mistakes one could make when applying SigmoidFocalCrossentropy is wrong scaling of the model outputs depending on from_logits. This is not addressed in the tutorial.
The parameter alpha is not explained and the image from the paper omits alpha as well, hence the equation from the image does not actually represent the calculations performed by SigmoidFocalCrossentropy.
Gradient instability for small gamma is not addressed.
The create_model method in the tutorial defines a Sequential model, then builds and trains it as well, i.e. it does not just "create a model". I would also argue that rebuilding the entire model just for the sake of changing a loss hyper-parameter is not good practice, as this could be achieved by re-compiling the model as well.

I agree with @bhack that the most prominent use case for the focal loss is object detection. A tutorial on object detection which makes use of the focal loss would probably be a lot more informative. In that case it would also not be such a big problem to be less mathematically precise about the formulation of the focal loss itself.

/cc @WindQAQ @seanpmorgan Probably we need to deprecate focal loss before the next release https://github.com/keras-team/keras-cv/blob/master/keras_cv/losses/focal_loss.py

We have now a focal loss in Keras CV. I suggest you to port this in the Keras io repository:
https://github.com/keras-team/keras-io


The viewer can view the summary of the film by clicking on it, which includes the plot, rating, and showtime.

Definition of done:
As a Developer, I have to retrieve the necessary film information from the appropriate data source, such as a database or API. This data should include the film's plot, rating, and showtime information.

implementing the feature where  viewers can click on a flim to access the summery including plot,rating and showtime will greatly enhance the user experience and provide the valuable information at a glance

By implementing this, the platform can provide a delightful and informative experience to its users, encouraging them to explore and engage with the films available on the platform.


Problem with offhand and Elytra causing errors upon saving withv10 and v11 api 6 and 7

Problem with offhand and Elytra causing errors upon saving via server exit or timed save while server is running.
I did some tests on clean servers running nothing but luckyperms, pji  and pjc and all seem to have these problems.
I know this is not release builds and that you might know if these issues but just to make sure that they dont sneak in to new releases I am posting.
server versions tested on
spongevanilla-1.12-7.0.0-BETA-289
spongevanilla-1.11.2-6.1.0-BETA-11
pjc
project core-7.0.0-0.1.0
project core-6.1.0-0.1.0
pji
project inventories-7.0.0-0.11.0
project inventories-6.1.0-0.11.0
project inventories-6.1.0-0.10.0

You didn't post any errors or describe the problem..

My bad i forgot to paste the errors
What happens is that once you save or wait for the plugin to do a save once the server is running an error shows in the console and nothing more happens until the server is shutdown or the person that coursed the error disconnects then another series of errors is triggered and once the person logs on again that person is stuck in a "please wait until inventory is loaded" loop that requires me to clear that person inventory and restart the server.  I Have included both logs from when it happens and logs from when server has been restarted and the user have relogged.


WIP Add video quality selection

Implementing #7

@cemrich I fixed the codeformat and the wording issues. The last thing todo is to eliminate the duplicated tracks in the TrackSelection View. At the moment I display all video tracks that are selected by the TrackSelector. I thing I have to manipulate the array with the video tracks to eliminate the duplicated tracks.

@userdimi Awesome!
The quality switcher should show up inside the mediathek player, too. It is using the same player (service) so this should be no problem. Also, the menu item should be disabled when only one quality exists.
There are two more features that would work nicely with your implementation, but are not strictly needed:

Saving the last selected quality (at least for the current session, or across app restarts)
Allow only a maximum quality on metered connections (like Youtube)

Number one is tricky because not all channels or mediathek videos share the same quality settings. Both features should be separate from this pull request.

@cemrich I think that is not a big deal to implement the same quality button in the mediathek player and show it if more then one quality is available.
Your ideas for the two features are great! I will think about the details of the implementation and give you some feedback.
At the moment I stuck a little by overriding the TrackGroup of the TrackGroupArray. I wrote a detailed question with more information in the Exoplay Issue tracker: https://github.com/google/ExoPlayer/issues/6082
Maybe you have an idea how to solve the issue? I've commited my current changes to my feature branch so feel free to take a look on it.

@userdimi I don't see how you could use a filtered track list on the TrackSelectionView. However, you could provide a TrackNameProvider (maybe inherit from DefaultTrackNameProvider) and number the duplicate qualities. I don't know if that's possible with the TrackNameProviders information but it would indicate to the user that duplicate qualities are not a bug but fallback urls.

@cemrich Thank you for the hint. I will take a look at the TrackNameProvider. You are right, it's very uncool to remove the fallback URLs from the TrackSelector 😃

@cemrich I've implemented a CustomTrackNameProvider class. In this class I manipulate the displayed string and set "Fallback" prefix to duplicated tracks. I've implemented the "Quality" menu item in the mediathek player also. Thanks a lot for the great hint with the TrackNameProvider. I've pushed my changes so feel free to check it out. You can change the german wording of the "Fallback" prefix also

Thank you very, very much for your work!
I've added one last refactoring suggestion. If you don't want to change it, I'll merge inside a feature branch and refactor later :)

@cemrich You are welcome. I learned a lot by contributing to your project. I'll looking forward to see this feature in production 🙂
Like a wrote in the reply, will refractor the class and push the changes tomorrow

@cemrich I refactored the CustomTrackNameProvider class and pushed my changes. Thank's a lot for your feedback!


Make relative instead of absolute links

Please, let us finish the conversation. I'd like to hear what @ain has to say.
@ain To be honest I'm not sure I'm following.

a decision that is 2 years old, at its current pace, is probably already obsolete

Here you supposedly mean, that having absolute symlinks no longer makes sense? Or is it just a general statement?

The important matter is always to solve the problem in its scope and I didn't see it in Cap scope back in the days.

This supposedly means, that capistrano shouldn't have switched to absolute symlinks 2 years ago (back in the days). The problem should have been solved on the side of some other application.

It's a cerbot and server routing problem, not a Cap problem.

And this must mean, that the problem at hand (the one I've run into, with certbot) shouldn't be solved on capistrano's side.
Summing it up, it's not clear what's your take on capistrano using absolute symlinks nowadays.
Then, let me describe the issue I've run into, just in case. I have a pysical server with LXC containers. In each LXC container there's a site running. On a physical server I have nginx, which proxies HTTP requests to corresponding container based on Host header. To obtain SSL certificate for a site, I must tell certbot path to document root.
If I run certbot on a physical machine, I have no way to pass it path to document root, since symlink to current realease doesn't work outside of a container.
If I run certbot inside of a container, I have no way to automatically renew certificate. Since for that I need to restart nginx on the physical server from inside of a LXC container. For nginx to notice the new certificate.
This issue may manifest itself with FTP servers. (I believe at least some of them allow to chroot user to a directory.) And maybe SFTP ones. And generally with any kind of chroot.
And I see no advantages to using absolute symlinks over relative ones. At least nobody has told me any yet. But I see disadvantages.
Also, do you know anything about this decision everybody's talking about? From history of this repo I see absolute symlinks were used from day one. And more importantly, what was the reason to choosing absolute symlinks?

I don't think running certbot inside a container is necessarily a good idea. It took less than 10 lines outside the container to sort that out for all domains on the server for me. Also allowing easy cert update automation on all domains. You just run certbot against the custom port. Separation of interests.
The below is for HAProxy, but I'm sure you can replicate this for Apache or nginx.
frontend http-in
  bind *:80
  mode http
  acl letsencrypt_control path_beg -i /.well-known/acme-challenge/
  use_backend letsencrypt if letsencrypt_control
backend letsencrypt
  mode http
  server letsencrypt <IP_ADDRESS>:51212


CR-7821

Codecov Report

Merging #159 (41b1ea7) into main (5c8fde0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #159   +/-   ##
=======================================
  Coverage   25.13%   25.13%
=======================================
  Files           1        1
  Lines         187      187
=======================================
  Hits           47       47
  Misses        134      134
  Partials        6        6

Continue to review full report at Codecov.

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

/e2e


Add bar labels to the Bars mark example

Describe your changes
Adding bar labels to the Bars mark example.
Testing performed
Checked that the code ran correctly in the notebook.

I'd also like to add some tests to check everything is rendering correctly. Perhaps we can discuss in the next weekly. Thanks!

Merging, this looks great!


RuntimeError: Placeholder storage has not been allocated on MPS device!

I tried to run the script on my macOS(m2) as down follow:
CUDA_VISIBLE_DEVICES='mps:0' accelerate launch bins/tts/inference.py \
--config "ckpts/tts/valle_libritts/args.json"
--log_level debug
--acoustics_dir ckpts/tts/valle_libritts
--output_dir ckpts/tts/valle_libritts/result
--mode "single"
--text "his is a clip of generated speech with the given text from Amphion Vall-E mode"
--text_prompt "many animals of even complex structure which live parasitically within others are wholly devoid of an alimentary cavity"
--audio_prompt ckpts/tts/valle_libritts/prompt/LJ025-0076.wav
--test_list_file None
but i got the error massages :

2023-12-25 21:44:01 | WARNING | phonemizer | words count mismatch on 100.0% of the lines (1/1)
Traceback (most recent call last):
File "/Users/hehongshu/dev/llm/Amphion/bins/tts/inference.py", line 167, in
main()
File "/Users/hehongshu/dev/llm/Amphion/bins/tts/inference.py", line 163, in main
inferencer.inference()
File "/Users/hehongshu/dev/llm/Amphion/models/tts/base/tts_inferece.py", line 173, in inference
pred_audio = self.inference_for_single_utterance()
File "/Users/hehongshu/dev/llm/Amphion/models/tts/valle/valle_inference.py", line 127, in inference_for_single_utterance
audio = self.inference_one_clip(text, text_prompt, audio_file)
File "/Users/hehongshu/dev/llm/Amphion/models/tts/valle/valle_inference.py", line 109, in inference_one_clip
samples = self.audio_tokenizer.decode([(encoded_frames.transpose(2, 1), None)])
File "/Users/hehongshu/dev/llm/Amphion/utils/tokenizer.py", line 68, in decode
return self.codec.decode(frames)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/encodec/model.py", line 175, in decode
return self._decode_frame(encoded_frames[0])
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/encodec/model.py", line 183, in _decode_frame
emb = self.quantizer.decode(codes)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/encodec/quantization/vq.py", line 112, in decode
quantized = self.vq.decode(codes)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/encodec/quantization/core_vq.py", line 361, in decode
quantized = layer.decode(indices)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/encodec/quantization/core_vq.py", line 288, in decode
quantize = self._codebook.decode(embed_ind)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/encodec/quantization/core_vq.py", line 202, in decode
quantize = self.dequantize(embed_ind)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/encodec/quantization/core_vq.py", line 188, in dequantize
quantize = F.embedding(embed_ind, self.embed)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/torch/nn/functional.py", line 2210, in embedding
return torch.embedding(weight, input, padding_idx, scale_grad_by_freq, sparse)
RuntimeError: Placeholder storage has not been allocated on MPS device!
Traceback (most recent call last):
File "/Users/hehongshu/anaconda3/envs/amphion/bin/accelerate", line 8, in
sys.exit(main())
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/accelerate/commands/accelerate_cli.py", line 47, in main
args.func(args)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/accelerate/commands/launch.py", line 1017, in launch_command
simple_launcher(args)
File "/Users/hehongshu/anaconda3/envs/amphion/lib/python3.9/site-packages/accelerate/commands/launch.py", line 637, in simple_launcher
raise subprocess.CalledProcessError(returncode=process.returncode, cmd=cmd)
subprocess.CalledProcessError: Command '['/Users/hehongshu/anaconda3/envs/amphion/bin/python', 'bins/tts/inference.py', '--config', 'ckpts/tts/valle_libritts/args.json', '--log_level', 'debug', '--acoustics_dir', 'ckpts/tts/valle_libritts', '--output_dir', 'ckpts/tts/valle_libritts/result', '--mode', 'single', '--text', 'his is a clip of generated speech with the given text from Amphion Vall-E mode', '--text_prompt', 'many animals of even complex structure which live parasitically within others are wholly devoid of an alimentary cavity', '--audio_prompt', 'ckpts/tts/valle_libritts/prompt/LJ025-0076.wav', '--test_list_file', 'None']' returned non-zero exit status 1.

I noticed that you are using macOS with MPS, but you are still using CUDA_VISIBLE_DEVICES to assign the device. It might be worth considering using PYTORCH_ENABLE_MPS_FALLBACK instead to assign the MPS device. However, please note that there could be potential compatibility issues since Amphion is primarily developed for the Linux platform with GPU devices.

Hi @MonroeHe , if you have any further questions about training on MPS device, feel free to re-open this issue. We are glad to follow up!


Brackets doesn't seem to match the color scheme

Using the style in VScode. It looks like () and [] have a bright color, not matching the overall color scheme.

Fixed, but please in the future make sure you are creating issues in the right repo
For vscode https://github.com/posterpole/vscode


Time selection for VOD download

Provide a possibility to choose which part of the complete VOD you want to download (needs investigation if it is possible first)

Implemented!


Add pprof profiling support to all binaries.

What is this change?
This adds the ability to expose the pprof profiler for all of the topolvm binaries.
Background
We are seeing a bit of memory growth over time with lvmd, and wanted to run some profiling to see if there's some sort of memory leak, but don't have that ability. This would add that functionality.

Testing:
Tested locally  in minikube
❯ helm upgrade -i -n topolvm-system topolvm ../../charts/topolvm -f manifests/values/local.yaml
❯ kc get pod -n topolvm-system
NAME                                               READY   STATUS    RESTARTS      AGE
topolvm-cert-manager-657b7864b7-hhw2k              1/1     Running   0             9m13s
topolvm-cert-manager-cainjector-57fbb46b78-7k6nq   1/1     Running   0             9m13s
topolvm-cert-manager-webhook-85bff86bcc-zcj7w      1/1     Running   0             9m13s
topolvm-controller-664c66c87c-v46j4                5/5     Running   0             34s
topolvm-lvmd-0-t4qh8                               1/1     Running   0             33s
topolvm-node-58smh                                 3/3     Running   1 (31s ago)   33s

❯ diff manifests/values/base.yaml manifests/values/local.yaml
2,4c2,4
<   repository: topolvm
<   tag: dev
<   pullPolicy: Never
---
>   repository: docker.io/personal/topolvm-with-sidecar
>   tag: devel
>   pullPolicy: Always
11a12,13
>   profiling:
>     port: 6060
46a49,50
>   profiling:
>     port: 6060
49a54,55
>   profiling:
>     port: 6060

Another thing of note. If you use the images from topolvm directly, please note that we strip debugging information: https://github.com/topolvm/topolvm/blob/2096240b0b18dcfb4e4656259c5619176a2b102e/Makefile#L163
It would be cool if we could add pprof when debugging symbols are enabled, but Ill leave it to you if you want to implement that or not

Why do you not choose to use the existing pprof implementation at

I wasn't aware of this implementation in controller-runtime. I will migrate this to use that instead. Thanks for the pointer.

Last but not least, it would be great if you could share your memory observations over time. The leak findings are insanely useful and we will do our best to remediate

I will share more information when I have the details. At this time I don't have a ton to go on, just observation of memory growth over time that seems specific to the lvmd process.

Ok, the current changes use the controller-runtime's pprof integration when available, otherwise it handled shutdown gracefully via context and doesn't leak goroutines.
As for the note/question about stripping debugging information, were you suggesting detecting the debugging symbol's existence at runtime, and only serving the pprof endpoint when the debugging symbols exist? In my testing, even without the debugging symbols the pprof endpoint is rather useful. Let me know if you want some changes in this area. Thanks much for the quick review!

mostly good. I'll approve this after you update values.yaml. Also, these commits can be squashed, can you do that?

Values file updated, and I'm working to squash these commits. :+1:

@jakobmoellerdev It appears the helm readme hadn't been updated with helm-docs. I've run this update and will check back the ci tasks.

Hi @naemono ,

We are seeing a bit of memory growth over time with lvmd, and wanted to run some profiling to see if there's some sort of memory leak, but don't have that ability. This would add that functionality.

FYI, our team also found lvmd memory growth. I don't know if this is the same issue as your report.
The issue we found was that as we repeatedly created and deleted PVs in TopoLVM, the metrics container_memory_usage_bytes{namespace="topolvm-system", container="lvmd"} kept increasing. After investigation, this was not lvmd, but rather an increase in the lvm cache. Therefore, the following metrics were not increasing
container_memory_usage_bytes{namespace="topolvm-system", container="lvmd"} - container_memory_cache{namespace="topolvm-system", container="lvmd"}
Once we've reported this issue to LVM mailing list. However, we don't have enought time to dig into this problem for now.
<EMAIL_ADDRESS>


Properly handle pasting of multiple tags in a tag field in the admin

This tries to properly handle the pasting of multiple tags into a tag field. The pasted string is split by comma and displayed properly as single tags.
The solution comes an issue in the tag-it library: https://github.com/aehlke/tag-it/issues/139#issuecomment-203447998
fixes #5357

Thank you @bruecksen but we should avoid changing the jQuery library/vendor code as it makes updating this fragile.
Instead, it would be better to fix this at the TagController (Stimulus) level if possible.
Also, it's worth noting that we are actively investigating a replacement library and it supports pasting items with commas correctly out of the box.
See https://github.com/wagtail/wagtail/issues/2952 (it's an order issue but has been recently updated).

@lb- thanks for your comment. I thought so that it is not a good idea, then i looked in the commit history of the file and saw lots of changes so I thought why not another one. But you are right it makes things tricky. Do you think I could fix this at the TagController? I don't want to spend to much time on this especially if an replacement is coming soon...

Ok. Thanks for investigating, I didn't realise we'd already patched the vendor JS.
I'll flag this issue in the core team chat, others may have a different opinion. Plus I'm about to be away for a month.


Why use -6.58 as the initialization of bias

https://github.com/s-gupta/visual-concepts/blob/0e223639df399dc973f8c7005ee68c228afc9784/output/v1/mil_finetune.prototxt#L184
Hi Saurabh,
Recently, I am trying to export this code from Caffe to Pytorch. When tuning the model in Fully-Convolutional Network, I found a very interesting trick in the code.
The bias of the classification layer should be set to -6.58, otherwise, the optimization will be misled. For example, If this value is initialized to zero, the model even does not converge. So I want to know why you use this value as initialization and how did you find it.

Did you export this code to pytorch?

Did you export this code to pytorch?

I have exported it to Pytorch. But still, have some troubles. I will release the code later, hope you can help to refine it together.

Did you export this code to pytorch?

@mememimis, I have exported it to Pytorch. But still, have some troubles. I will release the code later, hope you can help to refine it together.

Can you share your pytorch code? Thank you very much


Update documentation for validate_api_call

The validate_api_call method was updated but the documentation was not updated.
In this commit the validate_api_call was changed:
-def validate_api_call(schema, request, response):
+def validate_api_call(schema, raw_request, raw_response):

So the documentation should be updated

Fixed in #45


fix: the annual growth data is compared with the data after growth in…

… the next year.
The annual growth data should be compared with the base of the same year.
But diff() only will make it to compare the data with the next year.
shift(-1) will fix this problem.
below are some tests to show the difference between diff() and diff().shift(-1)
diff() without shift:
abs_diffs:
Time
1997.0       NaN <= not good
1998.0      96.0 <= this should be 1997 growth
1999.0    1402.0
2000.0   -2404.0
rel_diffs numbers:
1997.0         NaN <=
1998.0    0.033743 <=
1999.0    0.330115
2000.0   -1.304395 <=
shift data one row up:
pop_series.diff().shift(-1)
Time
1997.0      96.0 <= this is 1997 growth
1998.0    1402.0 <=
1999.0   -2404.0
2000.0     719.0
2001.0    -788.0
rel_diffs as below:
Time
1997.0    0.034922 <=
1998.0    0.492794 <=
1999.0   -0.566047
2000.0    0.390125 <=

Good idea. I've made this change in the upstream file and propagated it. Thank you!


next export broken due to EEXIST: file already exists

Bug report
Describe the bug
I updated my app from Next 8 to Next 9.
Unfortunately now when I try next export, it doesn't work any more. It exits with the following output:
> using build directory: /Users/mmiszy/htdocs/my-app/.next
  copying "static" directory
  copying "static build" directory
  launching 7 threads with concurrency of 10 per thread
  copying "public" directory
{ [Error: EEXIST: file already exists, copyfile '/Users/mmiszy/htdocs/my-app/public/static/style.css' -> '/Users/mmiszy/htdocs/my-app/public/static/style.css']
  errno: -17,
  code: 'EEXIST',
  syscall: 'copyfile',
  path:
   '/Users/mmiszy/htdocs/my-app/public/static/style.css',
  dest:
   '/Users/mmiszy/htdocs/my-app/public/static/style.css' }

or:
> using build directory: /Users/mmiszy/htdocs/my-app/.next
  copying "static" directory
  copying "static build" directory
  launching 7 threads with concurrency of 10 per thread
  copying "public" directory
{ [Error: EEXIST: file already exists, copyfile '/Users/mmiszy/htdocs/my-app/public/service-worker.js' -> '/Users/mmiszy/htdocs/my-app/public/service-worker.js']
  errno: -17,
  code: 'EEXIST',
  syscall: 'copyfile',
  path:
   '/Users/mmiszy/htdocs/my-app/public/service-worker.js',
  dest:
   '/Users/mmiszy/htdocs/my-app/public/service-worker.js' }

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
https://github.com/mmiszy/next-bug-example

next build && next export -o public

System information

OS: MacOS
Version of Next.js: Next.js v9.0.1

Do you have a repo in which I can reproduce this issue?

https://github.com/mmiszy/next-bug-example

Hey @mmiszy public folder is reserved for the public directory, it's behind the feature flag. We should throw an error when building to public folder. Sorry about that.

Is that something new introduced in Next.js 9? That would explain it.

Yes, but it's behind a feature flag, so it should work without it. I will make PR to fix this bug.


Project Proposal: React Native kit for EUDI Wallet reference implementation

Hi there,
The DSR team is happy to apply our experience in React Native and SSI Wallets to EUDI Wallet initiative and the OpenWallet Foundation. We'd like to propose React Native kit for EUDI Wallet reference implementation.
The kit will allow building cross-platform Mobile Wallet applications compliant with eIDAS Regulation and EUDI ARF and based on the reference implementations from EUDI.

Thank you @ashcherbakov for the proposal. I have added it to the agenda for April 17th. Will this work for you and the team?

@tkuhrt Thank you. Yes, April 17th works for us.

Approved at the April 17, 2024 TAC meeting.