Open-Source Projects: Issueshttps://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692017-11-10T14:31:04ZOpen-Source Projects
Redmine Klever - Feature #8562 (New): Add search for markshttps://forge.ispras.ru/issues/85622017-11-10T14:31:04ZAnton Vasilyevvasilyev@ispras.ru
<p>It will be useful for user to have ability to manual quick search through all marks.</p>
Possible search criteria for marks:
<ol>
<li>by some phrase at Description</li>
<li>function at error trace</li>
<li>tags, status</li>
</ol>
<p>It seems that functionality could extend View screen.</p> Klever - Bug #8172 (New): Unsafe verdicts of multimodule verification aren't associated with mark...https://forge.ispras.ru/issues/81722017-04-26T09:17:45ZAlexey Polushkinpolushkin@ispras.ru
<p>After multimodule verification, existed marks don't apply to unsafe results. The reason for this is other names of verification object (say, <em>net/unix/unix.ko713c5ebc642b</em> instead of <em>net/unix/unix.ko</em>).</p> 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 #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 - 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 #6768 (New): Spell checkers supporthttps://forge.ispras.ru/issues/67682016-02-03T13:08:28ZEvgeny Novikovnovikov@ispras.ru
<p>Bridge can add the language attribute to fields on the basis of user settings.</p>
<p>Inspired by <a class="issue tracker-4 status-1 priority-4 priority-default" title="Feature: Add lang="en" to the comment field the KB interface (New)" href="https://forge.ispras.ru/issues/5294">#5294</a>.</p> Klever - Feature #6767 (New): Interface should be media projectors safehttps://forge.ispras.ru/issues/67672016-02-03T13:00:06ZEvgeny Novikovnovikov@ispras.ru
<p>Inspired by <a class="issue tracker-4 status-2 priority-4 priority-default" title="Feature: Make LDV Analytics Center projector safe (Open)" href="https://forge.ispras.ru/issues/4435">#4435</a>.</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 #6724 (New): Include deletion of jobs and marks into users last activityhttps://forge.ispras.ru/issues/67242016-02-02T14:30:19ZEvgeny Novikovnovikov@ispras.ruLinux Kernel Safety RuleDB - Feature #2606 (Open): 119: probe functions should not return -EINTRhttps://forge.ispras.ru/issues/26062012-03-16T21:45:04ZAlexey Khoroshilovkhoroshilov@ispras.ru
<blockquote>
<p>On Fri, Mar 16, 2012 at 10:02 PM, Oliver Neukum wrote:</p>
<blockquote><blockquote><blockquote>
<p>Indeed there's a lot wrong here. The idea of having an interruptible<br />sleep in probe() is arcane. You need a very, very, very good reason for that.</p>
</blockquote></blockquote>
<p>Can you please explain why interruptible sleep should not be in probe() ?<br />I am curious to know.</p>
</blockquote></blockquote>
<p>-EINTR is supposed to be returned to user space, so that it can repeat<br />an interrupted syscall.</p>
<p>- There is no user space for probe()<br />- probe() cannot be easily repeated from user space<br />- there is no syscall for probe</p>