Re: AJAX error on chrome with latest 8.4 release
Hi, Just to follow up. This was neither a wicket error nor a chrome problem but some weird combination of non rolled back transaction + some transaction controlling filter on top of of wicket filter (that was somehow truncating response). On Tue, Apr 16, 2019 at 6:36 PM Maxim Solodovnik wrote: > Maybe non-minimized stacktrace can gave some more info? > > On Tue, 16 Apr 2019 at 22:35, Ernesto Reinaldo Barreiro > wrote: > > > > Hi, > > > > Bumping jQuery version to 3.4.0 provides same results (no minimized). > > > > On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik > > wrote: > > > > > non minified jquery and/or wicket.mode=DEVELOPMENT > > > May be it will shed some light on this issue ... > > > > > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > > > reier...@gmail.com> > > > wrote: > > > > > > > Hi, > > > > > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik < > solomax...@gmail.com> > > > > wrote: > > > > > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > > > > > > > Do you mean jquery non minified jQuery? > > > > > > > > -- > > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > -- > WBR > Maxim aka solomax > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
And thanks again for feedback and comments! On Thu, Apr 18, 2019 at 10:24 AM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > Just to follow up. This was neither a wicket error nor a chrome problem > but some weird combination of non rolled back transaction + some > transaction controlling filter on top of of wicket filter (that was somehow > truncating response). > > On Tue, Apr 16, 2019 at 6:36 PM Maxim Solodovnik > wrote: > >> Maybe non-minimized stacktrace can gave some more info? >> >> On Tue, 16 Apr 2019 at 22:35, Ernesto Reinaldo Barreiro >> wrote: >> > >> > Hi, >> > >> > Bumping jQuery version to 3.4.0 provides same results (no minimized). >> > >> > On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik >> > wrote: >> > >> > > non minified jquery and/or wicket.mode=DEVELOPMENT >> > > May be it will shed some light on this issue ... >> > > >> > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < >> > > reier...@gmail.com> >> > > wrote: >> > > >> > > > Hi, >> > > > >> > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik < >> solomax...@gmail.com> >> > > > wrote: >> > > > >> > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? >> > > > > >> > > > >> > > > Do you mean jquery non minified jQuery? >> > > > >> > > > -- >> > > > Regards - Ernesto Reinaldo Barreiro >> > > > >> > > >> > > >> > > -- >> > > WBR >> > > Maxim aka solomax >> > > >> > >> > >> > -- >> > Regards - Ernesto Reinaldo Barreiro >> >> >> >> -- >> WBR >> Maxim aka solomax >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > -- > Regards - Ernesto Reinaldo Barreiro > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Maybe non-minimized stacktrace can gave some more info? On Tue, 16 Apr 2019 at 22:35, Ernesto Reinaldo Barreiro wrote: > > Hi, > > Bumping jQuery version to 3.4.0 provides same results (no minimized). > > On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik > wrote: > > > non minified jquery and/or wicket.mode=DEVELOPMENT > > May be it will shed some light on this issue ... > > > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> > > wrote: > > > > > Hi, > > > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > > > wrote: > > > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > > > > Do you mean jquery non minified jQuery? > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > > > -- > Regards - Ernesto Reinaldo Barreiro -- WBR Maxim aka solomax - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: AJAX error on chrome with latest 8.4 release
Hi, Bumping jQuery version to 3.4.0 provides same results (no minimized). On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik wrote: > non minified jquery and/or wicket.mode=DEVELOPMENT > May be it will shed some light on this issue ... > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > > wrote: > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > Do you mean jquery non minified jQuery? > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Wicket is on development mode already. I'm serving "my own" minified version of jquery. I will play with that next and try to "reorder my code" to see if I can spot what is different. On Tue, Apr 16, 2019 at 5:28 PM Maxim Solodovnik wrote: > non minified jquery and/or wicket.mode=DEVELOPMENT > May be it will shed some light on this issue ... > > On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > > wrote: > > > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > > > > Do you mean jquery non minified jQuery? > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
non minified jquery and/or wicket.mode=DEVELOPMENT May be it will shed some light on this issue ... On Tue, 16 Apr 2019 at 20:59, Ernesto Reinaldo Barreiro wrote: > Hi, > > On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik > wrote: > > > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > > > > Do you mean jquery non minified jQuery? > > -- > Regards - Ernesto Reinaldo Barreiro > -- WBR Maxim aka solomax
Re: AJAX error on chrome with latest 8.4 release
Hi, On Tue, Apr 16, 2019 at 4:36 PM Maxim Solodovnik wrote: > Is it reproducible with non-minified (i.e. DEVELOPMENT) version? > Do you mean jquery non minified jQuery? -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Is it reproducible with non-minified (i.e. DEVELOPMENT) version? On Tue, 16 Apr 2019 at 20:34, Ernesto Reinaldo Barreiro wrote: > Hi Maxim, > > Thanks for feedback. > > wicket-jquery-ui based Wizard works for me as expected (just have tested > > Chrome latest at Ubuntu 18.10) > > > > We are using or own home grown implementation of a wizard on top of a > custom wrapper around bootstrap modal (I was the person creating those > components, so I know them well). We have many similar wizards in > application. I was expecting this wizard to be the same :-( I have already > tested some of the other wizards and they still work. Funny thing is we are > not doing anything particularly different here.. Or so I believe :-) > > > > > > On Tue, 16 Apr 2019 at 18:33, Ernesto Reinaldo Barreiro < > > reier...@gmail.com> > > wrote: > > > > > Hi, > > > > > > I'm experiencing following error > > > > > > POST > > > > > > > > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > > > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > > > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > > > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > > > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > > > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > > > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > > > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > > > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > > > > > On latest Chrome on Mac. This does not happens with latest FF (So, I > > assume > > > this is a wicket bug). Is this a known issue? Our application is very > > > complicated and I'm not sure I will be able to create a quickstart. > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > -- > > WBR > > Maxim aka solomax > > > > > -- > Regards - Ernesto Reinaldo Barreiro > -- WBR Maxim aka solomax
Re: AJAX error on chrome with latest 8.4 release
Hi Maxim, Thanks for feedback. wicket-jquery-ui based Wizard works for me as expected (just have tested > Chrome latest at Ubuntu 18.10) > We are using or own home grown implementation of a wizard on top of a custom wrapper around bootstrap modal (I was the person creating those components, so I know them well). We have many similar wizards in application. I was expecting this wizard to be the same :-( I have already tested some of the other wizards and they still work. Funny thing is we are not doing anything particularly different here.. Or so I believe :-) > > On Tue, 16 Apr 2019 at 18:33, Ernesto Reinaldo Barreiro < > reier...@gmail.com> > wrote: > > > Hi, > > > > I'm experiencing following error > > > > POST > > > > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > > > On latest Chrome on Mac. This does not happens with latest FF (So, I > assume > > this is a wicket bug). Is this a known issue? Our application is very > > complicated and I'm not sure I will be able to create a quickstart. > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > > > > -- > WBR > Maxim aka solomax > -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Hello Ernesto, wicket-jquery-ui based Wizard works for me as expected (just have tested Chrome latest at Ubuntu 18.10) On Tue, 16 Apr 2019 at 18:33, Ernesto Reinaldo Barreiro wrote: > Hi, > > I'm experiencing following error > > POST > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > On latest Chrome on Mac. This does not happens with latest FF (So, I assume > this is a wicket bug). Is this a known issue? Our application is very > complicated and I'm not sure I will be able to create a quickstart. > > -- > Regards - Ernesto Reinaldo Barreiro > -- WBR Maxim aka solomax
Re: AJAX error on chrome with latest 8.4 release
Hi Martin, Many thanks for your answer. > > https://stackoverflow.com/questions/22608564/neterr-incomplete-chunked-encoding-in-chrome-only > suggests > that it might be a local problem. Some people said that disabling the > antivirus software helped them, others had no disk space, ... > > Yes I have read that post but I have no antivirus running... I will check around to see what I can spot. > If you are able to reproduce it with wicket-examples or any other way then > please open an issue at JIRA! > Ok. I will try first to see what might be "wrong" with my computer + ask other team members to try failing code locally in order to check if it is just my computer. -- Regards - Ernesto Reinaldo Barreiro
Re: AJAX error on chrome with latest 8.4 release
Hi Ernesto, No, it is not known. https://stackoverflow.com/questions/22608564/neterr-incomplete-chunked-encoding-in-chrome-only suggests that it might be a local problem. Some people said that disabling the antivirus software helped them, others had no disk space, ... If you are able to reproduce it with wicket-examples or any other way then please open an issue at JIRA! On Tue, Apr 16, 2019 at 2:33 PM Ernesto Reinaldo Barreiro < reier...@gmail.com> wrote: > Hi, > > I'm experiencing following error > > POST > > http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button > net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 > send @ jquery-3.2.1.min-ver-1555412805000.js:4 > ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 > doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 > e @ jquery-3.2.1.min-ver-1555412805000.js:2 > schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 > schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 > ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 > (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 > dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 > q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 > > On latest Chrome on Mac. This does not happens with latest FF (So, I assume > this is a wicket bug). Is this a known issue? Our application is very > complicated and I'm not sure I will be able to create a quickstart. > > -- > Regards - Ernesto Reinaldo Barreiro >
AJAX error on chrome with latest 8.4 release
Hi, I'm experiencing following error POST http://10.211.55.6:8080/kms2/advanced-search?1-2.0-body-wizardModal-modal-form-footer-volatileButtons-3-button net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 send @ jquery-3.2.1.min-ver-1555412805000.js:4 ajax @ jquery-3.2.1.min-ver-1555412805000.js:4 doAjax @ wicket-ajax-jquery-ver-1555412805000.js:692 (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:556 e @ jquery-3.2.1.min-ver-1555412805000.js:2 schedule @ wicket-ajax-jquery-ver-1555412805000.js:289 schedule @ wicket-ajax-jquery-ver-1555412805000.js:349 ajax @ wicket-ajax-jquery-ver-1555412805000.js:555 (anonymous) @ wicket-ajax-jquery-ver-1555412805000.js:1793 dispatch @ jquery-3.2.1.min-ver-1555412805000.js:3 q.handle @ jquery-3.2.1.min-ver-1555412805000.js:3 On latest Chrome on Mac. This does not happens with latest FF (So, I assume this is a wicket bug). Is this a known issue? Our application is very complicated and I'm not sure I will be able to create a quickstart. -- Regards - Ernesto Reinaldo Barreiro
