| dcaliste | Hello Chris, how are you ? | 07:05 |
|---|---|---|
| chriadam | dcaliste: Hi, well thanks | 07:09 |
| chriadam | how are you? I hope you had a great week | 07:09 |
| dcaliste | Thanks for the review today, I'm replying to your remarks. | 07:09 |
| chriadam | thanks very much for your work! | 07:10 |
| chriadam | btw, in regards to the blog post, Jaymzz contacted me to say that there has been some delay | 07:11 |
| chriadam | I'm not entirely sure why | 07:11 |
| chriadam | and I don't know how long it's likely to be delayed for | 07:11 |
| dcaliste | Too bad, that !48 slipped in :( I'm migrating my own calendar from a radicale server that I was seldomly using too a webserver based on OpenXchange, I should be able to spot regression like that sooner (hopefully)… | 07:11 |
| chriadam | I will ask him to contact you directly to give you an update | 07:11 |
| chriadam | dcaliste: eh, these things happen. my testing was clearly not extensive enough either. | 07:12 |
| dcaliste | For the blog post, no problem, anyway everyone is on holidays at that period ;) Well, let say half, not accounting for the south hemisphere ones ;) | 07:12 |
| chriadam | indeed :-) | 07:12 |
| chriadam | we have some tasks from internal business customers related to CalDAV invitation handling | 07:14 |
| chriadam | so I'm currently looking into that | 07:14 |
| chriadam | which is good, as it means that I can spend some time and effort testing your changes to ensure they don't conflict etc with that work. | 07:15 |
| dcaliste | Oh, great. You may be interested in https://together.jolla.com/question/209964/thought-remarks-on-the-new-ui-31011/?answer=211213#post-id-211213 | 07:16 |
| dcaliste | But it's good news that you can allocate time for CalDAV again ! | 07:17 |
| chriadam | yes, that sounds like a regression we'd like to fix as part of this effort for invitation handling, definitely | 07:17 |
| chriadam | the "flickering" of the attendee list might be due to a synchronisation occuring in the background, perhaps.. | 07:18 |
| chriadam | but the " issue is interesting | 07:18 |
| dcaliste | I concluded the same yesterday ;) | 07:18 |
| dcaliste | The fact that flickering is happening at calendar launch is a lead: it is triggering sync at startup. | 07:19 |
| chriadam | indeed | 07:19 |
| chriadam | eek just noticed the carddav unicode sync issue which was mentioned in that one | 07:23 |
| dcaliste | About !49, as mentioned in my answer, I need to improve the RegExp a bit to catch the other escaping like Ă as you mentioned. | 07:23 |
| chriadam | added a comment to that tjc so hopefully someone else might start to contribute - that'd be great | 07:23 |
| chriadam | dcaliste: no doubt there will be a thousand edge cases, might be tricky to catch them all.. | 07:24 |
| dcaliste | About unnoticed TJC report, we should favor triaging so opening a proper bug report (even in TJC) from a user leaving a remark… | 07:30 |
| dcaliste | on the HTML escaping, I think, we're not too far from a safe routine. You're already tranforming problematic characters like '<' or '>' and then with a proper regexp, we should avoid transforming valid already escaped HTML ones. | 07:32 |
| chriadam | indeed. our testers did create bug report internally JB#41389, but for some reason I wasn't cc'd to that one | 07:34 |
| chriadam | true, well I guess only testing in real world will tell us if there are edge cases we missed. but I think you're right, I guess the HTML escape codes are all well-formed so the regex should easily catch those and avoid transforming ones which are already valid ones | 07:35 |
| dcaliste | I'm testing at the moment the new reg exp… | 07:38 |
| chriadam | regarding upsync vs downsync support, I wonder if it's worth supporting: two way sync, downsync only. i.e. don't support "upsync only" semantic. | 07:41 |
| chriadam | well, we can support all three in backend as you've done, but then only expose the first two in the accounts UI | 07:41 |
| dcaliste | I agree that I don't see any use of upsync only, but we never know… Adjusting the UI is a must though because currently it is exposing options that have no effect :/ Not that I was using any of them though ! | 07:43 |
| chriadam | indeed :-( our bad | 07:45 |
| chriadam | I will create an internal bug about that also so it doesn't get forgotten | 07:45 |
| chriadam | created JB#46915 | 07:49 |
| dcaliste | About the parsing of data containing for instance, it's not working at the moment. I need more time for investigation. I'll push later today when I figure out what's wrong with other entities than the one already used in helper function… | 07:50 |
| dcaliste | Ok for the bug id, I'll add it to the commit. Thanks. | 07:50 |
| chriadam | thank you | 07:50 |
| dcaliste | I wanted to mention also that next Tuesday is my son's birthday, I won't be able to attend our meeting. | 07:51 |
| chriadam | ah, no worries - I hope he has a happy birthday | 07:52 |
| chriadam | hopefully I will make good progress on testing+merging+tagging your various caldav PRs this week | 07:52 |
| chriadam | also I will poke Jaymzz to give you an update on ETA for the blog etc | 07:53 |
| chriadam | I had nothing else to discuss - was there anything else I forgot about which I need to follow up on? | 07:53 |
| dcaliste | No, I think it's fine. Thank you for the meeting and have a nice evening. | 07:54 |
| chriadam | thank you very much for your time and effort | 07:54 |
| chriadam | have a great couple of weeks | 07:54 |
| *** jpich_ is now known as jpich | 09:24 | |
| *** frinring_ is now known as frinring | 14:17 | |
| sailorAxe | is there a way to kill the fingerterm process without rebooting when fingerterm refuses to open? | 19:14 |
| kimmoli | ssh in | 19:16 |
| sailorAxe | ...so effectively no? | 19:19 |
| kimmoli | restart lipstick? | 19:20 |
| sailorAxe | How do I do that withot external devices and without a working terminal software? :) | 19:30 |
| kimmoli | sailfish utilities | 19:39 |
| kimmoli | https://jolla.zendesk.com/hc/en-us/articles/203837576#restart_home | 19:39 |
| sailorAxe | ...actually, an app called Crest helped :) | 19:42 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!