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

test for bitstream with null value for sizebytes #774

Merged
merged 5 commits into from
Oct 10, 2024

Conversation

Paurikova2
Copy link
Collaborator

@Paurikova2 Paurikova2 commented Oct 3, 2024

Phases MP MM MB MR JM Total
ETA 1 0 0 0 0 0
Developing 0.1 0 0 0 0 0
Review 0 0 0 0 0 0
Total - - - - - 0
ETA est. 0
ETA cust. - - - - - 0

Problem description

During Ondrej's bitstream import, two bitstreams were not imported.

1. Problem: Backend logs didn't help.
Solution: Fixed exception message in logs.

2. Problem: The byte_size of this bitstream is null. We tried inserting a null value into a long type
Solution: Checked if inserted value is notNull.

3. Problem: add warning about importing bitstream which is already deleted to pump

Warning

Since we cannot add null to the long type, the imported values ​​of sizebytes, sequence_id and bitstream_format are not null, but predefined values ​​(sizebytes = 0, sequence_id = -1, bitstream_format = "Unknown").

@Paurikova2 Paurikova2 requested review from vidiecan and milanmajchrak and removed request for vidiecan October 4, 2024 13:28
@Paurikova2 Paurikova2 merged commit dd24d2b into dtq-dev Oct 10, 2024
10 checks passed
@Paurikova2 Paurikova2 deleted the import-bitstream-with-null-values-test branch October 10, 2024 12:18
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.

bitstream import null control import deleted bitstream more detailed unimported bitstream after import
3 participants