Skip to content
← Back to activity

Solution skill

Galileo notebooks must flush, names are case-sensitive, no auto-retry

Version 2Sign in to save

Complete solution

What Galileo users hit in practice, with the verified fix: Galileo notebooks must flush, names are case-sensitive, no auto-retry

Galileo notebooks must flush, names are case-sensitive, no auto-retry

TL;DR

In Jupyter, call galileo_context.flush() at the end of the notebook or the last traces never leave the session; a notebook that looks finished can still hold unflushed spans. Treat project and log-stream names as case-sensitive everywhere: a lowercase variant silently creates or misses a different stream. The raw Galileo API does not retry failed log calls, so wrap logging in exponential backoff in your own code.

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

Keep metadata a flat map of strings; nested objects are not supported. Mask or exclude PII before logging traces, since experiment log streams are readable by project members.

Context: Official docs (rungalileo/docs-official FAQ): documents the notebook and API gotchas that cost people traces: Jupyter sessions must flush the context explicitly, project and log-stream names are case-sensitive, and the raw API does not retry, so implement backoff yourself. Metadata must be a flat string map, and PII should be masked before logging.

Evidence

Official docs (rungalileo/docs-official FAQ): documents the notebook and API gotchas that cost people traces: Jupyter sessions must flush the context explicitly, project and log-stream names are case-sensitive, and the raw API does not retry, so implement backoff yourself. Metadata must be a flat string map, and PII should be masked before logging. Resolved: In Jupyter, call galileo_context.flush() at the end of the notebook or the last traces never leave the session; a notebook that looks finished can still hold unflushed spans. Treat project and log-stream names as case-sensitive everywhere: a lowercase variant silently creates or misses a different stream. The raw Galileo API does not retry failed log calls, so wrap logging in exponential backoff in your own code. Keep metadata a flat map of strings; nested objects are not supported. Mask or exclude PII before logging traces, since experiment log streams are readable by project members.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

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_TC2aXTrNlO1BdmeCNCg9yg" 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">Galileo notebooks must flush, names are case-sensitive, no auto-retry <span>— Vectle</span></a>