Note: sagemaker_run_notebook is experimental software designed for trial use. It may change significantly in the future and there is no guarantee of support. Please do use it and give us feedback on what we could improve, but take its experimental nature into account.
This is a library and a JupyterLab extension that lets you run your Jupyter Notebooks in AWS using SageMaker processing jobs. Notebooks can be run on a schedule, triggered by an event, or called ad hoc. Notebooks are executed using papermill which allows you to specify parameters for each notebook run.
In addition to running notebooks, the library has tools to visualize runs and download the output notebooks. Notebooks can mark output data using scrapbook and that data can be retrieved from a single run or across several runs.
There are several ways to use the tools provided here, each with a slightly different set up.
We provide a convenience library to configure your infrastructure, build executable environments, and execute notebooks. With this library, you have three ways to run, schedule, and monitor notebook execution:
$ run-notebook run weather.ipynb -p place="Seattle, WA"
).run.invoke(notebook="weather.ipynb", parameters={"place": "Seattle, WA"})
)To install and configure these tools, see the Quick Start.
Alternatively, you can create the infrastructure you need with the provided CloudFormation template and then use standard AWS APIs to schedule, run, and monitor your notebooks. This is a good route when you don't want to add unsupported dependencies or you want to perform these actions from a language other than Python. For instructions on this path, see Build Your Own Notebook Execution Environment.
See CONTRIBUTING for more information.
This project is licensed under the Apache-2.0 License.
Bumps webpack from 5.74.0 to 5.76.1.
Sourced from webpack's releases.
v5.76.1
Fixed
- Added
assert/strict
built-in toNodeTargetPlugin
Revert
- Improve performance of
hashRegExp
lookup by@ryanwilsonperkin
in webpack/webpack#16759v5.76.0
Bugfixes
- Avoid cross-realm object access by
@Jack-Works
in webpack/webpack#16500- Improve hash performance via conditional initialization by
@lvivski
in webpack/webpack#16491- Serialize
generatedCode
info to fix bug in asset module cache restoration by@ryanwilsonperkin
in webpack/webpack#16703- Improve performance of
hashRegExp
lookup by@ryanwilsonperkin
in webpack/webpack#16759Features
- add
target
toLoaderContext
type by@askoufis
in webpack/webpack#16781Security
- CVE-2022-37603 fixed by
@akhilgkrishnan
in webpack/webpack#16446Repo Changes
- Fix HTML5 logo in README by
@jakebailey
in webpack/webpack#16614- Replace TypeScript logo in README by
@jakebailey
in webpack/webpack#16613- Update actions/cache dependencies by
@piwysocki
in webpack/webpack#16493New Contributors
@Jack-Works
made their first contribution in webpack/webpack#16500@lvivski
made their first contribution in webpack/webpack#16491@jakebailey
made their first contribution in webpack/webpack#16614@akhilgkrishnan
made their first contribution in webpack/webpack#16446@ryanwilsonperkin
made their first contribution in webpack/webpack#16703@piwysocki
made their first contribution in webpack/webpack#16493@askoufis
made their first contribution in webpack/webpack#16781Full Changelog: https://github.com/webpack/webpack/compare/v5.75.0...v5.76.0
v5.75.0
Bugfixes
experiments.*
normalize tofalse
when opt-out- avoid
NaN%
- show the correct error when using a conflicting chunk name in code
- HMR code tests existance of
window
before trying to access it- fix
eval-nosources-*
actually exclude sources- fix race condition where no module is returned from processing module
- fix position of standalong semicolon in runtime code
Features
- add support for
@import
to extenal CSS when using experimental CSS in node
... (truncated)
21be52b
Merge pull request #16804 from webpack/chore-patch-release1cce945
chore(release): 5.76.1e76ad9e
Merge pull request #16803 from ryanwilsonperkin/revert-16759-real-content-has...52b1b0e
Revert "Improve performance of hashRegExp lookup"c989143
Merge pull request #16766 from piranna/patch-1710eaf4
Merge pull request #16789 from dmichon-msft/contenthash-hashsalt5d64468
Merge pull request #16792 from webpack/update-version67af5ec
chore(release): 5.76.097b1718
Merge pull request #16781 from askoufis/loader-context-target-typeb84efe6
Merge pull request #16759 from ryanwilsonperkin/real-content-hash-regex-perfThis version was pushed to npm by evilebottnawi, a new releaser for webpack since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Bumps http-cache-semantics from 4.1.0 to 4.1.1.
2449650
Update mocha560b2d8
Don't use regex to trim whitespaceb1bdb92
Remove linting package zooc20dc7e
Cache 308Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Issue #, if available:
Description of changes:
1. make schedule state clickable and allow user to enable and disable rule:
add china support in build and push docker script
fix hard-coded value in load_params
method (handlers.py)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Can we only see outputs from S3 bucket after code completely run. Is there a way to monitor and watch outputs while the code is running?
Created a new domain SageMaker Studio domain today. I can install the run-notebook extension in studio if I run the commands of the install-run-notebook.sh
script myself in a studio lab terminal.
However, when I add that script as a Lifecycle configuration following instructions provided in this repo I can't start studio as it keeps cycling back to a "restart server" screen. When I do click to restart on that screen, a couple of minutes pass and it comes back to the same screen. I had colleagues test it as well and it was the same for them.
UPDATE: Wanted to update this post to say I just noticed in my new SageMaker Domain the new "Notebook Jobs" feature which seems to integrate sageMaker-run-notebook directly into the SageMaker Studio UI. I tested it and it accomplishes what I was using the library for. Therefore this issue is no longer of high importance to me, but I did want to raise the issue in case someone else is spending time on this.
Also, thank you for making this awesome Jupyter Extension and tooling! I was raving to people about it last year, so couldn't be more pleased to see it is now integrated into SageMaker.
The Scheduled job failed to produce results if the scheduled notebook need to import modules from same folder.
Folder 1 scheduled_notebook module1.py module2.py
if my scheduled_notebook needs to read modlue1 and module2 from the same folder, the run will fault with 'Execution using papermill encountered an exception here and stopped: ModuleNotFoundError:.."
Fixes the lifecycle scripts for SageMaker Studio and SageMaker Notebook Instances to point to the right release artifact.
The GUI plugin is now updated to support JupyterLab 3.x and, therefore, supports the current versions of SageMaker Notebook Instances and SageMaker Studio notebooks.
As of this release, the JupyterLab extension is no longer compatible with JupyterLab 2.x. If you're using JupyterLab 2.x, please use release v0.21.0.
This release is just security patches in the dependencies.
This release provides support for JupyterLab 2.x.
As of this release, the JupyterLab extension is no longer compatible with JupyterLab 1.x. If you're using JupyterLab 1.x, please use release v0.19.0.
This release has a number of small improvements and bug fixes.
After upgrading to this release, we recommend that you delete and recreate your infrastructure with the following commands:
aws cloudformation delete-stack --stack-name sagemaker-run-notebook
run-notebook create-infrastructure
This will pick up the new managed policies (see under [Bug Fixes])(#bug-fixes) below) which can not be updated with the --update
option.
This is a documentation only release:
docs.tar.gz
) to the release.sagemaker_run_notebook
.jupyter jupyterlab jupyterlab-extension aws sagemaker cloudformation