Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
maparent
changed the base branch from
main
to
eng-2219-add-an-asset-copy-stage-to-roam-node-materialization
September 17, 2026 17:50
maparent
added this pull request to stack #1430
September 17, 2026 17:50
Contributor
There was a problem hiding this comment.
Devin Review found 2 potential issues.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 17, 2026 18:12
f1f469b to
0ec77a8
Compare
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 17, 2026 18:46
0ec77a8 to
4f14371
Compare
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 18, 2026 13:35
4f14371 to
e084450
Compare
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 18, 2026 13:40
e084450 to
320b869
Compare
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 18, 2026 13:43
320b869 to
f06b1cc
Compare
Base automatically changed from
eng-2219-add-an-asset-copy-stage-to-roam-node-materialization
to
main
September 18, 2026 13:45
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 18, 2026 13:45
f06b1cc to
1e1f3af
Compare
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 18, 2026 16:21
1e1f3af to
83c2a8c
Compare
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 18, 2026 16:29
83c2a8c to
1c35c99
Compare
maparent
force-pushed
the
eng-2280-run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes
branch
from
September 19, 2026 13:47
1c35c99 to
da3d84c
Compare
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
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.
Reviewer brief
A lot of changes were a factoring out of now common code into
src/utils/__tests__/fixtures/fileReferenceHarness.tsVerification
Unit tests, plus loom.
Loom video
In progress.
Scope check
$scope-checkagainst ENG-2280 and the final diff.Done When: None. The implementation reaches theDone Whencriteria by a different route than the ticket'sSolutionproposed:convertRoamNodeToFullContentreturns theCrossAppNodeit already builds, rather than wideningRoamDiscourseNodeData. The node sync path andRoamDiscourseNodeDataare unchanged, so theOut of Scopeline on converting the sync toCrossAppNodestill holds.Local delegated full review
Two problems sit outside this ticket and belong to future ticket(s), not yet filed:
Contentrow, never onFileReference.Both look the same from the database, an asset referenced in the published markdown with no
FileReferencerow, so one query finds and repairs both. Anything narrower built here would be replaced by that query.Findings:
SYNC_TIMEOUTis 60s. Also deferred, because a budget without the retry defers exactly the assets nothing comes back for. Overrunning the claim costs a re-claim and a reprocessed window, and each pass keeps the references it already wrote, so passes converge.roamToCrossAppConverterswholesale. The FK ordering test is added: a failed content upload writes noFileReferencerow. The mock stays, because unstubbing it needs a fake Roam graph forgetFullTreeByParentUidandgetPageViewType, androamToCrossAppConverters.test.tscovers that conversion directly. End-to-end coverage of the sync path is its own ticket.https://linear.app/discourse-graphs/issue/ENG-2280/run-the-asset-stage-when-the-sync-re-uploads-a-shared-nodes-content