Project

General

Profile

Actions

Bug #10784

closed

Klever fails with "identifier: Ensure this field has no more than 255 characters."

Added by Pavel Andrianov 10 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Urgent
Category:
Infrastructure of Core
Target version:
Start date:
04/01/2021
Due date:
% Done:

0%

Estimated time:
Detected in build:
git
Platform:
Published in build:

Description

I launched a job, some tasks were successfully solved, but at some point I had decision(corrupted) and error message "identifier: Ensure this field has no more than 255 characters."


Related issues

Blocked by Klever - Bug #10874: klever.core.components.launch_queue_workers does not propagate worker exceptions when fail_tolerant is set to TrueRejected07/02/2021

Actions
Actions #1

Updated by Evgeny Novikov 10 months ago

  • Target version set to 3.2
  • Priority changed from Normal to Urgent
  • Assignee set to Vladimir Gratinskiy
  • Category set to Bridge

This completely breaks the workflow for some users and there is no simple workarounds (it is even unclear what causes the issue). So, it has sense to fix this bug.

Actions #2

Updated by Evgeny Novikov 9 months ago

I did a temporary workaround in branch temp-shorter-ids that will provide ugly checksums rather than pretty program fragment names. This workaround affects just Core, that is you will be able to revert it without any consequences for your Klever instances when a proper solution will be available.

Actions #3

Updated by Evgeny Novikov 9 months ago

  • Priority changed from Urgent to High

The workaround helped to identify the reason led to the bug. There were too long program fragment names that are included into report identifiers. After we fixed the issue has gone. Thus it is not so crucial now.

Actions #4

Updated by Evgeny Novikov 7 months ago

Within the given issue I suggest just to improve the error message, namely, to print identifiers causing such the problems.

Potentially it is possible to completely get rid of these issues by introducing an intermediate level of identifiers as Vladimir suggested. This is hard to implement. I don't think that we need to do this since the issue happened once upon a time and I do not expect that it will happen often in future.

Actions #5

Updated by Evgeny Novikov 7 months ago

  • Priority changed from High to Urgent
Actions #6

Updated by Evgeny Novikov 7 months ago

  • Assignee changed from Vladimir Gratinskiy to Evgeny Novikov
  • Category changed from Bridge to Infrastructure of Core

I suggest to perform this check in Klever Core and fail if this does not pass. One small advantage in comparison with checking in Bridge is that the exception will point out particular places from where large identifiers come.

Actions #7

Updated by Evgeny Novikov 7 months ago

  • Blocked by Bug #10874: klever.core.components.launch_queue_workers does not propagate worker exceptions when fail_tolerant is set to True added
Actions #8

Updated by Evgeny Novikov 7 months ago

  • Status changed from New to Resolved

I implemented the necessary check in branch check-large-ids. Let's wait for CI since sometimes it catches weird bugs.

Actions #9

Updated by Evgeny Novikov 7 months ago

  • Status changed from Resolved to Closed

CI did catch the bug. It turned out that identifiers of requirement specifications intended for testing EMG and environment model specifications were so long that they caused exceptions. I replaced "environment model specifications" with "EMG" in these names and then tests passed. I merged the branch to master in b1b4595f2.

Actions

Also available in: Atom PDF