a lot of expired shares and as a result of rejections
To be clear, it's not a bug in the miner, it's just an unnecessary warning, the workaround is 100% safe and works. Basically, it means we don't refresh the nonce range we test since the pool job we just received is 100% identical to the previous one, we continue hashing from the last nonce used before the new job arrived. It's more that it's occuring much more often in the ERGO mining world, pools don't seem to refresh the job from the daemon when they send out a "new" job for the same network block height. The warning was inherited from other mining protocols where this doesn't really happen naturally but should be removed for ERGO for users since it adds zero value, only confusion.