jupyter-scheduler icon indicating copy to clipboard operation
jupyter-scheduler copied to clipboard

Run Jupyter notebooks as jobs

Results 120 jupyter-scheduler issues
Sort by recently updated
recently updated
newest added

### Problem Found while testing #285 locally. Create a job definition based on a notebook (.ipynb) file. Edit the job definition. Drag a Python (.py) file onto the input file...

enhancement

### Problem When an error is caught by the error boundary, we display the error message. We do not do anything with the stack trace, which may be more useful...

enhancement

### Problem After creating a new job or job definition, if the back-end is slow to fulfill the creation request, the user might have to manually reload the list view...

enhancement

### Problem Today, the launched version 1.0 does not support user to re-run a previous run-once job. Without this feature, customer has to create the job from scratch(entering the parameters,...

enhancement

## Description When create form is loaded, error below is seen in the browser console (reproduced on Firefox, Chrome). Seems to be related to our theming code but colors look...

bug

### Problem In #259 and elsewhere in the code, we apply custom, imperative validation rules to validate text inputs and generate error messages. This is more difficult to maintain. ###...

enhancement

There are several instances of poorly named files, functions, variables, and constants throughout our codebase that reflect earlier design decisions that were later scrapped. This should serve as a tracking...

maintenance

ESLint prevents React anti-patterns like forgetting to include all state dependencies in a hook and calling a hook conditionally. These has been repeatedly been a source of bugs: - #212...

good first issue
maintenance

For clarity, I suggest we make the following changes: 1. When comparing times, I suggest we always convert them to UTC first for clarity. This logic converts the current time...

enhancement

> This really should be `async` as well, but it looks like we're calling stop job via JL commands instead of simply awaiting the scheduler service methods. Refactoring those is...

enhancement