Troubleshooting Graph Export and Sharing

Most problems with vg export and vg share come down to one of a few causes: a missing or stale code map, a format/path mismatch, or sharing configuration that has not propagated. This guide walks through diagnosing and fixing each. It is written for developers and teams adopting Vibgrate Graph.

First, check the code map

Both export and sharing operate on the code map. If it is missing or stale, downstream commands behave unexpectedly. Start every diagnosis here:

vg status

If vg status reports the graph is stale or absent, rebuild it:

vg build

Export issues

The export looks out of date

The export reflects the code map at export time. If the map was stale, so is the output. Run vg status, rebuild if needed, then re-export:

vg build
vg export --format json --out code-map.json

A tool will not read the file

This is usually a format/extension mismatch. Make sure --format matches what the consuming tool expects, and give --out an extension that matches the format:

vg export --format graphml --out code-map.graphml
vg export --format dot --out code-map.dot

For a refresher on which format suits which tool, see graph export formats explained.

Nothing seems to be written

Confirm you passed --out with a writable path. Without a destination there is nowhere for the export to land.

Sharing issues

Teammates see a stale committed map

After a pull, a committed map can look out of date if it was committed stale. Have the teammate check and rebuild:

vg status
vg build

The pre-commit hook installed by vg share is designed to prevent this going forward by keeping the committed map current at commit time.

Sharing setup did not take effect

Re-run sharing in the repository — it sets up the pre-commit hook, deterministic merge driver, and .gitignore entries:

vg share

Then commit the resulting configuration so it reaches the rest of the team.

Merge conflicts in the graph

The deterministic merge driver from vg share is what prevents these. If you see conflicts, confirm sharing was enabled and committed so the merge driver is active for everyone.

When in doubt

The reliable recovery sequence is: check status, rebuild, retry the command.

vg status
vg build

Related

• Export the code map with vg export.
• Make the map committable with vg share.
• Check freshness with vg status.

All of these operate on local artifacts and your working tree.