Hi @jan_blaha,
I can verify that the import in version 3.0.1 is way faster. The other good thing is also that is visible now in the logs when the import starts and when it is finished. We are thinking about an upgrade. Congratulations on the new version.
Unfortunately, we also tried the import of our templates on the new version 3.0.1 but with the same issues.
Dear @jan_blaha,
unfortunately, we still have the issue that we can not reliably work with jsReport because after re-starts of jsReport the imported files disappear from the Application and we can not generate files.
Is there a way how I can send you our sample export files in different versions so you can take a look at why it is it not working?
We already tried a look at different things, like importing in different jsReport versions etc.
Also your provided sample was working on our side without an issue. But as far as I can see your sample is around 103 kb in size and our samples are already around 600 to 700 kb in size.
Mr. Blaha,
do you have an import/export file you could send me which was working for you so I can try it out with another data sample on our environment? So I can also verify your outcome.
Importing partially (less data) from one instance to another in our environment leads to more correct behaviour. This means the data is imported and the ~.tran folder is deleted afterwards. But this is not our normal use case. Usually, we simply want to merge the data from e.g. Staging to Production.
Hi Mr. @jan_blaha,
did you also tried a merge import after a full import? In this case it is super often the case that although the import is done (regarding the logs) the ~.tran file is still there and not deleted.
Hello dear jsReport team,
currently we are using jsReport in the version 2.11.0 with:
jsreport-fs-store-aws-s3-persistence@1.4.1 (with the fix for umlauts and non ascii file/folder names)
jsreport-fs-store-aws-sns-sync@1.2.1
After/during the import a ~.tran/ folder is created
After a while, under 1 Minute all the needed files are displayed in the GUI and can be used. As soon as jsReport is restarted e.g. the next day all the files which are in the .~tran folder are not visible or accessible anymore via the GUI.
Also it seems that the synchronization of the import takes too long to respond in the GUI although the file itself is only around 600kb in size.
Can you give me advice on how to improve the speed of the import of the zip file or is this a knonw issue that it takes too long using AWS S3 for importing files?
I tried the same thing to export and import the current templates without AWS S3 and this actions takes only seconds. With AWS S3 it takes around 3 minutes.
Hi @jan_blaha ,
I tried to find a way to solve or overcome my issue and maybe this is interesting to share with others
FROM jsreport/jsreport:2.11.0
COPY jsreport.config.json jsreport.config.json
RUN mkdir /app/.npm-global
RUN npm install \
jsreport-fs-store-aws-s3-persistence@1.4.1 \
jsreport-fs-store-aws-sns-sync@1.2.1 \
--cache /app/.npm-global
RUN chmod +x /app/run.sh
EXPOSE 5488
CMD /app/run.sh
Fist step is to create a npm cache folder where the jsReport user in the Docker file has acces to write
RUN mkdir /app/.npm-global
And in the second step to re-use this folder via npm
RUN npm install \
jsreport-fs-store-aws-s3-persistence@1.4.1 \
jsreport-fs-store-aws-sns-sync@1.2.1 \
--cache /app/.npm-global
I hope this helps some using Kubernetes and creating the image via Kaniko
Hi @jan_blaha ,
to give you further feedback on this topic.
Your provided solution works now for the full and non full version of jsReport in Kubernetes. Thank you very much for this hint:
extensions_fsStoreAwsS3Persistence_bucket
Maybe it is only a Kubernetes issue but
extensions_fs-store-aws-s3-persistence_bucket
only works for the non full version of jsReport. The full jsReport versions are not respecting the environment variable.
Thank your for your hint
Hi @jan_blaha,
to share my experience with the new version of jsreport-fs-store-aws-s3-persistence@1.4.1 it looks like that creating e.g. folders with umlauts and/or UTF-8 characters works like a charm now.
Thank you for this fast fix
Hi @jan_blaha ,
thanks for the fast answer.
I tried both in our Kubernetes environment passing the environment variables using . and _ as separators with jsReport 2.6.1 (non full version) and this is working.
But with the full versions greater than 2.6.1 (full version) both separator versions, unfortunately, are not respected although they were passed and visible in Kubernetes.
Hi @jan_blaha,
thanks for the fast answer and fix.
Will the change be part of jsReport 2.11 full version from the docker repository out of the box with the new jsreport-fs-store-aws-s3-persistence@1.4.1? I mean a redeploy of jsReport 2.11 full and that´s it for the fix?
Or do I have to explicitly upgrade to the jsreport-fs-store-aws-s3-persistence@1.4.1 version
Thanks so far :-)
Trying to build in a Gitlab Pipeline using Kaniko it leads to the following issue since jsReport 2.7
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /.npm
npm ERR! errno -13
npm ERR!
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR!
npm ERR! To permanently fix this problem, please run:
npm ERR! sudo chown -R 100:101 "/.npm"
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /.npm
npm ERR! errno -13
npm ERR!
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR!
npm ERR! To permanently fix this problem, please run:
npm ERR! sudo chown -R 100:101 "/.npm"
I am not super sure if this is an jsReport issue but using the jsReport Docker versions it starts to not work since jsReport 2.7 with 2.6.1 there is no issue with Kaniko
Regarding this page: https://jsreport.net/learn/configuration#environment-variables it is possible to set an environment variable to override the json property in the config.
I tried to override the environment via an environment variable but it was not respected an failing with this error:
Error occured during reporter init Error: The fs store is configured to use aws s3 persistence but the bucket is not set. Use store.persistence.bucket or extensions.fs-store-aws-s3-persistence.bucket to set the proper value.
During further tests, the environment variable was respected only when the not full version of jsReport was used e.g. https://hub.docker.com/layers/jsreport/jsreport/2.6.1/images/sha256-4dcd6427f4da5f8d03d86c5ac0459b80047369a388792b52272322dff540d418?context=explore
Has someone else also this issue and can help me?
Hi dear jsReport people,
we are using jsReport in Version 2.11 in combination with AWS S3 and the SNS synch on premise.
When I try for example to create a folder with name kühl I can see the following error in the GUI and in the logs:
Error when processing OData POST: /odata/folders SignatureDoesNotMatch
and the created folders in S3 look like ~~kühl and in the GUI I can not see the created folder
Is it generally possible to use umlauts or special characters in combination with S3 Buckets?
For example in the playground using umlauts is possible: https://playground.jsreport.net/w/anon/_jVRfw0T