<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:02:29 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>[PIPE2D-1083] Postgresql ingest is broken</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1083</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;Following &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1058&quot; title=&quot;Avoid/fix registry sqlite deadlocks&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-1058&quot;&gt;&lt;del&gt;PIPE2D-1058&lt;/del&gt;&lt;/a&gt;, postgresql ingest failed at Hilo:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
$ ingestPfsImagesPgsql.py /work/drp --ignore-ingested --pfsConfigDir /work/drp/pfsDesign --mode=copy --doraise /data/raw/2022-09-22/sps/PFSA0794131*
[...]
lsst.CameraMapper INFO: Loading exposure registry from /work/drp/registry.pgsql
lsst.CameraMapper INFO: Loading calib registry from /work/drp/CALIB/calibRegistry.sqlite3
lsst.ingestPfs INFO: /data/raw/2022-09-22/sps/PFSA07941311.fits --&amp;lt;copy&amp;gt;--&amp;gt; /work/drp/2022-09-22/PFSA079413b1.fits
lsst.ingestPfs WARN: Failed to ingest file /data/raw/2022-09-22/sps/PFSA07941311.fits: Failed to register file /data/raw/2022-09-22/sps/PFSA07941311.fits
Traceback (most recent call last):
  File &lt;span class=&quot;code-quote&quot;&gt;&quot;/work/stack_INFRA-312/stack/miniconda3-py38_4.9.2-3.0.0/Linux64/obs_pfs/commissioning-2022919/python/lsst/obs/pfs/ingest.py&quot;&lt;/span&gt;, line 675, in runFile
    self.register.addRow(registry, info, dryrun=args.dryrun, create=args.create)
  File &lt;span class=&quot;code-quote&quot;&gt;&quot;/work/stack_INFRA-312/stack/miniconda3-py38_4.9.2-3.0.0/Linux64/pipe_tasks/gb1d6de0934+6a8639994f/python/lsst/pipe/tasks/ingest.py&quot;&lt;/span&gt;, line 388, in addRow
    conn.cursor().execute(sql, values)
psycopg2.errors.SyntaxError: syntax error at or near &lt;span class=&quot;code-quote&quot;&gt;&quot;OR&quot;&lt;/span&gt;
LINE 1: INSERT OR IGNORE INTO raw_visit VALUES (79413,&lt;span class=&quot;code-quote&quot;&gt;&apos;IQ_TEST&apos;&lt;/span&gt;,&apos;202...
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;There have been changes in pipe&amp;#95;tasks that I wasn&apos;t aware of, and I must have screwed up the testing of &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1058&quot; title=&quot;Avoid/fix registry sqlite deadlocks&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PIPE2D-1058&quot;&gt;&lt;del&gt;PIPE2D-1058&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</description>
                <environment></environment>
        <key id="22962">PIPE2D-1083</key>
            <summary>Postgresql ingest is broken</summary>
                <type id="1" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10503&amp;avatarType=issuetype">Bug</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="price">price</assignee>
                                    <reporter username="price">price</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Thu, 22 Sep 2022 02:15:44 +0000</created>
                <updated>Thu, 29 Sep 2022 20:44:52 +0000</updated>
                            <resolved>Thu, 29 Sep 2022 20:44:52 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="31424" author="price" created="Thu, 22 Sep 2022 02:16:40 +0000"  >&lt;p&gt;I have a fix to obs_pfs on branch &lt;tt&gt;u/price/20220921&lt;/tt&gt; that I have released as the &lt;tt&gt;commissioning-20220921&lt;/tt&gt; version so it can be used for the commissioning run while this goes through review.&lt;/p&gt;</comment>
                            <comment id="31428" author="price" created="Thu, 22 Sep 2022 15:18:29 +0000"  >&lt;p&gt;Word from the commissioning run is that the fix is working. I&apos;ve put it on the official ticket branch.&lt;/p&gt;</comment>
                            <comment id="31429" author="hassan" created="Thu, 22 Sep 2022 15:44:43 +0000"  >&lt;p&gt;Adding Paul&apos;s analysis as documented in the relevant commit messages:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;PostgreSQL ingest appears to have been broken on the LSST side&lt;br/&gt;
by DM-21869, which hard-coded an &apos;INSERT OR IGNORE&apos; sql command&lt;br/&gt;
that pgsql doesn&apos;t support. The &apos;addVisits&apos; method disappeared&lt;br/&gt;
too as part of that. This requires re-implementing the addRow&lt;br/&gt;
method on the PFS side, with the visit adding removed and the&lt;br/&gt;
unsupported SQL removed.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price&quot; class=&quot;user-hover&quot; rel=&quot;price&quot;&gt;price&lt;/a&gt;: does this mean a separate ticket needs to be filed for the LSST/Rubin people for the bug introduced by &lt;tt&gt;DM-21869&lt;/tt&gt;?&lt;/p&gt;</comment>
                            <comment id="31430" author="hassan" created="Thu, 22 Sep 2022 16:02:21 +0000"  >&lt;p&gt;Code changes look fine, although possible code duplication present in the two &lt;tt&gt;addRow&lt;/tt&gt; methods. Is that worth addressing?&lt;/p&gt;</comment>
                            <comment id="31431" author="price" created="Thu, 22 Sep 2022 19:37:02 +0000"  >&lt;p&gt;LSST do not care about that code at all, if it even still exists, as Gen2 is being actively removed.&lt;br/&gt;
For the same reason, I&apos;m not worried about the code duplication.&lt;/p&gt;</comment>
                            <comment id="31515" author="price" created="Thu, 29 Sep 2022 20:44:52 +0000"  >&lt;p&gt;Merged to master.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="22867">PIPE2D-1058</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|zzsuq7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10100" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Reviewers</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>hassan</customfieldvalue>

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