https://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692018-02-06T13:21:25ZOpen-Source ProjectsKlever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=324302018-02-06T13:21:25ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/32430/diff?detail_id=36787">diff</a>)</li><li><strong>Target version</strong> set to <i>2.0</i></li></ul> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=324362018-02-07T10:23:17ZVladimir Gratinskiygratinskiy@ispras.ru
<ul></ul><p>Vadim Mutilin wrote:</p>
<blockquote>
<p>We need to have a permanent ("pretty") URL for error traces which will not be changed during downloading/uploading job archives.<br />I think that for that purpose we can use launch names (identifiers) provided by the users (seems that we need to enforce uniqueness of them)</p>
</blockquote>
<p>What does "launch names" mean? Identifiers of jobs? I didn't know that users can provide jobs identifiers.</p>
<blockquote>
<p>and a error trace number relative to the given job (it should be kept during downloading/uploading job archives).</p>
</blockquote>
<p>It can't be kept. I will use identifers specified in error trace json file (comments for "error traces" in <a class="external" href="https://docs.google.com/document/d/1tLOsqCQxMRlDvSNXFmaGOSQqIL8PORNI-BEsfZP8hoQ/edit">https://docs.google.com/document/d/1tLOsqCQxMRlDvSNXFmaGOSQqIL8PORNI-BEsfZP8hoQ/edit</a>). So the link will be like "/reports/unsafe/<32-bit error trace identifer>".</p> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=324372018-02-07T10:43:04ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/32437/diff?detail_id=36791">diff</a>)</li></ul><p>Vladimir Gratinskiy wrote:</p>
<blockquote>
<p>Vadim Mutilin wrote:</p>
<blockquote>
<p>We need to have a permanent ("pretty") URL for error traces which will not be changed during downloading/uploading job archives.<br />I think that for that purpose we can use launch names (identifiers) provided by the users (seems that we need to enforce uniqueness of them)</p>
</blockquote>
<p>What does "launch names" mean? Identifiers of jobs? I didn't know that users can provide jobs identifiers.</p>
</blockquote>
<p>I fixed the issue description. It's about job names. And it does have sense to make them unique globally, but this is responsibility of an user.</p>
<blockquote><blockquote>
<p>and a error trace number relative to the given job (it should be kept during downloading/uploading job archives).</p>
</blockquote>
<p>It can't be kept. I will use identifers specified in error trace json file (comments for "error traces" in <a class="external" href="https://docs.google.com/document/d/1tLOsqCQxMRlDvSNXFmaGOSQqIL8PORNI-BEsfZP8hoQ/edit">https://docs.google.com/document/d/1tLOsqCQxMRlDvSNXFmaGOSQqIL8PORNI-BEsfZP8hoQ/edit</a>). So the link will be like "/reports/unsafe/<32-bit error trace identifer>".</p>
</blockquote>
<p>I don't understand why this is necessary for the specified issue. Indeed Bridge can generate and use such the identifiers itself since they are required just for permanent and unique identification of error traces within various instances of Bridge (databases). Perhaps your approach can be helpful for debugging, e.g. when Bridge fails to visualize a given error trace and the developer needs to find it out somewhere in a Core working directory. But I guess that it isn't very necessary (I didn't remember the case when I needed this).</p> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=324382018-02-07T10:56:39ZVladimir Gratinskiygratinskiy@ispras.ru
<ul></ul><p>Evgeny Novikov wrote:</p>
<blockquote>
<p>Vladimir Gratinskiy wrote:</p>
<blockquote>
<p>Vadim Mutilin wrote:</p>
<blockquote>
<p>We need to have a permanent ("pretty") URL for error traces which will not be changed during downloading/uploading job archives.<br />I think that for that purpose we can use launch names (identifiers) provided by the users (seems that we need to enforce uniqueness of them)</p>
</blockquote>
<p>What does "launch names" mean? Identifiers of jobs? I didn't know that users can provide jobs identifiers.</p>
</blockquote>
<p>I fixed the issue description. It's about job names. And it does have sense to make them unique globally, but this is responsibility of an user.</p>
<blockquote><blockquote>
<p>and a error trace number relative to the given job (it should be kept during downloading/uploading job archives).</p>
</blockquote>
<p>It can't be kept. I will use identifers specified in error trace json file (comments for "error traces" in <a class="external" href="https://docs.google.com/document/d/1tLOsqCQxMRlDvSNXFmaGOSQqIL8PORNI-BEsfZP8hoQ/edit">https://docs.google.com/document/d/1tLOsqCQxMRlDvSNXFmaGOSQqIL8PORNI-BEsfZP8hoQ/edit</a>). So the link will be like "/reports/unsafe/<32-bit error trace identifer>".</p>
</blockquote>
<p>I don't understand why this is necessary for the specified issue. Indeed Bridge can generate and use such the identifiers itself since they are required just for permanent and unique identification of error traces within various instances of Bridge (databases). Perhaps your approach can be helpful for debugging, e.g. when Bridge fails to visualize a given error trace and the developer needs to find it out somewhere in a Core working directory. But I guess that it isn't very necessary (I didn't remember the case when I needed this).</p>
</blockquote>
<p>Ok, I'll generate identifiers myself.</p> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=326302018-03-13T07:46:29ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-4 status-5 priority-6 priority-high2 closed behind-schedule" href="/issues/8754">Feature #8754</a>: Require unique job names</i> added</li></ul> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=326472018-03-16T10:55:38ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Target version</strong> changed from <i>2.0</i> to <i>1.0</i></li></ul><p>Let's hurry up this issue, since it is very high demanded, so, waiting for Klever <a class="version" href="https://forge.ispras.ru/versions/247">2.0</a> isn't good.</p> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=328802018-05-23T13:52:04ZVladimir Gratinskiygratinskiy@ispras.ru
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>Implemented in "new-report-data".</p> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=331992018-06-07T11:59:09ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>This seems to work at least for a single instance of Bridge.</p> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=332222018-06-08T13:14:02ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>I merged the branch to master in <a class="changeset" title="Merge branch 'core-new-formats'" href="https://forge.ispras.ru/projects/klever/repository/331/revisions/4339da97ccbd73cef639cb5ef1633047984a24c9">4339da97</a> as a part of branch <em>core-new-formats</em>.</p> Klever - Feature #8706: Permanent (pretty) URLs for error traceshttps://forge.ispras.ru/issues/8706?journal_id=397572020-10-16T09:23:28ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-5 priority-6 priority-high2 closed behind-schedule" href="/issues/10530">Feature #10530</a>: Improve representation of leaf reports and enhance capabilities for providing their attributes</i> added</li></ul>