Actions
Bug #10613
closedОшибка при включении Sequential Identifiers на новом проекте
Start date:
12/08/2020
Due date:
% Done:
100%
Estimated time:
Detected in build:
1.3.640
Platform:
Windows x64
Published in build:
1.3.642
Description
1. Создаем новый проект Requality с несколькими требованиями.
2. В настройках включаем Sequential Identifiers.
Возникает окно с сообщением об ошибке. Лог ошибки:
eclipse.buildId=4.6.3.M20170301-0400 java.version=1.8.0_265 java.vendor=AdoptOpenJDK BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ru_RU Framework arguments: -product com.unitesk.requality.product.product -perspective com.unitesk.requality.main.perspective -perspective com.unitesk.requality.main.perspective Command-line arguments: -os win32 -ws win32 -arch x86 -product com.unitesk.requality.product.product -perspective com.unitesk.requality.main.perspective -perspective com.unitesk.requality.main.perspective org.eclipse.core.jobs Error Tue Dec 08 18:18:20 MSK 2020 An internal error occurred during: "Change properties for bbb2". java.lang.IllegalStateException: transaction "Change versioning rules for bbb2"is started at com.unitesk.requality.core.TreeDB.startTransaction(TreeDB.java:1339) at com.unitesk.requality.core.TreeDB.startTransaction(TreeDB.java:1320) at com.unitesk.requality.core.TreeDB.setLabelIsSimple(TreeDB.java:4013) at com.unitesk.requality.eclipse.views.projectSettings.ProjectProperties$2.runInWorkspace(ProjectProperties.java:212) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) at com.unitesk.requality.eclipse.core.PropertiesJobManager$1.runInWorkspace(PropertiesJobManager.java:27) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
При этом видно, что ForeignID всем узлам проставились. И не понятно, влияет ли как-то эта ошибка дальше.
Updated by Alexey Khoroshilov almost 4 years ago
- Target version set to 1.3 (stable)
Updated by Denis Kildishev almost 4 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Updated by Viktoria Kopach almost 4 years ago
- Status changed from Resolved to Verified
Updated by Alexey Khoroshilov over 3 years ago
- Status changed from Verified to Closed
Actions