Rongcui Dong
Rongcui Dong
But what about values that don't implement `Eq`? Implementation aside, would it still be a valid range map?
> macOS requires pumping the events after destroying a window for the OS to process the change and remove it from the desktop. This has been the case going back...
This also fails on me with MacPorts: ``` ... ∗ installed coq-paramcoq.1.1.3+coq8.18 ∗ installed coq-itauto.8.18.0 ∗ installed coq-gappa.1.5.4 ∗ installed coq-mathcomp-finmap.1.5.2 ∗ installed coq-coquelicot.3.4.0 ∗ installed coq-simple-io.1.8.0 ∗ installed coq-reglang.1.1.3...
It's a pretty new repo so definitely not many files. It has plenty of blobs, however. Can you ensure that the previous command is finished before running the next one?...
Ok, maybe this is not it
I still get it occasionally: ```console 2025-01-13 20:28:00.465 [info] fossil branch current: 23ms 2025-01-13 20:28:01.414 [info] fossil sync: still running // periodic sync 2025-01-13 20:28:03.955 [info] fossil sync: 5042ms //...
Also, whenever this happens, the extension basically stops working. No buttons in the VCS tab will work, and it requires a restart. Perhaps there can be a way to reset...
There are actually a few reasons where `fossil` commands take that long in my case. I have set up a fossil server on one of my computers, which runs on...
The following log is from a fast computer with local SSD repo only: ```console 2025-01-22 09:58:11.527 [info] fossil branch current: 27ms 2025-01-22 09:58:16.557 [info] fossil branch current: 21ms 2025-01-22 09:58:16.561...
I also encounter the bug with Sync disabled.