Wednesday, February 28, 2018
grimoire@muc.metronome.im
February
Mon Tue Wed Thu Fri Sat Sun
      1
2
3 4
5 6
7
8
9
10
11
12 13
14 15
16
17
18
19 20 21 22
23
24
25
26
27
28
       
             
Metronome IM "cook" book room | Support and Dev talk about the Metronome XMPP server.

Latest stable version build is: 4.0.3

For more information you can visit: https://metronome.im

Room logs can be found here: https://muc.metronome.im/logs/grimoire/

* Links *
<==========================================================>
- Building & Installation:
https://metronome.im/building
- Documentation:
https://metronome.im/documentation
- Issues Tracker:
https://github.com/maranda/metronome/issues
<==========================================================>

[02:40:19] <Echo1> maranda committed --
metronome.release, net.http{.server}: bump up to pre-release.
-> https://github.com/maranda/metronome/commit/7345a760e50a0e027bbb19ae98ea75ba1da1625f
[02:40:20] <Echo1> maranda committed --
mod_pep, pep_aux.lib: properly fix issue #287.
-> https://github.com/maranda/metronome/commit/7026a1fc718bc2176dcc02e2c2d2e9741cfabc00
[02:40:21] <Echo1> maranda committed --
mod_dialback: handle loop cases when sending errors.
-> https://github.com/maranda/metronome/commit/3b48005835214f8de5752d502355c0ae25060738
[03:12:51] <Echo1> maranda committed --
mod_pep: hook on above mod_stanza_optimizations.
-> https://github.com/maranda/metronome/commit/0d4f66cae8e6650faee7db82c8ad5c9b21261599
[03:12:52] <Echo1> maranda committed --
mod_pep: remove function closure, won't be reused.
-> https://github.com/maranda/metronome/commit/723010672b68bad113f655fabb1b8c51d55b62c9
[07:25:23] <Maranda> jonasw, I fixed the PEP code btw now it should work as it actually should.
[07:25:56] <Maranda> 😖 😑 😪
[07:28:44] <jonasw> I’m at work today, so I’ll probably not going to have time to test this
[07:30:42] <Maranda> jonasw, no worries
[07:42:51] <Echo1> maranda committed --
mod_pep: remove unused import.
-> https://github.com/maranda/metronome/commit/4c767cbfc345917338296508dcc31f60e6fdf52b
[13:11:48] <Maranda> I never thought that activating pep services on demand caused so many corner cases
[13:12:02] <Maranda> And I need to handle 'em all
[13:12:10] <Maranda> 😐
[18:34:51] <jonasw> Maranda, congrats, the PEP tests run with current master :)
[18:35:59] <Maranda> jonasw, yay?
[18:37:08] <Maranda> jonasw, I just had to stay awake until 4:30am "until it fixed itself" 😧 😧
[18:37:18] <Maranda> 🤣 🤣
[18:37:55] <jonasw> :D
[18:38:09] <jonasw> Maranda, now it appears that the MUC component wouldn’t allow me to create rooms
[18:38:14] <jonasw> maybe that’s also due to mod_auth_anon?
[18:38:19] <jonasw> I’ve set restrict_room_creation = false on the MUC component
[18:38:44] <Maranda> Yes it's because of it, sec
[18:43:08] <Maranda> jonasw, hmm that's not toggable let me rectify that
[18:43:35] <jonasw> btw, why did you fork instead of contribute?
[18:44:35] <Maranda> various reasons, including the usual "I disagree" ones.
[18:45:29] <jonasw> "I disagree"?
[18:52:14] <Maranda> Yes disagreement with the Project path/progression, disagreement between contributors / developer the usual things.
[18:54:05] <jonasw> I wonder what type of disagreements those were
[18:57:51] <Echo1> maranda committed --
mod_muc: add option to allow room creation by anon sessions.
-> https://github.com/maranda/metronome/commit/6918421e1c07df05b3d9ea84a829c1d5b891e949
[18:59:59] <Maranda> jonasw, I'm not sure it's any important anymore, it was before 0.9 release anyways, just make a quick count of how many years ago it was :P
[19:03:34] <jonasw> Maranda, https://github.com/maranda/metronome/issues/289
[19:04:21] <Maranda> jonasw, have a log by any chance?
[19:04:24] <jonasw> ŝure
[19:04:49] <jonasw> it’s a bit convoluted since it’s MUC: https://paste.debian.net/hidden/06d4f628/
[19:05:18] <jonasw> but that’s the last failing test \o/
[19:07:28] <Maranda> jonasw, hm who should be the *author of the empty subject* though?
[19:08:52] *Maranda interesting the xep doesn't cover that bit.
[19:10:24] <Maranda> (on room creation that is)
[19:10:41] <Maranda> I guess I'll make it the room creator.
[19:10:46] <Maranda> brb
[19:11:34] <Maranda> or more likely the room jid.
[19:12:16] <jonasw> good question; maybe look at what the prosody patch does
[19:15:18] <jonasw> Maranda, I’ll now add metronome to the travis-ci suite for aioxmpp; I’ll set it to "allow to fail" for now, because I only put released versions into "must not fail" mode.
[19:15:33] <Maranda> jonasw, no need I think, I actually do that if there isn't a subject author anyways
[19:15:36] <jonasw> (and 3.8 doesn’t include some of the patches you recently made, AFAICS)
[19:15:45] <Maranda> I just removed the ifs
[19:15:56] <Maranda> jonasw, I'll move the tag now :P
[19:16:03] <jonasw> MOVE THE TAG?
[19:16:06] <jonasw> are you insane? :-O
[19:16:12] <jonasw> isn’t that like the one thing one must never do in git?
[19:16:26] <Maranda> jonasw, really? hmm not really it's not hg
[19:16:28] <jonasw> even worse than rebasing published branches? :-O
[19:17:05] <jonasw> cf. man git-tag:
But if you have pushed things out (or others could just read your
repository directly), then others will have already seen the old tag.
In that case you can do one of two things:

