There is one more instance of pango_printf in render_text which needs to
be fixed. Could you fix it and send a new patch?

Also, patches can be sent with git send-email to avoid formatting
issues. That method is preferred for sending patches to this list. See
https://git-send-email.io for a helpful guide to using git send-email.

On Mon May 29, 2023 at 2:46 PM EDT, Nikita Ivanov wrote:
> I've sent the response a few days ago but I think it was a wrong addres.
> Here is properly formatted patch.

These sentences above the --- become part of the commit message. If you
want to leave a note like this which should not be part of the commit
message, you should write them below the ---.

Hi, thanks for the patch! It looks like some of the lines got wrapped by
mistake? Could you fix and resend it?

On Wed May 3, 2023 at 9:00 AM EDT, Edd Salkield wrote:
> Currently I use kiln to compress my source images for faster downloading
> on the web, in `config.toml` as follows:
>
> ```
> [[tasks]]
> input = [".jpg", ".jpeg", ".png"]
> output = ".jpg"
> preprocess.jpg = "magick /dev/stdin -strip -interlace Plane
> -gaussian-blur 0.05 -quality 85% /dev/stdout"
> output_dir = "public"
> ugly_urls = true
> ```
>

On Wed May 3, 2023 at 9:01 AM EDT, Edd Salkield wrote:
> I was dwelling on the design of kiln, and in particular how feeds are 
> handled, in this blog post[1]. 
> It seems to me like feeds are currently a special case of index 
> pages, and I'm wondering if they can be unified. 
>
> In particular, feeds are given a set of feed variables: `.Title`, 
> `.Path`, `.URL`, and `.Pages`. However, these variables are a subset of 
> the page variables. 
>
> Are there any other aspects of rendering a feed that couldn't be done 
> in an index page?
>
> [1]: https://edd.salkield.uk/blog/2023/02/07/in_praise_of_kiln.html

Looks like your build tasks are being received by lists.sr.ht's celery
worker. You should configure separate redis databases for builds.sr.ht
and lists.sr.ht.

I realize now that this is not supported by POSIX ERE. But it is
supported by other tools like awk. You may want to revert this.

---
 gitsrht-update-hook/post-update.go |  25 +++----
 gitsrht-update-hook/submitter.go   | 110 ++++++++++++++---------------
 2 files changed, 68 insertions(+), 67 deletions(-)

diff --git a/gitsrht-update-hook/post-update.go b/gitsrht-update-hook/post-update.go
index ef2e992..676df81 100644
--- a/gitsrht-update-hook/post-update.go
+++ b/gitsrht-update-hook/post-update.go
@@ -176,7 +176,7 @@ func parseUpdatables() (*string, *string) {
 }
 
 func postUpdate() {
-	var context PushContext
[message trimmed]

---
 hubsrht/builds.py   |  3 ++-
 hubsrht/services.py | 40 +++++++++++++++++++++++++++++++++-------
 2 files changed, 35 insertions(+), 8 deletions(-)

diff --git a/hubsrht/builds.py b/hubsrht/builds.py
index 604f8a4..88f900d 100644
--- a/hubsrht/builds.py
+++ b/hubsrht/builds.py
@@ -107,7 +107,8 @@ git am -3 /tmp/{payload["id"]}.patch"""
         }))
 
         b = builds.submit_build(project.owner, manifest, build_note,
-            tags=[repo.name, "patches", key], execute=False, valid=valid)
[message trimmed]

On Tue Apr 11, 2023 at 9:56 AM EDT, Drew DeVault wrote:
> More background?

This is something that you had wanted to do as part of the move away
from alembic. Is this no longer wanted?

On Tue Apr 11, 2023 at 8:49 AM EDT, Drew DeVault wrote:
> When testing this by using the UI at builds.sr.ht/submit I get this
> exception:
>
> srht.graphql.client.GraphQLError: {'errors': [{'message': 'pq: null value in column "visibility" of relation "job" violates not-null constraint', 'path': ['submit']}], 'data': None}

Sounds like the API is running an outdated version?

Anyways, I sent a v2 to fix an unrelated problem.