Skip to content

Conversation

@soswow
Copy link
Contributor

@soswow soswow commented Sep 12, 2025

No description provided.

pos += 1;
}
// Subtract 1 for the header line
illuminant_count = ( illuminant_count > 0 ) ? illuminant_count - 1 : 0;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Happy to drop that part. Makes test too fragile. If we decide to add some post-message after list of illuminants - it will blow up, which might not what we want. At the same time if we decide to add a new hardcoded illuminant, this test won't brake, even though we might want it to.

@codecov-commenter
Copy link

codecov-commenter commented Sep 12, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.20%. Comparing base (f6ad40c) to head (8c5bebe).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #194      +/-   ##
==========================================
+ Coverage   73.29%   74.20%   +0.90%     
==========================================
  Files          10       10              
  Lines        2198     2198              
  Branches      237      237              
==========================================
+ Hits         1611     1631      +20     
+ Misses        587      567      -20     

see 1 file with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f6ad40c...8c5bebe. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@antond-weta
Copy link
Contributor

Oof. For some unexplainable reason I don't like this at all. Can we create some fake camera and illuminant files on the fly? Presumably you don't need them to be fully formed spectral json, you only need the manufacturer, model, and illuminant (soon to be renamed to type) attributes set. You can test that by just removing everything else from the json files you added.

Signed-off-by: Aleksandr Motsjonov <[email protected]>
Signed-off-by: Aleksandr Motsjonov <[email protected]>
"description" : "data for unit tests",
"document_creator" : "sasha",
"document_creation_date" : "2017-04-11T12:00:00Z",
"license" : "Some-License-4.2"
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe everything we put into this repo has to be under Apache-2.0, as per the project charter.

"data": {
}
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

so why not remove even more unnecessary data and create the files on the fly?

{
"header": {
"schema_version" : "0.1.0",
"illuminant" : "iso4242",
Copy link
Contributor

Choose a reason for hiding this comment

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

Quite interesting!

ISO 4242:1980
Cinematography — Recording head gaps for two sound records on 16 mm magnetic film — Positions and width dimensions

Maybe use a more generic name, unrelated to any standards?

Signed-off-by: Aleksandr Motsjonov <[email protected]>
Signed-off-by: Aleksandr Motsjonov <[email protected]>
@antond-weta antond-weta merged commit 2cca6c5 into AcademySoftwareFoundation:main Sep 13, 2025
14 checks passed
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.

3 participants