Penetration Testing Results - Some Issues
-
Thanks for the feedback Boris!
-
When upgrading from version 2.2.0 to 2.4.0 (or later) we get the following red wall of text. What's going wrong here?
-
hi! hmm i think this problem is related to a folders migration logic we run when you update to any version > 2.3.0.
are you storing your templates using fs-store?
this is a similar topic https://forum.jsreport.net/topic/1262/error-because-of-folder-shortid/6 in which i ask for some help to reproduce the issue so we can fix it, maybe you can help us sharing your original entities (the entities previous the jsreport upgrade to 2.4.0), you can share a zip of your
datafolder and your config file privately via email if you want to help us to fix this. unfourtunately this is the best way for us to replicate the problem, since we are not able to replicate the same issue, so it probably means that it is only affecting some specific migrations and your case will help to verify this.quote from the other topic:
are you able to replicate the issue every time you upgrade the jsreport? i mean, if you go back to your previous jsreport/jsreport:2.0.0-full image with the same data folder that you have at that time, and then try to upgrade to jsreport/jsreport:2.6.1-full, does the issue continues to happen every time? if this is something you can reproduce every time you try to migrate from jsreport/jsreport:2.0.0-full to jsreport/jsreport:2.6.1-full then best will be that you share with us the data folder that you have on jsreport/jsreport:2.0.0-full so we can inspect what is happening, since the addition of folders entities to jsreport (v2.3.0) there is a migration step that we run at jsreport startup that tries to migrate entities to folders, it can be the case that this migration is causing this issue by duplicating the shortid, however we never saw this before.
-
Hi Boris,
I can downgrade back to 2.2.0 and the server runs fine. Any time I go to 2.4.0 or greater, this red screen is presented. I've tried every version between 2.6.1 and 2.3.0, and they all show the red screen.
Yes, we're using fs.
I have included our config file in the zip (and also the start-up script, as it installs some specific npm modules into the docker container) - where should I email it to?
-
I have included our config file in the zip (and also the start-up script, as it installs some specific npm modules into the docker container) - where should I email it to?
thanks, this will really help to verify the problem. you can send it to bjrmatos@gmail.com
-
@izelt i have received the email with the details, we will check the problem and reply here with some news when we find the issue. thanks for the help
-
Any update on this @bjrmatos ?
-
not yet, it is added to my work queue so i will get to it soon, sorry for the wait
-
@izelt sorry for the long wait. FYI i have sent you email with some notes about the problem and a workaround for your case.
-
That appears to have worked in the lab Boris! Prod soon. Thank you.
