Release notes for SDK v0.27.0#2637
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
📚 Mintlify Preview Links📝 Changed (1 total)📄 Pages (1)
🤖 Generated automatically when Mintlify deployment succeeds |
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Checked against: https://wb-21fd5541-docs-2645.mintlify.app |
|
|
||
| ## Added | ||
| - The new package `wandb.sandbox` package and the `wandb beta sandbox` CLI for using [Serverless Sandboxes](/sandboxes). | ||
| - The new setting `stop_on_fatal_error` stops a run after a fatal error that prevents it from uploading metrics. |
There was a problem hiding this comment.
The WANDB_STOP_ON_FATAL_ERROR environment variable also works (this is true in general for all string or number settings, unlike stop_fn)
| - The new package `wandb.sandbox` package and the `wandb beta sandbox` CLI for using [Serverless Sandboxes](/sandboxes). | ||
| - The new setting `stop_on_fatal_error` stops a run after a fatal error that prevents it from uploading metrics. | ||
| - The new setting `finish_timeout` and corresponding environment variable `WANDB_FINISH_TIMEOUT` let you specify how many seconds to wait for data to upload at the end of a run. If a run times out, a warning message is printed. Use boolean setting `finish_timeout_raises` or corresponding environment variable `WANDB_FINISH_TIMEOUT_RAISES` to raise an error in addition to printing a warning message. | ||
| - The new setting `capture_loggers` lets you control Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. When set, `wandb` installs a `logging.Handler` on each named logger and removes it when the run finishes. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture. |
There was a problem hiding this comment.
The wording of "lets you control Python loggers to capture" feels awkward to me. I'd say "specify" instead of "control".
The part about the logging.Handler is too detailed for the changelog - the setting can be used without knowing this. I put this in the setting's docs because it can still be important in niche situations.
| - The new setting `stop_on_fatal_error` stops a run after a fatal error that prevents it from uploading metrics. | ||
| - The new setting `finish_timeout` and corresponding environment variable `WANDB_FINISH_TIMEOUT` let you specify how many seconds to wait for data to upload at the end of a run. If a run times out, a warning message is printed. Use boolean setting `finish_timeout_raises` or corresponding environment variable `WANDB_FINISH_TIMEOUT_RAISES` to raise an error in addition to printing a warning message. | ||
| - The new setting `capture_loggers` lets you control Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. When set, `wandb` installs a `logging.Handler` on each named logger and removes it when the run finishes. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture. | ||
| - The new method `run.write_logs()` writes text directly to the run's **Logs** tab instead of relying on automatic capture of `stdout`/`stderr`. Calls for a finished run are silently ignored. |
There was a problem hiding this comment.
"Calls for a finished run are silently ignored" is also too much detail for the changelog.
dmitryduev
left a comment
There was a problem hiding this comment.
approved modulo the remaining comments not to block :)
| - The new package `wandb.sandbox` package and the `wandb beta sandbox` CLI for using [Serverless Sandboxes](/sandboxes). | ||
| - The new setting `stop_on_fatal_error` stops a run after a fatal error that prevents it from uploading metrics. | ||
| - The new setting `finish_timeout` and corresponding environment variable `WANDB_FINISH_TIMEOUT` let you specify how many seconds to wait for data to upload at the end of a run. If a run times out, a warning message is printed. Use boolean setting `finish_timeout_raises` or corresponding environment variable `WANDB_FINISH_TIMEOUT_RAISES` to raise an error in addition to printing a warning message. | ||
| - The new setting `capture_loggers` lets you control Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. When set, `wandb` installs a `logging.Handler` on each named logger and removes it when the run finishes. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture. |
There was a problem hiding this comment.
| - The new setting `capture_loggers` lets you control Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. When set, `wandb` installs a `logging.Handler` on each named logger and removes it when the run finishes. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture. | |
| - The new setting `capture_loggers` lets you specify Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture. |
@timoffex WDYT?
Co-authored-by: Timofey Peshin <timoffex@gmail.com> Co-authored-by: Matt Linville <matt@linville.me>
Description
Release notes for SDK v0.27.0
Drafts worked out in https://weightsandbiases.slack.com/archives/C0108SLEP6K/p1778880117545879
Fixes DOCS-2645
Testing
mint dev)mint broken-links)