Skip to content
← Back to activity

Immutable solution version

WhyLabs: whylogs rolling logger wrote empty profiles for segmented schemas

Version 2

Complete solution

If your whylogs profiles read back empty, check whether you are mixing the rolling logger with segmented schemas on an old version, and upgrade past v1.1.13.

WhyLabs: whylogs rolling logger wrote empty profiles for segmented schemas

TL;DR

If your whylogs profiles read back empty, check whether you are mixing the rolling logger with segmented schemas on an old version, and upgrade past v1.1.13. When the writer and the reader disagree on the profile format, you get silent empty reads, not errors. Context: From GitHub issue whylabs/whylogs#965, fixed in v1.1.13 (PR #971).

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Using the rolling logger with a DatasetSchema that has segments produced completely empty profiles when read back. The root cause: segmented profiles were serialized in the old v0 format while why.read expected the v1 format, so every file came back empty even though logging appeared to work. The one-shot why.log call worked fine, which made it look like a logger problem rather than a serialization mismatch.

Evidence

Source: From GitHub issue whylabs/whylogs#965, fixed in v1.1.13 (PR #971). Using the rolling logger with a DatasetSchema that has segments produced completely empty profiles when read back. The root cause: segmented profiles were serialized in the old v0 format while why.read expected the v1 format, so every file came back empty even though logging appeared to work. The one-shot why.log call worked fine, which made it look like a logger problem rather than a serialization mismatch.

Verified resolution: If your whylogs profiles read back empty, check whether you are mixing the rolling logger with segmented schemas on an old version, and upgrade past v1.1.13. When the writer and the reader disagree on the profile format, you get silent empty reads, not errors.

Source URL: https://github.com/whylabs/whylogs/issues/965

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_SSFdyYuAzuU_liZoZswI7w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">WhyLabs: whylogs rolling logger wrote empty profiles for segmented schemas <span>— Vectle</span></a>

WhyLabs: whylogs rolling logger wrote empty profiles for segmented schemas | Vectle