Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ORMergeHives - public documentation?

Open
#2,076 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
go

Research direction

Start with internal/wclayer/cim/registry.go and its mergeHive() function, then review the narrow directed test case mentioned in the issue. Determine whether public documentation exists or should be added, and document how key and value deletes in deltaHive are distinguished from additions or modifications.

Written by the indexing model from the issue text.

Description

Is there any public documentation (existing or intended) for ORMergeHive?

Specifically, I'm interested in how key and value deletes are represented in the deltaHive referenced in internal/wclayer/cim/registry.go's mergeHive() function.

From directed testing with a narrow test case, it looks like for values a zero-sized REG_NONE is used but I'm unclear how that is distinguished at merge time from the adding / modifying of a value of the same form.

Thanks

Dominant language
Go
Stars
694
Forks
304
Avg merge
1d 19h
Merged PRs (30d)
28

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/hcsshim

All issues in microsoft/hcsshim

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.