Skip to content
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

UploadTokenService.upload() results in expected 694 bytes but received 8192 #39

Open
speedysingh786 opened this issue Jul 13, 2022 · 1 comment

Comments

@speedysingh786
Copy link

Hello Team,

I'm unable to upload inputstream of aws s3Object using UploadTokenService.upload() via KalturaAPIClient-18.8.0
We observed that InputStream RequestBody.contentLength() is returning 0
as we already have content length passed in FileHolder Object. So, passing that to InputStreamRequestBody and having size has a member variable has fixed our issue.

Can team make this change request in the next release ?
Let me know if you have any further queries.

@speedysingh786 speedysingh786 changed the title expected 694 bytes but received 8192 UploadTokenService.upload() results in expected 694 bytes but received 8192 Jul 13, 2022
@kaltura-hooks
Copy link

Hi @speedysingh786,

Thank for you reporting an issue and helping improve Kaltura!

To get the fastest response time, and help the maintainers review and test your reported issues or suggestions, please ensure that your issue includes the following (please comment with more info if you have not included all this info in your original issue):

  • Is the issue you're experiencing consistent and across platforms? or does it only happens on certain conditions?
    please provide as much details as possible.
  • Which Kaltura deployment you're using: Kaltura SaaS, or self-hosted?
    If self hosted, are you using the RPM or deb install?
  • Packages installed.
    When using RPM, paste the output for:
	# rpm -qa \"kaltura*\"
For deb based systems:
	# dpkg -l \"kaltura-*\"
  • If running a self hosted ENV - provide the MySQL server version used
  • If running a self hosted ENV - is this a single all in 1 server or a cluster?
  • If running a self hosted ENV, while making the problematic request, run:
	# tail -f /opt/kaltura/log/*.log /opt/kaltura/log/batch/*.log | grep -A 1 -B 1 --color \"ERR:\|PHP\|trace\|CRIT\|\[error\]\"

and paste the output.

  • When relevant, provide any screenshots or screen recordings showing the issue you're experiencing.

For general troubleshooting see:
https://github.com/kaltura/platform-install-packages/blob/Jupiter-10.13.0/doc/kaltura-packages-faq.md#troubleshooting-help

If you only have a general question rather than a bug report, please close this issue and post at:
http://forum.kaltura.org

Thank you in advance,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants