report_py3o: empty fields displayed as False about reporting-engine HOT 16 CLOSED

It has been fixed several months ago, cf this commit:
https://bitbucket.org/faide/py3o.template/commits/bb6b837778526eb87c77ffe34b65f136411e3ab1
and with that line of code:
https://github.com/OCA/reporting-engine/blob/10.0/report_py3o/models/py3o_report.py#L244
where the escape_false=True has been added.

Are you sure you have up-to-date code for report_py3o and py3o.template ?

from reporting-engine.

Maybe your docker image is not up-to-date for py3o.template... it will work fine if you have py3o.template==0.9.11.

from reporting-engine.

@guewen Did you find the solution ? Can we close the bug ?

from reporting-engine.

Thanks for your fast answer!

You are right, this issue doesn't happen when the Local Fusion is enabled. I'm using the fusion server though. Which brings me to the next question: should we use the fusion server at all? I read it's recommended to use it but what are the reasons? Stability?

Any hint on how I could correct this issue when using the fusion server? (I had to apply #120 to be able to use the server).

Details of the versions:

version: '2'
services:

  oooserver:
    image: xcgd/libreoffice:latest
    volumes:
      - "data-py3o:/tmp"

  py3orenderserver:
    image: xcgd/py3oserver-docker:latest
    depends_on:
      - oooserver
    ports:
      - "8994:8994"
    volumes:
      - "data-py3o:/tmp"

  py3ofusion:
    image: xcgd/py3o.fusion:latest
    depends_on:
      - py3orenderserver
    ports:
      - "8765:8765"

  odoo:
    depends_on:
      - py3ofusion
      - py3orenderserver

volumes:
  data-py3o:

root@2af7cdf83e86:/# pip freeze
beautifulsoup4==4.4.1
chardet==2.3.0
constantly==15.1.0
Genshi==0.7
html5lib==0.999
incremental==16.10.1
lxml==3.6.4
py3o.formats==0.3
py3o.fusion==0.8.6
py3o.renderclient==0.2
py3o.template==0.9.11
py3o.types==0.1.1
pyf.splitter==3.1
pyf.station==2.0.5
pyf.transport==2.0.1
Pygments==2.1.3
pyjon.events==1.2
pyjon.utils==0.7
python-dateutil==2.6.0
simplejson==3.10.0
six==1.10.0
Twisted==16.6.0
zope.interface==4.3.2

root@0c667e3369dc:/# pip freeze
constantly==15.1.0
incremental==16.10.1
JPype1==0.6.1
py3o.formats==0.3
py3o.renderers.juno==0.8
py3o.renderserver==0.5.1
pyf.splitter==3.1
pyf.station==2.0.5
pyf.transport==2.0.1
pyjon.events==1.2
pyjon.utils==0.7
python-dateutil==2.6.0
simplejson==3.10.0
six==1.10.0
Twisted==16.6.0
zope.interface==4.3.2

from reporting-engine.

Hi Guewen,

Fusion server is used for scalability because it offloads some of the work from Odoo and is extensible (not done yet) to use multiple libreoffice instances in parallel.

If you don't have a huge workload you don't really need it.

What docker image did you use? It may be possible that our fusion server image is was not yet updated to contain the latest changes from py3o.template

EDIT: I dit not see your detailed info about versions. You indeed used our fusion server image. This must be the issue. Would you mind proposing a PR to the py3o.fusion docker image repository that uses the needed versions?

from reporting-engine.

Thanks Florent. I put the details in the comment above (you can unroll the "Details"). I used the latest images (but also tried with the versioned images but they have less recent libraries). The latest fusion image uses py3o.template==0.9.11.

However, could it be that the fusion server does not set espace_false to True when rendering (default being False)? (https://bitbucket.org/faide/py3o.fusion/src/40436176fc54399d762c3d5fec7e324cc6c3e9c1/py3o/fusion/formpage.py?at=default&fileviewer=file-view-default#formpage.py-397)

from reporting-engine.

@faide reading your edit, I'll check the libs versions

from reporting-engine.

@guewen good catch on the formpage.py l397, this must be it.

What would be the most sensible way to pass this option? I propose we change the input payload sent to the server to include this option...

from reporting-engine.

@faide proposal here:

py3ofusion: https://bitbucket.org/faide/py3o.fusion/pull-requests/1/add-templating-options-in-the-form/diff
report_py3o: #122

Let me know if I need to change anything.

from reporting-engine.

fusion PR is merged and released on Pypi

we now see we concerned people so that the docker image gets a stable 0.8.7 release will keep you posted ^^

from reporting-engine.

btw look at the py3o.fusion CONTRIBUTORS file and please feel free to amend the line about yourself (I did not put your email, because I did not know if you wanted to)

from reporting-engine.

fusion PR is merged and released on Pypi

we now see we concerned people so that the docker image gets a stable 0.8.7 release will keep you posted ^^

Yeah! Thanks

from reporting-engine.

thanks all! 🎆

from reporting-engine.

@guewen the docker image is released on docker hub!

from reporting-engine.

Thanks a lot, deploying it to our test server, I keep you updated

from reporting-engine.

Test successful with the image xcgd/py3o.fusion:0.8.7 and after having applied #120 and #122 :)

from reporting-engine.