-
Open source package ecosystem expert and functional programming enthusiast
-
Joined on
2021年06月03日
Are uploaded images being saved correctly when this happens, or just the item text?
Excellent detective work, @Profpatsch! #1010 now fixes that issue on my instance, and Mastodon users can now follow and receive new listings from it.
Plopped a print statement in signatures.py just to be sure that A: I was building the container from source correctly and B: that your patch actually produces the expected result:
I built a container image from the branch and tested it again, but the error persists. I made sure to delete the previous container image locally and restarted the container to be certain that my...
/authorize_interaction
I agree that this would be a useful feature. I'd have thought that this could work well with a special "everything on this instance" user, which automatically publishes an Announce activity when...
This issue could be related to #992, I think.
These additional lines of log output are potentially interesting, they appear just before the crash occurs:
a) I clicked follow on grindhold@para1.k.rainbow-lollipop.de from @seabass@hachyderm.io within a few minutes of 16:30 UTC on 2026年05月27日. The follow request is shown as waiting for approval...
a) and b) - I was asking a friend who has a Mastodon account for help with testing it. I'll create an account on a Mastodon instance myself and get back to you on that.
Alternatively, all the logic to determine the correct image name and tag could be moved before the image is build by Nix. Then, that could be passed to Nix itself so that the image is built with...
A bit of a brute-force solution, but... the container images shouldn't be kept around in the runners after they're pushed to the registry anyway. So again, if this is the problem, we could just...
Perhaps the Forgejo Actions runner keep old images around, and this command is selecting the wrong one to be tagged and pushed to the registry?
@lars-li No, the version doesn't appear in the logs at all; I just looked at the contents of the flohmarkt/constants.py file inside each container image to determine the version it contains.
Related to #1001
I tried building a container image locally from the Git tag 0.18.0, using podman build. I used the Dockerfile in the flohmarkt repository, which is based on docker.io/library/python:3.12,...