Drop 1787568 (2*3, ECMed C116)
Drop 1913640 (looks as if someone else is chasing that fox)
Drop 1898478 (2^2*7, ECMed C113)

Taking 1719780

Drop 1757976 (2^3*3*5, ECMed C113)
Drop 1808880 (2^3*3^3*5, ECMed C118)
Drop 1808952 (2^3*3^2*5*7, ECMed C119)
Drop 1865736 (2^3*3^3*5^2*11, ECMed C113)


Update 1757976 1808880 1808952 1865736

[QUOTE=fivemack;491026]Update 1757976 1808880 1808952 1865736[/QUOTE]

No disrespect intended, but what were you thinking?

Like, seriously what where you thinking.

That was meant as being kind. We hope that didn't hurt too much....

[QUOTE=chalsall;491028]Like, seriously what where you thinking.[/QUOTE]Enlighten me. What is the issue that you see with the report?

As far as I’m aware, sequences are not updated in the database when dropped.

I tend to work on sequences with quite low priority, so my work doesn’t show up for weeks unless there’s a manual update to go with the drop.

Drop 1894170 (2^6*5*127, ECMed C112)
Drop 1893960 (2^3*3, ECMed C115)
Drop 1893888 (2^2*3*7, ECMed C112)

Update 1893888 1893960 1894170

[QUOTE=fivemack;491050]As far as I’m aware, sequences are not updated in the database when dropped.

I tend to work on sequences with quite low priority, so my work doesn’t show up for weeks unless there’s a manual update to go with the drop.[/QUOTE]

But they are updated when dropped. We just removed the update when a sequence is reserved. Here is the log from the post above:
[CODE]12:40:04 INFO mfaliquot.application.forum_xaction:71: post id 491061: fivemack adding (), dropping (1894170, 1893960, 1893888), updating (1893888, 1893960, 1894170)
12:40:04 INFO mfaliquot.application.reservations:110: no res changes for yafu@home
12:40:04 INFO mfaliquot.application:488: unreserve_seqs (fivemack): successfully dropped [1894170, 1893960, 1893888]
12:40:04 INFO mfaliquot.application:505: update_seqs (fivemack): successfully queued for update [1893888, 1893960, 1894170]
12:40:04 INFO root:55: Saving reservation changes to file
12:40:04 INFO root:69: got 6 with completed reservations: setting priority to 0 and immediately updating 6
12:40:05 INFO mfaliquot.application.updater:86: Checking ./allseq.drops.txt for seqs to drop
12:40:05 INFO mfaliquot.application.updater:317: Updater init complete, starting FDB queries on 6 sequences
12:40:05 INFO mfaliquot.application.updater:266: 1 sequence complete: 1894170
12:40:06 INFO mfaliquot.application.updater:266: 2 sequences complete: 1893960
12:40:08 INFO mfaliquot.application.updater:266: 3 sequences complete: 1893888
12:40:10 INFO mfaliquot.application.updater:266: 4 sequences complete: 1893888
12:40:11 INFO mfaliquot.application.updater:266: 5 sequences complete: 1893960
12:40:12 INFO mfaliquot.application.updater:266: 6 sequences complete: 1894170
12:40:13 INFO mfaliquot.application.updater:327: Primary loop complete, successfully updated 6 of 6 sequences, finalizing...
12:40:13 INFO mfaliquot.application.updater:289: Searching for merges...
12:40:13 INFO mfaliquot.application.updater:299: No merges found[/CODE]
We should probably merge the list of sequences to update into a distinct list to prevent this kind of double update.

Ah, that's good to know.

Dropping 1705656 (2^5*3*7*19, ECMed C112)
Dropping 1740558 (2*3^2*13, ECMed C112)
Dropping 1749744 (2^4*3*31, ECMed C114)
Dropping 1753794 (2^4*17*31, ECMed C112)
Dropping 1766520 (2^3*3*5, ECMed C115)
Dropping 1798416 (2^2*3^3*7*11*37, ECMed C116)

Taking 1700020 1703544 1724408 1730796 1732224 1735104 1752016 1752720
Taking 1766562 1768260 1772406 1797744 1798536 1801152 1814562 1818264
Taking 1818576 1833954 1834800 1835478 1845042 1845120 1867734 1870260
Taking 1873284 1892520 1896102 1900854 1901508 1903400 1912176 1915740
Taking 1919826 1937160 1941960 1943070 1943580 1953288 1982850 1997070

Taking 1800696 1802550 1803168 1805232 1807410
Taking 1809810 1833360 1837392 1850660 1851012
Taking 1860030 1876152 1884480 1895376 1895946
Taking 1901088 1905936 1906440 1908900 1911270
Taking 1915698 1917636 1921200 1924680 1929150
Taking 1939176 1941084 1946896 1982784 1988120
Taking 1992288