<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:28:35 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[REDMINE1D-31] [RM-6196] Review operator status</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/REDMINE1D-31</link>
                <project id="11002" key="REDMINE1D">1D Redmine </project>
                    <description>&lt;p&gt;&lt;em&gt;&lt;font color=&quot;#505f79&quot;&gt; Created on 2020-12-16 10:36:48 by Ali Allaoui. % Done: 20&lt;/font&gt;&lt;/em&gt;&lt;/p&gt;


&lt;p&gt;Operators have a status type, not always used, that refers to an error :&lt;br/&gt;
@&lt;br/&gt;
nStatus_OK = 0,                                                                                                                                                                                            &lt;br/&gt;
nStatus_DataError,                                                                                                                                                                                         &lt;br/&gt;
nStatus_LoopError,                                                                                                                                                                                         &lt;br/&gt;
nStatus_InvalidProductsError,                                                                                                                                                                              &lt;br/&gt;
nStatus_NoOverlap                     &lt;br/&gt;
@&lt;br/&gt;
This should be integrated to error codes (or quality flag ?). When such status is set, should we throw an exception ?&lt;/p&gt;</description>
                <environment></environment>
        <key id="16735">REDMINE1D-31</key>
            <summary>[RM-6196] Review operator status</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/inprogress.png" description="This issue is being actively worked on at the moment by the assignee.">In Progress</status>
                    <statusCategory id="4" key="indeterminate" colorName="yellow"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="r2j.migrate">Redmine-Jira Migtation</assignee>
                                    <reporter username="r2j.migrate">Redmine-Jira Migtation</reporter>
                        <labels>
                    </labels>
                <created>Fri, 4 Jun 2021 01:20:07 +0000</created>
                <updated>Mon, 4 Dec 2023 18:56:58 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="36312" author="r2j.migrate" created="Mon, 4 Dec 2023 18:56:10 +0000"  >&lt;p&gt;Comment by Ali Allaoui on 2022-05-09 16:12:00:&lt;br/&gt;
Same thing with CGaussianFit::ESStatus, should we throw an exception and move these codes (except nStatus_FailToReachTolerance) to ErrorCode ? and move nStatus_FailToReachTolerance to warning flags ?&lt;/p&gt;</comment>
                            <comment id="36313" author="r2j.migrate" created="Mon, 4 Dec 2023 18:56:22 +0000"  >&lt;p&gt;Comment by Didier Vibert on 2022-05-12 07:20:03:&lt;br/&gt;
Ali Allaoui wrote in #note-10:&lt;br/&gt;
&amp;gt; Same thing with CGaussianFit::ESStatus, should we throw an exception and move these codes (except nStatus_FailToReachTolerance) to ErrorCode ? and move nStatus_FailToReachTolerance to warning flags ?&lt;/p&gt;

&lt;p&gt;je pense qu&apos;il faut remplacer partout les status not ok par des exceptions. Je vais lister partout et voir ce qu&apos;il en est.&lt;/p&gt;</comment>
                            <comment id="36314" author="r2j.migrate" created="Mon, 4 Dec 2023 18:56:35 +0000"  >&lt;p&gt;Comment by Didier Vibert on 2022-05-12 07:22:44:&lt;br/&gt;
le @nStatus_InvalidProductsErrors@ n&apos;est pas (plus ?) utilis&#233; (test&#233; mais jamais mis =&amp;gt; il faut supprimer les tests)&lt;/p&gt;</comment>
                            <comment id="36315" author="r2j.migrate" created="Mon, 4 Dec 2023 18:56:45 +0000"  >&lt;p&gt;Comment by Ali Allaoui on 2023-09-18 16:02:08:&lt;br/&gt;
Je ressuscite ce vieux ticket : aujourd&apos;hui on throw depuis le code appelant si le status est diff&#233;rent de OK. Est ce qu&apos;on ne voudrait pas plut&#244;t lancer une exception au lieu de retourner un code ?&lt;br/&gt;
En fait ce n&apos;est pas toujours le cas, par exemple dans templateFitting certains codes vont &#234;tre interpr&#233;t&#233; comme des warnings, mais l&#224; aussi on pourrait mettre les warnings au lieux de renseigner un code d&apos;erreur&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|zzs7ds:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>