00:08:05 It seems the prefs "mailnews.database.summary.dontPreserveOn{Copy,Move}" should be completed by adding "offlineMsgSize". 00:09:18 Otherwise some mess can be happen, as in: http://logbot.buc.me/seamonkey/20210704#c1815 00:13:12 When you move a mail from a local folder (ie. Archives) to imap Inbox, the size of the mail is increased (by 100 bytes in my case), probably because an additional empty "X-Mozilla-Keys:" header is added (why?). But the "offlineMsgSize" still has the old value. In some cases it confuses SM mailer. 00:14:44 Probably TB affected as well... 00:18:45 buc wonder if it is Bug 1430480 00:23:26 Nope, it is not attachment related. 00:24:38 buc you sure? see duplicate Bug 680004 00:28:12 Nope, there are no any attachments in my tests at all. 00:30:23 buc let my try anyway. Looking at the patch it seems to be a general fix not just for attachments. 00:34:07 The issue is not good reproducible. Fortunately I caught a reproducible case in my current environment and found the reason. 00:34:13 ok does not look related at second glance 00:35:34 Bummer that jorgk is no longer doing TB development. 00:37:42 When the mail is movied/copied to imap malbox, the "offlineMsgSize" header (if any) is copied into the correspond .msf file. Then when you read that folder, SM sees the broken "offlineMsgSize" and then uses it to compute file offsets etc., which leads to corrupted email data shown. 00:39:01 BTW, the "Repair" procedure (from folder properties) drops this parameter. 00:45:01 Well, yes -- searching for "mailnews.database.summary.dontPreserveOnMove", mailnews/imap/src/nsImapMailFolder.cpp reads the pref and than ADDS some more parameters, including "offlineMsgSize". But the similar code in mailnews/local/src/nsLocalMailFolder.cpp does not add anything. So "local-->imap" move is affected. 01:00:40 Seems was bug 486007 for imap, and bug 459680 for Local. But the header was added for imap only... 01:11:01 that doesnt surprise me, i have had the feeling for awhile TB development has gone downhill for awhile now 01:12:26 Probably at that time a mail did not increase during the movement from local to imap. But then "X-Mozilla-Keys" header was added (bug 691770, bug 426651), or something later... 01:16:31 BTW, useful python2 tool to parse .msf files (at least into xml): https://github.com/KevinGoodsell/mork-converter 01:20:40 Anyway, if we already remove "size" when copy/move (in defaults prefs), nothing seems to be spoiled if we remove "offlineMsgSize" as well. 01:21:27 Probably copying from a local folder to remote imap server it tooooooo rare operation... :) 01:22:05 ...so no one has complained so far. 01:24:59 need some slppe. Will take a look tomorrow. 01:25:08 ^sleep 13:17:57 yo 13:19:04 frg_Away: and how can I test it, run autoconf or manually change in configure? 13:19:36 frg_Away: (...if SM compiles with cargo 1.46) 13:31:18 Meeting starts in 29 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-07-11 13:40:22 Meeting starts here in 20 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-07-11 13:42:33 Hi frg, IanN, ewong 13:42:54 good day WaltS48 13:43:19 WaltS48 Hi 13:44:24 fantomas Just change the minimum required level. There is no other way around it. 13:46:20 hello everyone 13:47:08 tonymec hi 13:49:18 hi tonymec 13:49:55 tonymec: hi 13:50:03 Meeting starts here in 10 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-07-11 13:54:31 hi .* 13:55:38 hi there njsg 13:58:31 Meeting starts here in 2 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-07-11 14:00:26 Meeting time - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-07-11 14:00:31 hi rsx11m 14:00:37 hi IanN 14:00:45 Hi rsx11m 14:00:48 hi frg 14:01:38 Who's taking minutes? 14:01:58 me and probably late again :) 14:02:35 thanks frg 14:03:37 Nominees for Friends of the Fish Tank? 14:03:55 ewong for fixing up the update process. 14:03:56 https://blog.seamonkey-project.org/2021/07/08/updates-3/ 14:04:13 +++ 14:04:35 agreed 14:06:00 Action Items 14:07:15 Anything still need doing on Bug 1716547? 14:07:20 Nothing from me. Sorry for not fixing the website typo. I always got sidetracked or found something elase to do :( 14:07:52 Typo fix and wanted to add the logbot. Should we do it 14:07:56 and for Bug 1716544? 14:08:13 with the current self signed cert? 14:08:34 IanN should we remove freenode or demote it down? 14:08:50 frg: demote down I would say 14:09:14 Ok will see that I find some time. 14:09:21 IanN: for 1716547 help possibly, or should that go in a separate bug? 14:10:12 njsg if not website should go into separate bug. Can go into 544 as a separate part I think. 14:10:30 If website then 547 14:11:09 agreed 14:11:17 maybe a new bug for help and a meta-bug for the network change? 14:13:12 njsg meta is a bit much I think. Seperate bug is ok with me. We can link them the website bug. 14:13:24 yeah, meta would be overkill 14:13:41 just link the bugs 14:13:48 544 already has 547 in see also 14:14:49 Status of the SeaMonkey Infrastructure 14:15:39 no change from me but updates are working :) ewong is now working in the crash stats. 14:15:49 ^on the 14:16:52 frg: not seen anything on the equivalent TB bug recently 14:18:22 mozilla seems to be dead set to do this soon. They will suffer more than us. I can live with it for some time and do private debugging if someone has a reproducable case. 14:20:49 no other changes to build infra as far as I am aware 14:21:33 Status of the SeaMonkey Source Tree 14:23:24 frg: IanN: bug 1720029 14:23:31 (for help irc link) 14:23:51 thanks njsg 14:24:04 All building I think. Prepiously only Mozilla had the habit of removing sources we use but now TB has joined them without giving notice. So far all manageable. 14:27:13 Release Train 14:27:55 2.53.8 unfortunately has a non wirking message archiving. Bug 1718839 14:29:01 Wonder if we should do a 2.53.8.1 IanN with the wip fix any severe new regressions in? Comment 5 6? 14:29:44 I didn't test yet. Did mostly reviews to get l10n changes in c-c. 14:31:40 frg: yeah, I have an idea of what to do to fix the issue I found 14:33:33 IanN show we do a 2.53.1 then? 14:33:41 2.53.8.1 14:34:03 frg: yes, we can do 14:34:12 Bug 515675 needs to go in too. 14:35:19 frg: is something broken in 2.53.8 that it fixeS? 14:35:23 Given that 2.53.9 has some extensive changes under the hood probabyl best to have a stable fallback with 2.53.8.1. 14:36:38 IanN removed the two other EnsureFolderIndex location. I am not sure what is broken now in 2.53.8 drag and drop but something is for sure. 14:37:43 suite\mailnews\content\messengerdnd.js contained them. 14:38:12 https://searchfox.org/comm-esr60/search?q=EnsureFolderIndex&path= 14:38:17 frg: ah okay 14:40:21 Extensions Tracking 14:41:09 IanN Alternative to putting the bug in might be to add the new EnsureFolderIndex(treeView, msgFolder) to mailWindowOverlay.js 14:41:28 If they are compatible 14:42:34 2.53.9 is still in flux I think. Noting from me for extensions. 14:43:21 Some outstanding reviews for cZ and also link open. Wonder if we should move them to 2.53.10 to let them bake a bit more. 14:45:27 put them in the beta but back out from 2.53.9 release? 14:46:08 unless they are too comprehensive 14:47:04 polyfill fixed some issues with using gitlab/github 14:47:17 https://github.com/JustOff/github-wc-polyfill 14:47:33 rsx11m well based on 2.53.8 and 2.53.7 I doubt that the beata is really tested... 14:47:39 ^beta 14:47:43 :-/ 14:48:31 gitlab now needs web sustom elements. From what I see for emoticons. Really important usage to put this bloat in. 14:49:40 I amy trying to get stylo into 2.53 as a prerequsite but because of ever changing rust our older stuff does not compile with current rust. 14:50:00 ^custom elements 14:50:33 got to love custom elements... 14:51:21 I am good a backporting but still needs more patches :) 14:51:56 Next wave is 4000 but most of them will probably not be needed so maybe 400 to 1000. 14:52:14 2.Next, Feature List, Planning and Roundtable 14:52:21 Just want to wait a little to see if regression crept into 2.53.9b1 pre 14:53:05 bau 14:53:26 ditto 14:53:40 Maybe we need to look at mdn links next. They want to stop displaying archived content July 14th. 14:53:58 Whatever this means. Might affect debugQA and help. 14:54:17 have to see what breaks 14:55:09 you mean https://developer.mozilla.org ? 14:55:44 and the site too, possibly 14:56:32 961 hits for developer.mozilla.org, 951 of which under src/releases 14:56:39 so release notes and download pages 14:57:03 probably depends how they define "archived content" 14:57:40 njsg: where are you searching? 14:58:03 IanN: hg grep on the site repository 14:59:17 interesting 15:00:50 https://thunderbird.topicbox.com/groups/addons/T0fc122512b7a289b-M34b8a956d00eac4a57ceea1f/fyi-deprecation-plan-for-firefox-specific-pages-on-mdn 15:01:13 > 1. Stop displaying all archived content on July 14, 2021 15:01:15 Whatever this means 15:01:28 Maybe they should just link to google com :) 15:02:38 in theory they only archives Firefox specific content 15:02:52 but again it depends what they mean by Firefox specific 15:03:47 I would wait too they removed it and then see what impact it has. 15:03:50 so, everything https://developer.mozilla.org/en-US/docs/Archive/Index_of_archived_content I'd assume 15:04:16 yes 15:05:40 We could put still relevant stuff in our website source. 15:06:25 some are not links, 730 and 720 if I grep for href=..., 61 unique addresses 15:07:12 but it is a matter of going through each unique link and working out if it has been archived and working out the best source going forward 15:07:42 If these are years old release notes or news I would not care. 15:07:46 that could be a link to another source or copying into our website 15:09:00 yeah, agreed 15:10:30 so recent news / releases notes, last 2 years? then other areas 15:11:40 yeah. Anything prominent first and then walking "down". 15:12:31 ShouldnÄt be a problem with our active community helping out :D 15:14:05 the alternative is to just clone the archive ;-) 15:15:10 loads of rubbish we don't want, but perhaps things that mention SeaMonkey might be useful to clone 15:16:56 okay, AOB? 15:17:23 bau again 15:17:40 Next meeting is in 2 weeks time 15:17:47 same bat time, same bat channel 15:18:11 I can post the agenda and invitation but have a conflict on the 25th 15:18:27 no problem in general, though - just to let you know 15:18:46 rsx11m I usually repost to alt.comp.software.seamonkey. 15:19:02 Forgot this time so late today. 15:20:12 thanks for your time everyone 15:20:25 have fun! 15:20:33 you too 15:21:04 bye 15:22:16 bye 15:38:02 frg_Away: thanks, but how do I change required cargo level ? 15:42:04 fantomas I am on 2.53.9. Check if python/mozboot/mozboot/util.py contains 1.47 and just set to 1.43 15:45:02 MINIMUM_RUST_VERSION = '1.47.0' 15:45:08 is that used for cargo version too? 15:45:36 ...it is. Thanks. 16:37:46 Regarding http://logbot.buc.me/seamonkey/20210711#c1985 "offlineMsgSize" -- it seems a decade old issue, described in bug 426651 (and other related). 16:37:52 Mails in local folders have additional headers added, from "X-Mozilla-" namespace. When such a mail is copied/moved to a remote imap server, most of such headers are dropped, but "X-Mozilla-Keys" remains (bug 426651). But "offlineMsgSize" parameter does not count this header's bytes, and then imap server can receive wrong size. 16:38:46 Besides the 99 bytes of the header, also one additional newline is added to the end of the mail (ie. total 100). 16:41:42 It is very old (10 years) and seems rare issue. SM <= 2.49.5 affected as well. А bit of a pity that already at that time TB stopped taking proper care of the perfection of his code. :( 18:00:16 buc do you have a sample mail? I see the behaviour but my mails did not trigger the bad display of them. 19:23:51 well, SM 2.53.8 does compile with cargo-1.46.0 22:52:42 frg: I could set a testing account on my imap server right now. 22:52:44 The bug is reliably reproduced if it has already appeared. However, it is not clear at all how to create a certain simple test "from scratch". And it was mentioned in those bug reports. Therefore the easiest way is just to clone the environment in which the bug is reproduced. 23:09:40 frg: Well, I've create imap testing account. Ping me in private... 23:14:20 buc Thanks. Need to sleep. Have to run some errands early. Wil ping you Monday evening. I have an imap account with gmx just unable to find a good test message. Might not be able to fix it. This is a bit over my head. 23:14:31 see you tomorrow.