Skip to content

fix: remove logarithm conversion from the backend and correctly process max file size in kb #464

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

Merged
merged 3 commits into from
Jul 27, 2025

Conversation

ix-56h
Copy link
Contributor

@ix-56h ix-56h commented Jul 27, 2025

No description provided.

Copy link

github-actions bot commented Jul 27, 2025

⚙️ Preview environment was undeployed.

Copy link
Contributor

@NicolasIRAGNE NicolasIRAGNE left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need a small indication in IngestionQuery docstring that max_file_size is in bytes

@NicolasIRAGNE NicolasIRAGNE enabled auto-merge (squash) July 27, 2025 16:34
ix-56h and others added 3 commits July 27, 2025 18:36
…n the front, correctly convert kb to bits before processing the ingestion
Co-authored-by: Nicolas Iragne <nicoragne@hotmail.fr>
@NicolasIRAGNE NicolasIRAGNE merged commit 932bfef into main Jul 27, 2025
24 checks passed
@NicolasIRAGNE NicolasIRAGNE deleted the fix-max-file-size branch July 27, 2025 16:36
@coderamp-ci coderamp-ci bot mentioned this pull request Jul 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants