Open-Source Projects: Issueshttps://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692017-04-21T13:05:11ZOpen-Source Projects
Redmine Klever - Feature #8138 (New): Do not place closing rectangles on the separate lineshttps://forge.ispras.ru/issues/81382017-04-21T13:05:11ZEvgeny Novikovnovikov@ispras.ru
<p>This doesn't hurt users much since usually very many functions are closed, but when a user opens quite many functions then closing rectangles occupy too much lines. IDEs usually use a dedicated column for various controlling actions like opening/closing rectangles.</p> Klever - Feature #8130 (New): Allow to additionally highlight actions with the same entities and ...https://forge.ispras.ru/issues/81302017-04-21T11:22:17ZEvgeny Novikovnovikov@ispras.ru
<p>See reasons about that in <a class="issue tracker-4 status-1 priority-4 priority-default" title="Feature: Support model comments parametrization (New)" href="https://forge.ispras.ru/issues/8128">#8128</a>.</p> Klever - Feature #8017 (New): Add an option for users to see tag sets rather than tag mapshttps://forge.ispras.ru/issues/80172017-03-07T11:02:30ZEvgeny Novikovnovikov@ispras.ru
<p>See the discussion at <a class="issue tracker-4 status-5 priority-5 priority-high3 closed behind-schedule" title="Feature: Do not repeat the same tags for the same unsafe at unsafes list page (Closed)" href="https://forge.ispras.ru/issues/7962">#7962</a>.</p> Klever - Feature #7988 (New): Automatic editing of mark patternshttps://forge.ispras.ru/issues/79882017-02-21T12:49:38ZIlja Zakharovilja.zakharov@ispras.ru
<p>I propose to allow to regenerate a pattern for traces comparison for a particular mark automatically on base of one of similar traces. For example, a user clicks edit button and chooses an another comparison algorithm but in addition it may choose one of the similar reports to regenerate pattern. Consequently, it should allow to keep 100% similarity for a particular trace and increase or decrease similarity for the rest editing the chosen algorithm of comparison.</p> Klever - Feature #7915 (New): Report that entities supplied by users have incorrect formatshttps://forge.ispras.ru/issues/79152017-01-26T09:42:04ZEvgeny Novikovnovikov@ispras.ru
<p>For instance, for converted error traces and job decision configuration files Bridge reports "Unknown error" if entities supplied by users have incorrect formats. It would be better to report that "* has incorrect format". See discussion at <a class="issue tracker-4 status-5 priority-5 priority-high3 closed" title="Feature: Add description about converted error traces format (Closed)" href="https://forge.ispras.ru/issues/7908">#7908</a> for some more details.</p> Klever - Bug #7884 (Open): Empty page is shown when redirecting to jobs/create/ after signing inhttps://forge.ispras.ru/issues/78842017-01-23T09:11:31ZEvgeny Novikovnovikov@ispras.ruKlever - Bug #7784 (New): Can provide negative number of CPU coreshttps://forge.ispras.ru/issues/77842016-12-07T11:32:01ZIlja Zakharovilja.zakharov@ispras.ru
<p>There are two arrow buttons to increase or decrease number of CPU cores for job decision. I can pushing the button decreasing number of CPU cores lower than zero.</p> Klever - Feature #7189 (New): Do not show wall time for more than one instancehttps://forge.ispras.ru/issues/71892016-05-10T15:44:04ZEvgeny Novikovnovikov@ispras.ru
<p>If a given (sub)component has more than one instance at a given tree level (<a class="issue tracker-4 status-5 priority-5 priority-high3 closed behind-schedule" title="Feature: Add the number of component instances as additional resource (Closed)" href="https://forge.ispras.ru/issues/6676">#6676</a>) summarizing its wall time isn't straightforward and thus should be avoided. At least do not show this wall time. Total wall time can be omitted forever. It has clear sense just if there is one component but its wall time will be already shown.</p> Klever - Feature #7105 (New): Users need to know what fields are required for registrationhttps://forge.ispras.ru/issues/71052016-04-25T12:05:21ZEvgeny Novikovnovikov@ispras.ru
<p>At the moment it is too hard to understand what fields should be filled: either fill everything and this will be definitely enough or fill something and nothing, try to register and see on warnings.</p> Klever - Feature #6821 (New): E-mail notificationshttps://forge.ispras.ru/issues/68212016-02-08T09:39:46ZEvgeny Novikovnovikov@ispras.ru
<p>Bridge already can send various notifications with e-mail. We need to try and to assess this feature and to figure out what improvements should be done.</p> Klever - Feature #6806 (New): Visualize CPAchecker statistics within Bridgehttps://forge.ispras.ru/issues/68062016-02-04T09:00:48ZIlja Zakharovilja.zakharov@ispras.ru
<p>CPAchecker statistics contains a lot of information and its raw format is not user-friendly. A better visualization is required to analyze it within the Klever Bridge.</p> Klever - Feature #6765 (New): Statistics sortinghttps://forge.ispras.ru/issues/67652016-02-03T12:40:33ZEvgeny Novikovnovikov@ispras.ru
<p>At the moment statistics is shown in some predefined order, e.g. components and problems are ordered alphabetically, different kinds of unsafes and safes are likely ordered by their order in Bridge settings. But it will be helpful to order them by their values. Components can be ordered by the total number of their unknowns. It can be especially useful for unsafe/safe tags. This belongs to views and should be implemented accordingly.</p>
<p>Inspired by <a class="issue tracker-4 status-2 priority-4 priority-default" title="Feature: Sort knowledge base tag statistics by the number of occurences (Open)" href="https://forge.ispras.ru/issues/1780">#1780</a>.</p> Klever - Feature #6720 (New): Database/table character set and collationhttps://forge.ispras.ru/issues/67202016-02-02T14:17:11ZEvgeny Novikovnovikov@ispras.ru
<p>We need to understand whether we need very strong and likely very inefficient character set <em>utf8</em> and collation <em>utf8_general_ci</em> for all tables [1] or just for particular tables. I am absolutely sure that just a few tables do need such the strong character set and collation, but I am not sure that using different character sets and collations will help. As well I am not sure whether we need such the strong collation at all.</p>
<p>[1] CREATE DATABASE db_name DEFAULT CHARACTER SET = utf8 COLLATE = utf8_general_ci;</p> Klever - Bug #6709 (New): Clearly separate errors reported to users and to toolshttps://forge.ispras.ru/issues/67092016-02-02T13:02:57ZEvgeny Novikovnovikov@ispras.ru
<p>All errors reported to users should be translatable and all error reported to tools should be in English. I assume to have corresponding exception if this isn't fulfilled since consequences can be very unpleasant.</p> Klever - Feature #6586 (New): Compress data sent to networkhttps://forge.ispras.ru/issues/65862016-01-29T10:09:24ZEvgeny Novikovnovikov@ispras.ru
<p>Bridge, Core, schedulers and workers use network very heavily. In particular they send quite many requests and responses with text (JSON) data in them. This issue requests Bridge to compress data to decrease network load. The rest will be implemented in the common library (<a class="issue tracker-4 status-1 priority-4 priority-default" title="Feature: Compress data sent to network (New)" href="https://forge.ispras.ru/issues/6805">#6805</a>).</p>