From goffi at goffi.org Thu Jan 14 22:31:18 2016 From: goffi at goffi.org (Goffi) Date: Thu, 14 Jan 2016 22:31:18 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [en] Need help to track an Ajax issue with Firefox Message-ID: <3641602.6muIqynEJq@necton3> Hello, I have an issue with Firefox/Iceweasel 43. If I launch the devtools with the console or the network tab, I realise that many post request (Ajax request with XmlHttpRequest) are aborted. This usually means a network issue, or a coding error (or a abort() made on purpose), but I haven't found the problem so far. I'm running a Debian Sid, and I have tried with the beta of firefox 44 and have the same problem (I have also tried --safe-mode to avoid add-ons). But if I go with Chromium, I don't have this issue at all. The issue is also happening on the demo on libervia.org, and I don't know when it started (it's a bit difficult to bisect the code as we have had many changes during the 0.6.0 developing phase, on different components). So if some of you can try to use libervia.org and tell me if they have post request aborted using the devtools/network tab (they appear in red in this case), specially on json_signal. I have tried on an other computer with firefox 42, no pb there, so I suspect a bug on firefox 43. Also the loading of libervia is really slow if you have a lot of articles, this is due to the creation of blog widget with pyjamas, we'll try to improve that. We were talking about realising 0.6.1 for last Christmas, but we have finally decided it would be better to wait a few weeks more and release a more stable version. We have already fixed a lot of annoying bugs :) Cheers Goffi From baptiste at mouterde.fr Sat Jan 16 00:09:02 2016 From: baptiste at mouterde.fr (Baptiste Mouterde) Date: Sat, 16 Jan 2016 00:09:02 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Ben=5D_Need_help_to_trac?= =?utf-8?q?k_an_Ajax_issue_with_Firefox?= In-Reply-To: <3641602.6muIqynEJq@necton3> References: <3641602.6muIqynEJq@necton3> Message-ID: <56997C0E.8080902@mouterde.fr> Hey! I did the test here. running debian sid and iceweasel 38 was fine. but on iceweasel 43 I have the same problem. I noticed once I did an action (sending a message, changing status) the blocked request end its journey to the land of libervia. So I guess the request is pending until latest status change? hope this can help :) o/ ko_lo aka bmouterd On 14/01/2016 22:31, Goffi wrote: > Hello, > > I have an issue with Firefox/Iceweasel 43. If I launch the devtools with the > console or the network tab, I realise that many post request (Ajax request > with XmlHttpRequest) are aborted. This usually means a network issue, or a > coding error (or a abort() made on purpose), but I haven't found the problem > so far. > > I'm running a Debian Sid, and I have tried with the beta of firefox 44 and have > the same problem (I have also tried --safe-mode to avoid add-ons). But if I go > with Chromium, I don't have this issue at all. > > The issue is also happening on the demo on libervia.org, and I don't know when > it started (it's a bit difficult to bisect the code as we have had many changes > during the 0.6.0 developing phase, on different components). > > So if some of you can try to use libervia.org and tell me if they have post > request aborted using the devtools/network tab (they appear in red in this > case), specially on json_signal. > > I have tried on an other computer with firefox 42, no pb there, so I suspect a > bug on firefox 43. > > Also the loading of libervia is really slow if you have a lot of articles, > this is due to the creation of blog widget with pyjamas, we'll try to improve > that. > > We were talking about realising 0.6.1 for last Christmas, but we have finally > decided it would be better to wait a few weeks more and release a more stable > version. We have already fixed a lot of annoying bugs :) > > Cheers > Goffi > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev > -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: signature.asc Type: application/pgp-signature Taille: 819 octets Desc: OpenPGP digital signature URL: From goffi at goffi.org Sat Jan 16 22:07:19 2016 From: goffi at goffi.org (Goffi) Date: Sat, 16 Jan 2016 22:07:19 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Ben=5D_Need_help_to_trac?= =?utf-8?q?k_an_Ajax_issue_with_Firefox?= In-Reply-To: <56997C0E.8080902@mouterde.fr> References: <3641602.6muIqynEJq@necton3> <56997C0E.8080902@mouterde.fr> Message-ID: <6114536.YDEg67vhVx@necton3> Le samedi 16 janvier 2016, 00:09:02 Baptiste Mouterde a écrit : > Hey! Hi Baptiste, thanks for your feedback > I did the test here. running debian sid and iceweasel 38 was fine. > but on iceweasel 43 I have the same problem. Ok, so that confirm that there is an issue with Firefox/Iceweasel 43. It can be either a behaviour change, or a bug. > I noticed once I did an action (sending a message, changing status) the > blocked request end its journey to the land of libervia. > So I guess the request is pending until latest status change? There are 2 kinds of requests: methods call (when you have any action: sending a message or changing a status), and the one managing signals, json_signal_api, which use long polling technique and is called again each time a signal is received (a signal is any event: new message received, status has changed, etc). So json_signal_api should be pending nearly all the time, and when a signal is received, a new call is made. It really smells like a Firefox bug. By the way, I have committed a change yesterday (not yet available on the online demo), which show a visual feedback (not only in javascript console) to the user when connection with server is lost, so this issue should be more obvious. Also we are planing to move to websockets, but this is not a priority at all as current behaviour is (normally) working well, and we have many other things to do. If we can't find a solution, we'll maybe move on websocket earlier as planed. > hope this can help :) It does, thanks. I had to validate you message, which was blocked because you are not subscribed on the list. Did you post with the same address that your subscribed one? Thanks Goffi From goffi at goffi.org Sat Jan 16 22:55:50 2016 From: goffi at goffi.org (Goffi) Date: Sat, 16 Jan 2016 22:55:50 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Ben=5D_Need_help_to_trac?= =?utf-8?q?k_an_Ajax_issue_with_Firefox?= In-Reply-To: <6114536.YDEg67vhVx@necton3> References: <3641602.6muIqynEJq@necton3> <56997C0E.8080902@mouterde.fr> <6114536.YDEg67vhVx@necton3> Message-ID: <2886775.YTLH9vNmKM@necton3> I have filled a bug on Mozilla's bugzilla: https://bugzil.la/1240319 Le samedi 16 janvier 2016, 22:07:19 Goffi a écrit : > Le samedi 16 janvier 2016, 00:09:02 Baptiste Mouterde a écrit : > > Hey! > > Hi Baptiste, thanks for your feedback > > > I did the test here. running debian sid and iceweasel 38 was fine. > > but on iceweasel 43 I have the same problem. > > Ok, so that confirm that there is an issue with Firefox/Iceweasel 43. It can > be either a behaviour change, or a bug. > > > I noticed once I did an action (sending a message, changing status) the > > blocked request end its journey to the land of libervia. > > So I guess the request is pending until latest status change? > > There are 2 kinds of requests: methods call (when you have any action: > sending a message or changing a status), and the one managing signals, > json_signal_api, which use long polling technique and is called again each > time a signal is received (a signal is any event: new message received, > status has changed, etc). So json_signal_api should be pending nearly all > the time, and when a signal is received, a new call is made. > > It really smells like a Firefox bug. > > By the way, I have committed a change yesterday (not yet available on the > online demo), which show a visual feedback (not only in javascript console) > to the user when connection with server is lost, so this issue should be > more obvious. > > Also we are planing to move to websockets, but this is not a priority at all > as current behaviour is (normally) working well, and we have many other > things to do. If we can't find a solution, we'll maybe move on websocket > earlier as planed. > > > hope this can help :) > > It does, thanks. > > I had to validate you message, which was blocked because you are not > subscribed on the list. Did you post with the same address that your > subscribed one? > > > Thanks > Goffi > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From goffi at goffi.org Thu Jan 21 13:34:17 2016 From: goffi at goffi.org (Goffi) Date: Thu, 21 Jan 2016 13:34:17 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Ben=5D_Need_help_to_trac?= =?utf-8?q?k_an_Ajax_issue_with_Firefox?= In-Reply-To: <2886775.YTLH9vNmKM@necton3> References: <3641602.6muIqynEJq@necton3> <6114536.YDEg67vhVx@necton3> <2886775.YTLH9vNmKM@necton3> Message-ID: <121117401.qtuDmLM0A3@necton3> Le samedi 16 janvier 2016, 22:55:50 Goffi a écrit : > I have filled a bug on Mozilla's bugzilla: https://bugzil.la/1240319 It was indeed a Firefox/Iceweasel bug, as you can see in the bugreport, the bug is now fixed in last nighly builds. So it you see weird behaviour with Libervia, just downgrade to firefox 42, or wait for the patch to be released. ++ Goffi From goffi at goffi.org Tue Jan 26 09:22:17 2016 From: goffi at goffi.org (Goffi) Date: Tue, 26 Jan 2016 09:22:17 +0100 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= Quelques nouvelles/some news Message-ID: <3033763.GEJzeYD2HZ@necton3> english below Salut à tous, quelques nouvelles rapides: - ce jeudi et vendredi auront lieux le 19ème « XMPP summit » où je serai présent pour SàT. C'est un moment où beaucoup de discussions techniques ont lieu, mais c'est surtout l'occasion de connaître une partie de la communauté XMPP - juste après viendra le Fosdem, où je ferai 2 conférences : https://fosdem.org/2016/schedule/event/decentralized_social_network/ (salle Python à samedi à 13:30) et https://fosdem.org/2016/schedule/event/decentralized_blogging_with_xmpp/ (salle RTC samedi à 18:00). Si vous y êtes n'hésitez pas à venir me voir après les confs, ou au « lounge XMPP » où je serai certainement régulièrement - nous avons corrigé pas mal de bugs gênants dans la 0.6.0, et nous préparons donc une 0.6.1 pour d'ici 2 ou 3 semaines (nous préférons attendre pour corriger le maximum de problèmes) - nous avons travaillé sur l'import de blogs, et nous pouvons désormais importer des blogs Dokuwiki (pas encore disponible dans la version de dév) et Dotclear. Il y a plusieurs nouveautés liés à ça que j'expliquerai sans doute dans un article de blog bientôt - le travail sur la version bureau/Android n'a pas encore pu commencer, il devrait démarrer peu après le Fosdem. Goffi -- G'day, some news: - there will be the 19th XMPP summit this Thursday, which I'll attend for SàT. It's a time for technical discussions, and mainly to meet a part of the XMPP community - next there will be the Fosdem where I'll have 2 talks: https://fosdem.org/2016/schedule/event/decentralized_social_network/ (Python devroom, Saturday 13:30) and https://fosdem.org/2016/schedule/event/decentralized_blogging_with_xmpp/ (RTC devroom 18:00). If you come, don't hesitate to meet me after the talks, or at the "XMPP lounge where I should be quite often. - we have fixed many annoying bugs from the 0.6.0, and we are planing to release a 0.6.1 in about 2 or 3 weeks (we rather wait to fix most of issues) - we have worked on blog import, and we can now import blogs from Dokuwiki (not available yet in dev version) and Dotclear. There a a couple of linked new features that I'll probably explain soon in a blog post. - the work on desktop/Android frontend hasn't started yet, it should soon after the Fosdem Goffi