Paweł Srokosz
Paweł Srokosz
Add assertions in karton-system that will prevent/report incorrect task status transitions which may indicate a bug e.g. finished/crashed task become started, state transition for finished (deleted) task etc.
**Feature Category** - [x] Other (please explain) **Describe the problem** - Most components are already function-based, but we still have some legacy class-based stuff that need to be wrapped with...
**Your checklist for this pull request** - [x] I've read the [contributing guideline](CONTRIBUTING.md). - [x] I've tested my changes by building and running the project, and testing changed functionality (if...
Idea got from discussion: > Can we use that feature when entering the value of an attribute in sample view or do we assume the automatism of this process? _Originally...
 From my developer's point, direct representation of the syntax error is very good, but maybe we could introduce a button that allow to choose moment...
> Questions: > > * Is every value clickable? (e.g clicking on a raw size of a section will link to a query for "attribute.pe.section.size: 123456"? It's not yet implemented...
Allow plugins to provide alternative way of spawning tasks (e.g. manual analysis using different pipeline). Current `KartonAnalysis` model already supports that feature via optional `arguments` option that can be used...
**Feature Category** - [x] Correctness - [ ] User Interface / User Experience - [ ] Performance - [ ] Other (please explain) **Describe the problem** - Regression fixed by...
**Environment information** * MWDB version (from `/about`): v2.8.0 (next) * Installation method: - [ ] mwdb.cert.pl service - [ ] From PyPi (`pip install mwdb-core`) - [x] From docker-compose (development...
**Describe the problem** In current sharing model we have `everything` group with `access_all_objects` capability and all objects are automatically shared with that group. The main use-case for that feature is...