> This issue is very difficult to reproduce because of its racy nature. As far as I understand, one of the condition to trigger this issue is the state of the server side where I don't have a control of. I tried to test it in an automated environment and launched an insurance continuously for 3 days. However during that period, the issue wasn't triggered neither with the old nor new version of snapd.
> Run snapd 2.71 in the environment where the reported issue was detected and ensure no more occurrences are detected. As above, there is no clear conclusion from the testing but at least the condition is met. So I suppose we can say the verification is done. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2104066 Title: More details should be provided than v2/snaps/refresh: context canceled To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2104066/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
