I can report the problem is still there. A duplicate share is sent after a devfee session - then pool bans the IP. I can't say for certain the problem is linked to the devfeee session, because this time the duplicate share was not the first share following the devfee session, but there were no duplicates before the devfee session - log below. I have another miner running 0.23 which had 45+ successful shares and no devfee session yet.
This pool is run by an OP I know who disabled IP banning for duplicates, but all other pools are banning the IP if a duplicate is sent (on suspicion of stealing hashrate) hence CD is still not reliable to use (at least on this algo).
A duplicate should never be sent by the miner during the same session so this must be a bug.
$ ./CryptoDredge -a cnturtle -o stratum+tcp:// -u -p --no-nvml
...
[13:51:45] INFO - CryptoDredge 0.23.0 NVIDIA GPU Miner
[13:51:45] INFO - Built with CUDA Toolkit 10.0
[13:51:45] INFO - DevFee is 1% (2% for MTP)
[13:51:45] INFO - Start built-in watchdog
[13:51:46] WARN - NVML is disabled
...
[13:51:46] INFO - Selected algo: cnturtle
...
[14:03:08] INFO - Start devfee session
[14:03:43] INFO - Start user session
[14:04:08] INFO - 17/0 Accepted : diff=2845616 : 70.19KH/s
[14:04:30] INFO - 18/0 Accepted : diff=6288420 : 70.19KH/s
[14:04:31] INFO - 19/0 Accepted : diff=8576415 : 70.19KH/s
[14:05:19] INFO - 19/1 Rejected : diff=8553147, reason: Duplicate share2
Linked issues:
https://github.com/technobyl/CryptoDredge/issues/15https://github.com/technobyl/CryptoDredge/issues/8