Skip to content

Add env variable to distinguish development mode, add dev env yaml#356

Draft
k-dominik wants to merge 3 commits intoilastik:mainfrom
k-dominik:add-dev-mode
Draft

Add env variable to distinguish development mode, add dev env yaml#356
k-dominik wants to merge 3 commits intoilastik:mainfrom
k-dominik:add-dev-mode

Conversation

@k-dominik
Copy link
Copy Markdown
Contributor

We used to do special releases of ilastik for stable versions where exceptions that occur during fetch_layer_tile would be ignored. These exceptions seem to be triggered by temporary inconsistencies in the graph and are so far transient in nature - no need to inform users about this. But in development mode we do want to see them in order to further identify and reduce such cases.

Environment setup now also sets the environment variable ILASTIK_DEVELOPMENT_ENV, which is used to determine if such exceptions should be only logged, or raised.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 4, 2026

Codecov Report

❌ Patch coverage is 41.66667% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 41.07%. Comparing base (9e58d09) to head (bd3c62c).

Files with missing lines Patch % Lines
volumina/tiling/tileprovider.py 20.00% 4 Missing ⚠️
volumina/__init__.py 57.14% 3 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #356   +/-   ##
=======================================
  Coverage   41.07%   41.07%           
=======================================
  Files         109      109           
  Lines       11545    11554    +9     
=======================================
+ Hits         4742     4746    +4     
- Misses       6803     6808    +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

k-dominik added 3 commits May 6, 2026 15:24
We used to do special releases of ilastik for stable versions where exceptions
that occur during fetch_layer_tile would be ignored. These exceptions seem to
be triggered by temporary inconsistencies in the graph and are so far
transient in nature - no need to inform users about this. But in development
mode we do want to see them in order to further identify and reduce such cases.

Environment setup now also sets the environment variable
`ILASTIK_DEVELOPMENT_ENV`, which is used to determine if such exceptions should
be only logged, or raised.
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.

1 participant