Tim Janik

I am seeing the same issue, with `act version 0.2.63-9-g935e4c3`. The asset corruption seems to be size dependent: Things work fine at 4M: ```yml - run: dd if=/dev/urandom bs=1024 count=4096...

> Find the commit that breaks it Today, I also ran into Qwen2 random character generations. I think what I am seeing matches this bug description. Whether it is triggered...

> That commit was made after this issue was opened, so I don't see how that can be the issue. As I wrote above, the behaviour is prompt related. I'm...

Ok, one more observation. I am still running d62e4aaa02540c89be8b59426340b909d02bbc9e like this: `/ml/llama.cpp/llama-server -fa -nkvo --host 0.0.0.0 --port 8080 -np 4 -m /ml/models/Smaug-Qwen2-72B-Instruct.Q4_K_S.gguf -c 32768 -ngl 43` I have a number...

> If I recall correctly, this model had issues with precision in the attention. Can you test if this change fixes it? > > ```diff > diff --git a/src/llama.cpp b/src/llama.cpp...

I need the expansion for the contributor list, I don't think there is a commit available when you are looping over them right? ``` {% for contributor in github.contributors %}...

> Ah I see. In that case it is currently not possible to use the author or committer information. > > Would making `commit.author`/`commit.committer` a part of the `github` object...

> Yeah, I'm thinking of making the following use case possible: > > ``` > {% for contributor in github.contributors %} > * {{ contributor.author }} (@{{ contributor.username }}) >...

> I've considered adjusting the code for reconciling concurrent operations to look for concurrent snapshot operations and keeping only the newest one. Disclaimer, I don't know the rust code base...

> IME "Concurrent checkout" is quite easy to trigger even without watchman. I keep one terminal window permanently running `watch jj log` (like [@martinvonz](https://github.com/martinvonz) does in one of his demos)....