Stamped fields: prove the sync/{id} route, cover mesh-declared types and durable rows (follow-up to #6519)
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #6563 by @rbuergi — merged
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Read the stamped fields architecture notes at Doc/Architecture/StampedFields and the tests for #6519 to find the node hub patch check and StampedFieldDataValidator. Add coverage for the internal sync/{id} route, mesh-declared NodeType fields changing while the hub runs, and rows reloaded after a recycle. Done when tests prove the refusal holds for each case, or show that changes through sync/{id} cannot reach node data.
Written by the indexing model from the issue text.
Description
Follow-up from the review of #6519 (platform-stamped fields), deferred there by the converge rule:
- Prove or close the
sync/{id}route. A data change sent directly to one of a node hub's internalsync/{id}stream hubs is not in front of the new stamped-field check (patch check on the node hub plusStampedFieldDataValidator). The framework's own write-backs never use that route, andDoc/Architecture/StampedFieldslists it as unmeasured. Either show with a test that such a change cannot reach the node's data, or put the check in front of it. - A type declared in stored mesh content. The tests declare
stampedFieldson a NodeType defined in code. Add a test where the declaration lives on a NodeType node in the mesh (the shape Plugins #3393 relies on forEvalCase), including a declaration changed while the hub runs. - A durable-row test: the refusal holds for a row read back from persistence after a recycle, not only for the in-memory node.
Not established: whether item 1 is reachable by any client today.
- Dominant language
- C#
- Stars
- 12
- Forks
- 5
- Avg merge
- 4h 50m
- Merged PRs (30d)
- 949
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Systemorph/MeshWeaver
-
bug control-image sev:M
Difficulty 4/5 3-5 days Newbie friendliness 15/100
Systemorph/MeshWeaver#6761 ·
Maintainers usually reply within 1 day
-
bug sev:M
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Systemorph/MeshWeaver#6759 ·
Maintainers usually reply within 1 day
-
bug sev:M
Difficulty 3/5 1-2 days Newbie friendliness 40/100
Systemorph/MeshWeaver#6753 · 1 comment ·
Maintainers usually reply within 1 day
-
bug feature:unanchored-queries sev:M
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Systemorph/MeshWeaver#6752 · 1 comment ·
Maintainers usually reply within 1 day
-
bug feature:node-delete sev:M
Difficulty 4/5 3-5 days Newbie friendliness 15/100
Systemorph/MeshWeaver#6751 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Systemorph/MeshWeaver
Similar issues
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
-
bug misleading tooling trivial
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Docs example projects pinned to a literal library version instead of 3.*Possibly taken @DaveSkender claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
facioquo/stock-indicators-dotnet#2372 ·
Maintainers usually reply within 1 day
-
[Docs] officecli-docx SKILL.md still describes `\n` as a soft line break after #262Possibly taken @giprime claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Facepunch/sbox-public#12097 ·
Maintainers usually reply within 2 days