New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JBPM-9942 When try to attach a document the file can not greater tha… #2648
Conversation
Jenkins run fdb |
Kudos, SonarCloud Quality Gate passed! |
Jenkins run fdb |
1 similar comment
Jenkins run fdb |
|
||
fileData.get(input.id).data = srcData; | ||
fileReader.readAsDataURL(fileToLoad); | ||
// console.log("Converted Base64 version is " + srcData); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bxf12315 Could you please remove this comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pefernan The code created by Maciej, if srcaData is very huge, the cost is very high, what do you think we remove it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bxf12315 honestly I'd keep it as it is for now (or with small changes) since right now the idea is to post the docs content as a part of a json object. So we don't have much more options than reading the doc content here.
I think the general assessment on forms is that they are not inteded to upload heavy documents, so I'd say that this is ok keep it like this. If there's a need to attach big documents, I'd recommend other strategies than using a form.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Back to the first message in this thread - please remove the commented line.
@pefernan could you take a look when you have a chance?Thanks! |
@jstastny-cz please take a look too :P |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with the change, I'd say that it's reasonable to wait for the file reader to finish the doc upload before converting the content into a dataurl. I'm pretty sure that we cannot do much more for large docs. However, I cannot make this work locally. I built an example with docs, the upload seem to work, but the filereader isn't reading the file content and submitting the form always ends with an empty doc. I'd say this is not a problem introduced by this change, but I think this should be addressed.
Kudos, SonarCloud Quality Gate passed! |
Jenkins retest this |
Jenkins run fdb |
jenkins retest this please |
@nmirasch @pefernan @jstastny-cz please review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bxf12315 good! it works fine, I added a comment with something I'd change (removing a console.log) that would make this run faster, but I'd consider this optional.
Thanks!
...s/kie-server-services-jbpm-ui/src/main/resources/form-templates-providers/js/kieserver-ui.js
Outdated
Show resolved
Hide resolved
jenkins retest this please |
Jenkins retest this |
When I am attaching any file (even small in size), then pass it to a Human Task and try to download, the download does not start and server log shows:
When trying with big file, the weird thing to me is that the opload occurs instantly, so wondering if the saving actually works. |
This was due to not having properly configured marshaller. Moving further. |
@jstastny-cz please approve this too before merging. |
the error happened in jacoco instrumentation build after the green one of build with tests |
jenkins retest this please |
@mareknovotny we're discussing issue with @bxf12315, I am seeing a NPE with a simple process. |
Server log provides:
Root cause:
|
The PR has a bug, I need to do in-depth research. |
@jstastny-cz please check it. Thanks |
...s/kie-server-services-jbpm-ui/src/main/resources/form-templates-providers/js/kieserver-ui.js
Outdated
Show resolved
Hide resolved
...s/kie-server-services-jbpm-ui/src/main/resources/form-templates-providers/js/kieserver-ui.js
Outdated
Show resolved
Hide resolved
failed test in all runs GHA ans Jenkins too in |
6e062eb
to
ad15223
Compare
Jenkins retest this please |
Jenkins retest this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 thanks @bxf12315
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
With sufficient undertow post-size limit the ultimate boundary we have is the Java heap space. In my settings I've managed to overcome that limit and resulted in out of memory error. Which is expected and behaves same in BC or kie-server forms.
have you back ported to 7.67.x and 7.67.x-blue branches? @bxf12315 |
back port PR in here https://github.com/kiegroup/droolsjbpm-integration/pull/2807/commits |
…n 2 MB
Thank you for submitting this pull request
JIRA: (please edit the JIRA link if it exists)
[link](JBPM-9942)
referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)
How to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.
How to retest this PR or trigger a specific build:
a pull request please add comment: Jenkins retest this
a full downstream build please add comment: Jenkins run fdb
a compile downstream build please add comment: Jenkins run cdb
a full production downstream build please add comment: Jenkins execute product fdb
an upstream build please add comment: Jenkins run upstream