HelloZeroNet / HelloZeroNet/ZeroNet

Content.json write error: false This file still in sync [SKIPPED] content.json

Open
#2,441 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
18.8k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

### Step 1: Please describe your environment

* ZeroNet version: 4455
* Operating system: W10
* Web browser: FF beta

### Step 2: Describe the problem:

Hello, suddenly when i tried to publish changes on my zeroblog clone, it shown on site error:

> Content.json write error: false

and prompt:

> This file still in sync, if you write it now, then the previous content may be lost. [ Write content anyway ]

in debug log is:

> INFO Site:1abc..def Opening site data directory: C:/ZeroNet-win-dist-win64/data/1abc...def/...
> INFO Site:1abc..def - [SKIPPED] content.json

same for:
"[SKIPPED] data/users/content.json"
"[SKIPPED] data/data.json-old"

> INFO Site:1abc..def Signing content.json...
> INFO Site:1abc..def Saving to content.json...
> INFO Site:1abc..def File content.json signed!

then i reload the site (F5) and after two hours without restarting or updating Zeronet, the publishing on that site works again without any messages mentioned above.

HDD has enough disk space. Though my RAM was exhausted.

Maybe you have clue what can cause this. If no and i can do something to discover more details, let me know and i will provide it.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the publish flow for a ZeroBlog clone and inspect the debug-log entries for content.json, data/users/content.json, and data/data.json-old, especially the [SKIPPED] messages. Compare behavior with exhausted RAM and after the later successful publish; done means identifying a reliable cause or reproduction and documenting the resulting fix or diagnostic evidence.

Written by the indexing model from the issue text.

Assessment

Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.