~tardypad

https://tardypad.me

~tardypad/wee-most-discuss

Last active 4 months ago

~tardypad/wee-most-devel

Last active 4 months ago

~tardypad/wee-most-announce

Last active 4 months ago
View more

Recent activity

Re: New fork 4 months ago

From Damien Tardy-Panis to ~reedwade/wee-matter-devel

> I fixed ton of things recently. Specially about reliability when
> loosing connection. The re-hydratation process should now be bullet
> proof.

Yeah, I saw the few new commits. Thanks, I'll cherry-pick some if I can
especially the ones about the reliability on lost connections.

> There is ton of missing feature, especially when you administrate the
> instance. In my opinion, the user scope looks good enough (or maybe I
> just dont use some mattermost features).

Oh the user scope is definitely good enough. But I've been used to
wee-slack in my previous job and I'd like to have a similar user
experience with most of its bells and whistles.

Python Mattermost driver 5 months ago

From Damien Tardy-Panis to ~reedwade/wee-matter-devel

Hey

While checking out the Mattermost API I saw mentioned a community based
Python Mattermost driver [1]

I was wondering if there was any reason not to have used it for the
plugin as it seems at first glance that it would make the development
easier and faster.

[1] https://github.com/Vaelor/python-mattermost-driver

--
Damien Tardy-Panis

Re: Single file plugin and forks differences 5 months ago

From Damien Tardy-Panis to ~reedwade/wee-matter-devel

> Honestly I'm not seing the point on being alongside all the other
> weechat scripts.

Previously I was locally setting up the plugins I use by fetching a
single file for each of them. It was simple because "all" plugins in the
weechat ecosystem follow this pattern. But now I've changed my setup to
use a package for each plugin. So this single file plugin is now low
priority for me personally.

> I'm not interested in lazy loading buffers. It would be harder to
> handle things like notifications or to works correctly with other
> addons. Matching the IRC backend behavior looks easier and more
> reliable to me.

Single file plugin and forks differences 6 months ago

From Damien Tardy-Panis to ~reedwade/wee-matter-devel

Hi,

I wanted to contribute a few things to this plugin.

Most notably I would like to have the plugin as a single Python file so
that it can be added alongside all the other Weechat scripts [1] making
it easier for everybody to discover, install and manage it.

I understand that developing it as a single file is not really ideal but
in the end this is what is expected on the Weechat ecosystem side.

My preferred option would be to keep it multiple files as it is in the
repo and see if we can export it as a single file for the Weechat script
purpose. But otherwise managing it as a single file should not be too

Re: [pages.sr.ht] upload fails for tarball with many files 8 months ago

From Damien Tardy-Panis to ~sircmpwn/public-inbox

> We have to unpack it in the middle and forward each file to minio, one
> at a time. S3 doesn't have a bulk upload API.

Ah ok, thanks for the explanation. That's not a real problem to me as
this was anyway just a temporary hosting solution until I can self host
it myself.

Re: [pages.sr.ht] upload fails for tarball with many files 8 months ago

From Damien Tardy-Panis to ~sircmpwn/public-inbox

> Does it take a while to complete the request? It's limited to 90
> seconds, and I am loathe to increase this limit.

When trying to upload with `curl -vvv`, I get the message "We are
completely uploaded and fine" after a second, then it hangs before
displaying the error 90 seconds later indeed.

I wonder what is taking so long though, the unpacking is quasi instant
on my machine. Is there a lot of further processing on the files on the
server?

[pages.sr.ht] upload fails for tarball with many files 8 months ago

From Damien Tardy-Panis to ~sircmpwn/public-inbox

Hi

I'm encountering an error when trying to upload a tarball containing
many files to pages.sr.ht. The curl command is returning a 400 error
with the message "context deadline exceeded".

Sometimes a longer text is available as follow for example:
Post
"https://patchouli.sr.ht/pages.sr.ht/sites/jargon.tardypad.me/temp.9f021ee79d2f7055e37bee6790186df1/B/buried-treasure.gmi?uploadId=df0ba360-357d-46a9-9a15-fb650915732c":
context deadline exceeded%

You can also see the failure in the last build
https://builds.sr.ht/~tardypad/job/461040

[PATCH scdoc 3/3] Fix parsing of line breaks followed by underlined text 1 year, 6 months ago

From Damien Tardy-Panis to ~sircmpwn/public-inbox

---
 src/main.c       | 11 +++++++----
 test/line-breaks |  9 +++++++++
 2 files changed, 16 insertions(+), 4 deletions(-)

diff --git a/src/main.c b/src/main.c
index 08bf384..7bb6c42 100644
--- a/src/main.c
+++ b/src/main.c
@@ -176,19 +176,19 @@ static void parse_format(struct parser *p, enum formatting fmt) {
	p->flags ^= fmt;
}

static void parse_linebreak(struct parser *p) {
[message trimmed]

[PATCH scdoc 2/3] Fix parsing of line breaks without newline 1 year, 6 months ago

From Damien Tardy-Panis to ~sircmpwn/public-inbox

---
 src/main.c       | 2 +-
 test/line-breaks | 8 ++++++++
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/src/main.c b/src/main.c
index 603c91e..08bf384 100644
--- a/src/main.c
+++ b/src/main.c
@@ -186,8 +186,8 @@ static void parse_linebreak(struct parser *p) {
	uint32_t lf = parser_getch(p);
	if (lf != '\n') {
		fprintf(p->output, "+");
		parser_pushch(p, lf);
[message trimmed]

[PATCH scdoc 1/3] Add basic working tests for line breaks parsing 1 year, 6 months ago

From Damien Tardy-Panis to ~sircmpwn/public-inbox

---
 test/line-breaks | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100755 test/line-breaks

diff --git a/test/line-breaks b/test/line-breaks
new file mode 100755
index 0000000..c6c2fc4
--- /dev/null
+++ b/test/line-breaks
@@ -0,0 +1,29 @@
#!/bin/sh
. test/lib.sh

[message trimmed]