1. The sane thing. Just admit you screwed up, and use a different
name. Others have already seen one tag-name, and if you keep the
same name, you may be in the situation that two people both have
"version X", but they actually have different "X"'s. So just call
it "X.1" and be done with it.

2. The insane thing. You really want to call the new version "X" too,
even though others have already seen the old one. So just use git
tag -f again, as if you hadn’t already published the old one.

However, Git does not (and it should not) change tags behind users
back. So if somebody already got the old tag, doing a git pull on your
tree shouldn’t just make them overwrite the old one.
[19:17:09] <Maranda> github just let you do that period, delete release/delete tag and move doesn't have any effect as well by the looks
[19:17:32] <jonasw> make a .1
[19:17:43] <Maranda> hmm
[19:17:51] <Maranda> lol I always done that
[19:18:01] <jonasw> you’re abusing tags as branches
[19:18:03] <Maranda> didn't know it was a bad thing
[19:18:16] <jonasw> I’d suggest to make branches for minor releases and apply patches on top of those as needed
[19:18:21] <jonasw> tag patch releases in those branches
[19:18:26] <jonasw> that’s what I do anyways
[19:18:26] <Maranda> I just use what the github interface gives me for releases
[19:18:42] <Maranda> I'm terribly bad at repository management
[19:19:48] <jonasw> https://travis-ci.org/horazont/aioxmpp/builds/347422904 \o/
[19:21:25] <Maranda> 🤸‍♂ 🤸‍♂
[19:22:36] <Maranda> I need to see if lua5.2 stuff is doable before 3.8 or if there's need at all.
[19:22:41] <Maranda> But not today XD
[19:25:10] <jonasw> merged
[19:25:52] <Maranda> The other is some ominous segfault that happens if I call hostmanager.deactivate() on a busy host. I think I solved that but I'm not sure.
[19:26:59] <Maranda> and \o/
[19:27:51] <Echo1> maranda committed --
muc.lib: send empty subject at end of history even if not set. (Fixes…
-> https://github.com/maranda/metronome/commit/98cfa7663556ee9b1481a4db0da5cc8c8129d8f8
[19:29:40] <Maranda> jonasw, and ok thanks btw :P
[19:30:09] <jonasw> you’re welcome
[19:30:27] <jonasw> it’s nice to know that ones library is compatible to servers :)
[19:33:26] <Maranda> and... the other way around :P
[20:21:14] <Maranda> @version swift.im
[20:21:18] <Echo1> Maranda: swift.im is running Isode M-Link version 16.3v8-1 on an unknown platform
[20:21:32] <Maranda> @version jabber.org
[20:21:32] <Echo1> Maranda: jabber.org is running Isode M-Link version 16.3v13-1 on an unknown platform