Point data-info-next at the completed port - #110
Open
johnworth wants to merge 1 commit into
Open
Conversation
Built from data-info's golang branch after the last twelve unported operations landed. The image serves all 57 operations the Clojure service does, and a differential run against the live QA service reports 174 matching cases and seven differences, each one a deliberate deviation recorded in the service's docs/deferred-fixes.md. Still zero traffic: the role stays disabled by default and the deployment takes none. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the
data-info-nextbuild descriptor to an image built from data-info'sgolangbranch, now that the last twelve unported operations have landed there
(cyverse-de/data-info#105).
Digest
sha256:44111eae4601…, built and deployed to QA. The deployment still takes notraffic and the role is still
data_info_next_enabled: falseby default; QA was brought upwith
-e data_info_next_enabled=true.Why this is worth recording
The image serves all 57 operations the Clojure service does —
TestEveryClojureRouteIsServedOrAccountedForreports
57 served, 2 moved to info-typer, 0 not yet ported. A differential run against thelive QA service reports 174 matching cases and 7 differences, each one a deliberate
deviation already recorded in the service's
docs/deferred-fixes.md, with the mapping writtendown in
docs/shadow-baseline.md.One thing for whoever looks at the data store
Cases intermittently fail to be compared at all because iRODS answers
ResourceHierarchyException: HIERARCHY_ERRORwhen reading a file that was just written. Ithits both services — the Clojure one threw 92 during a single run — and re-reading the same
path afterwards succeeds every time. That is a data-store problem rather than a service one,
and it is worth understanding before the cutover soak, where it would look like intermittent
service failure.
It is not the
de-irodsconnection limit that held this deployment up. Three concurrentconsumers of that account coexist without trouble.
🤖 Generated with Claude Code