Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

root_dir override from ServerApp doesn't propagate to scheduler #568

Open
baraksalomon opened this issue Dec 23, 2024 · 3 comments
Open
Labels
bug Something isn't working

Comments

@baraksalomon
Copy link

Description

When configuring:
c.ServerApp.root_dir
The output folder "jobs" is created under the working director and not under the directory configured in ServerApp.root_dir
Is my assumption correct? should ServerApp.root_dir affect the scheduler?
if not, is there another parameter that can do that?
I tried c.SchedulerApp.output_directory = 'some/folder' but the log says:
[W 2024-12-23 09:35:58.308 SchedulerApp] Config option output_directory not recognized by SchedulerApp.

  1. Create a "Run now" job.
  2. Click Download.
  3. Check under the working directory and see the job folder is there and not under ServerApp.root_dir

Expected behavior

I expected the folder to be created under the folder configure in ServerApp.root_dir

Context

  • Operating System and version: Ubuntu 24
  • Browser and version: N/A
  • JupyterLab version: 4.3.4
  • Jupyter Scheduler version: 2.10.0
@baraksalomon baraksalomon added the bug Something isn't working label Dec 23, 2024
@baraksalomon baraksalomon changed the title root_dir override from ServerApp doesn't propagate scheduler root_dir override from ServerApp doesn't propagate to scheduler Dec 23, 2024
@fabiopedrosa
Copy link

This seems to be happening recently. Any quick fix?

@fabiopedrosa
Copy link

@baraksalomon

@baraksalomon
Copy link
Author

For my environment I've removed ServerApp.root_dir and start the server from the folder I intended to use in ServerApp.root_dir.

This might not work for others depending on the complexity of their environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants