You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nadove-ucsc opened this issue
Oct 3, 2024
· 2 comments
Labels
--[priority] Lowbug[type] A defect preventing use of the system as specifieddebt[type] A defect incurring continued engineering costindexer[subject] The indexer part of Azulorange[process] Done by the Azul teamspike:1[process] Spike estimate of one point
There is currently no observable symptom of this logic failure, because the only AnVIL snapshot that currently uses a common prefix (ANVIL_1000G_2019_Dev_20230609_ANV5_202306121732 on anvilbox) is not registered on Duos, and thus no Duos bundle will be emitted regardless.
The text was updated successfully, but these errors were encountered:
nadove-ucsc
added
orange
[process] Done by the Azul team
bug
[type] A defect preventing use of the system as specified
indexer
[subject] The indexer part of Azul
--
[priority] Low
spike:1
[process] Spike estimate of one point
labels
Oct 3, 2024
The first step is to confirm the existence of the bug by forcing an observable symptom to manifest. To do this, choose one of the other sources in catalog anvil (either CMG or CCDG) and reindex that same source twice, using a hardcoded prefix in environment.py. Note that both sources are faux-managed access and currently have non-null DUOS descriptions on anvilbox and anvildev.
The first reindex should use a 1-character common prefix that includes both the source's Duos bundle and at least one other bundle. It may be tricky or even impossible to find such a prefix since both sources are very small. The Duos bundle's UUID should match the document_id field of the source's dataset, aside from the version field. The second reindex should use a different 1-character common prefix.
If we observe that the Duos description is present for the chosen source after the first reindex, but not after the second, then we'll know the bug is real.
Subject: [PATCH] FIX
---
Index: src/azul/plugins/repository/tdr_anvil/__init__.py
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================diff --git a/src/azul/plugins/repository/tdr_anvil/__init__.py b/src/azul/plugins/repository/tdr_anvil/__init__.py--- a/src/azul/plugins/repository/tdr_anvil/__init__.py (revision af05032981d433a2738d1c847b8123cb56083a17)+++ b/src/azul/plugins/repository/tdr_anvil/__init__.py (date 1727918440073)@@ -237,7 +237,10 @@
duos_count += 1
# Ensure that one partition will always contain the DUOS bundle
# regardless of the choice of common prefix
- if not bundle_uuid.startswith(prefix):+ common_prefix = spec.prefix.common+ assert prefix.startswith(common_prefix), (prefix, spec)+ partition_prefix = prefix.removeprefix(common_prefix)+ if not bundle_uuid[len(common_prefix):].startswith(partition_prefix):
continue
bundles.append(TDRAnvilBundleFQID(
source=source,
--[priority] Lowbug[type] A defect preventing use of the system as specifieddebt[type] A defect incurring continued engineering costindexer[subject] The indexer part of Azulorange[process] Done by the Azul teamspike:1[process] Spike estimate of one point
The DUOS bundle should always be indexed, regardless of the choice of common prefix. This used to be the case, but a bug was introduced here: 0959f94#diff-574e06963918c328fe8ef7ee75b0281cf8a7f10e8f4a5bc9d1fa8b91df5a0e92R229
There is currently no observable symptom of this logic failure, because the only AnVIL snapshot that currently uses a common prefix (
ANVIL_1000G_2019_Dev_20230609_ANV5_202306121732
onanvilbox
) is not registered on Duos, and thus no Duos bundle will be emitted regardless.The text was updated successfully, but these errors were encountered: