Steven Allen
Steven Allen
Ah... I found the issue. The FVM is trying to return an illegal argument error in this case: https://github.com/filecoin-project/ref-fvm/blob/a0f85fa8889a2e9e2393aa87c0f8b003919557fd/fvm/src/kernel/default.rs#L808-L809 But `ChainEpoch` is an `i64`, not a `u64`. So `lookback` is...
> though IIRC one of the other popular distro (centos or fedora, I can't remember) still on 1.84 Ah, that's good to know. I'll see if I can downgrade to...
It's Ubuntu plucky. Which is unfortunately rules out 2024 edition unless I wait until October (although it might take that long anyways if I try to tackle the remaining TODOs).
> What if j/k were bound to move between events here? https://github.com/emacs-evil/evil-collection/pull/734 🙅 That would break keyboard navigation/selection. IMO, a better approach would be: 1. Mark it as [intangible](https://www.gnu.org/software/emacs/manual/html_node/elisp/Special-Properties.html#index-cursor_002dintangible-_0028text-property_0029). 2....
Make it a per-topic option.
Specifically, repurpose the seqno?
> I think this would break some systems that rely on it. Rely on it being sequential?
But yeah, making this a per-topic option would go a long way.
> Rather monotonically increasing. unixnanos? unixnanos with a counter in case we try to go backwards?
Well, specifically I was thinking about having a guaranteed monotonically increasing clock. I.e.: 1. Get unix nanos. 2. Look at the last sequence number. 3. If less than or equal...