2 Jan
2021
2 Jan
'21
10:36 a.m.
I tried searching the hyperkitty archives (the ARM list) for the results
of the ARM survey from last year, but if I search for e.g. "survey", I
get exactly one hit (six months old), rather than Doug Demaio's posting
from December titled "ARM survery results meeting" ??
--
Per Jessen, Zürich (1.2°C)
Member, openSUSE Heroes
2 Jan
2 Jan
10:38 a.m.
Per Jessen wrote:
I tried searching the hyperkitty archives (the ARM
list) for the
results of the ARM survey from last year, but if I search for e.g.
"survey", I get exactly one hit (six months old), rather than Doug
Demaio's posting from December titled "ARM survery results meeting" ??
Searching "heic" or "HEIC" on users.lists gives me zero hits, despite
the topic having been discussed only in the last two days.
--
Per Jessen, Zürich (1.2°C)
Member, openSUSE Heroes
10:40 a.m.
Am Sa, 2. Jan, 2021 um 10:36 A. M. schrieb Per Jessen
<per(a)opensuse.org>rg>:
I tried searching the hyperkitty archives (the ARM
list) for the
results
of the ARM survey from last year, but if I search for e.g. "survey", I
get exactly one hit (six months old), rather than Doug Demaio's
posting
from December titled "ARM survery results meeting" ??
There are some issues with updating the index, it takes up around 80G
and refreshing it takes
a few days. We probably need a cronjob that runs it weekly. You can try
it yourself if you `su mailman` and in `/var/lib/mailman_webui` run
`python3 manage.py update_index` iirc.
It technically should be able to run more often, but I didn't look into
how that would be done yet.
LCP [Stasiek]
https://lcp.world
2:07 p.m.
Stasiek Michalski wrote:
Am Sa, 2. Jan, 2021 um 10:36 A. M. schrieb Per Jessen
<per(a)opensuse.org>rg>:
According to "python3 manage.py runjobs -l", it is already being run
hourly - however, the hourly runjob produces an error:
/usr/lib/python3.6/site-packages/readme_renderer/markdown.py:38:
UserWarning: Markdown renderers are not available.
Install 'readme_render[md]' to enable Markdown rendering.
warnings.warn(_EXTRA_WARNING)
Error: None of the config files exist.
I'm just now running it manually - indexing 3'111'674 emails.
--
Per Jessen, Zürich (1.6°C)
Member, openSUSE Heroes
I tried searching the hyperkitty archives (the
ARM list) for the
results of the ARM survey from last year, but if I search for
e.g. "survey", I get exactly one hit (six months old), rather than
Doug Demaio's posting from December titled "ARM survery results
meeting" ??
There are some issues with updating the index, it takes up around 80G
and refreshing it takes a few days. We probably need a cronjob that
runs it weekly. You can try it yourself if you `su mailman` and in
`/var/lib/mailman_webui`
run `python3 manage.py update_index` iirc.
It technically should be able to run more often, but I didn't look
into how that would be done yet.
8:06 p.m.
Per Jessen wrote:
Stasiek Michalski wrote:
> Am Sa, 2. Jan, 2021 um 10:36 A. M. schrieb Per Jessen
> <per(a)opensuse.org>rg>:
>> I tried searching the hyperkitty archives (the ARM list) for the
>> results of the ARM survey from last year, but if I search for
>> e.g. "survey", I get exactly one hit (six months old), rather than
>> Doug Demaio's posting from December titled "ARM survery results
>> meeting" ??
>
> There are some issues with updating the index, it takes up around 80G
> and refreshing it takes a few days. We probably need a cronjob that
> runs it weekly. You can try it yourself if you `su mailman` and in
> `/var/lib/mailman_webui`
> run `python3 manage.py update_index` iirc.
> It technically should be able to run more often, but I didn't look
> into how that would be done yet.
Okay, that is horrendously slow. Interestingly xapian is being used, I
use that myself for indexing mails, for about ten years. I use it from
C, it is very fast.
Was "update_index" ever completed, if only once? the idea that it
should be run once an hour seems very ambitious :-)
--
Per Jessen, Zürich (0.2°C)
Member, openSUSE Heroes
10:56 p.m.
Am Sa, 2. Jan, 2021 um 8:06 P. M. schrieb Per Jessen <per(a)opensuse.org>rg>:
Per Jessen wrote:
I did run it twice before, but I'm not sure it finished
LCP [Stasiek]
https://lcp.world
Stasiek Michalski wrote:
>
> There are some issues with updating the index, it takes up around
> 80G
> and refreshing it takes a few days. We probably need a cronjob that
> runs it weekly. You can try it yourself if you `su mailman` and in
> `/var/lib/mailman_webui`
> run `python3 manage.py update_index` iirc.
> It technically should be able to run more often, but I didn't look
> into how that would be done yet.
Okay, that is horrendously slow. Interestingly xapian is being used,
I
use that myself for indexing mails, for about ten years. I use it
from
C, it is very fast.
Was "update_index" ever completed, if only once? the idea that it
should be run once an hour seems very ambitious :-)
3 Jan
3 Jan
5:19 p.m.
Stasiek Michalski wrote:
Am Sa, 2. Jan, 2021 um 8:06 P. M. schrieb Per Jessen
<per(a)opensuse.org>rg>:
My attempt ran for about 26 hours, then got killed - oom. Need more
memory.
--
Per Jessen, Zürich (0.7°C)
Member, openSUSE Heroes
Per Jessen wrote:
I did run it twice before, but I'm not sure it finished Stasiek Michalski wrote:
>
> There are some issues with updating the index, it takes up around
> 80G
> and refreshing it takes a few days. We probably need a cronjob
> that runs it weekly. You can try it yourself if you `su mailman`
> and in `/var/lib/mailman_webui`
> run `python3 manage.py update_index` iirc.
> It technically should be able to run more often, but I didn't look
> into how that would be done yet.
Okay, that is horrendously slow. Interestingly xapian is being used,
I use that myself for indexing mails, for about ten years. I use it
from C, it is very fast.
Was "update_index" ever completed, if only once? the idea that it
should be run once an hour seems very ambitious :-)
54
days inactive
55
days old
6 comments
2 participants
participants (2)
-
Per Jessen -
Stasiek Michalski