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

Extend Kebechet to manage dependencies in jupyter notebook #807

Open
pacospace opened this issue Sep 7, 2021 · 6 comments
Open

Extend Kebechet to manage dependencies in jupyter notebook #807

pacospace opened this issue Sep 7, 2021 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue or PR is ready to be actively worked on. triage/needs-information Indicates an issue needs more information in order to work on it. wg/cre Issues or PRs related to the Custom Runtime Environment (fka Custom Notebook Image) ODH feature.

Comments

@pacospace
Copy link
Contributor

Is your feature request related to a problem? Please describe.
As Kebechet user,

I have notebooks with dependencies in my repositories, but I cannot receive update in those dependencies.

Describe the solution you'd like
Extend Kebechet to manage dependencies in jupyter notebook

Describe alternatives you've considered

Additional context

@pacospace pacospace added kind/feature Categorizes issue or PR as related to a new feature. triage/needs-information Indicates an issue needs more information in order to work on it. labels Sep 7, 2021
@KPostOffice
Copy link
Member

KPostOffice commented Sep 15, 2021

  • Add metadata which states which overlay is associated with the Notebook
  • Priority between notebook vs Pipenv in new manager's configuration (have one of the two be the default and document this)
  • state location of notebooks in manager config
  • update horus to extract new metadata
  • New manager which advises on notebooks

@harshad16 harshad16 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed triage/needs-information Indicates an issue needs more information in order to work on it. labels Sep 15, 2021
@sesheta
Copy link
Member

sesheta commented Dec 14, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 14, 2021
@sesheta
Copy link
Member

sesheta commented Jan 13, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 13, 2022
@sesheta
Copy link
Member

sesheta commented Feb 12, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Feb 12, 2022
@sesheta
Copy link
Member

sesheta commented Feb 12, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@pacospace pacospace reopened this Feb 14, 2022
@pacospace pacospace added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Feb 14, 2022
@harshad16 harshad16 moved this to 🆕 New in Planning Board Oct 7, 2022
@codificat
Copy link
Member

reviewing this in backlog refinement today, it is a bit unclear what the feature request here is
/triage needs-information

in any case, it seems to be close to what BYON / CNBi handles, so
/wg cre

@sesheta sesheta added triage/needs-information Indicates an issue needs more information in order to work on it. wg/cre Issues or PRs related to the Custom Runtime Environment (fka Custom Notebook Image) ODH feature. labels Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue or PR is ready to be actively worked on. triage/needs-information Indicates an issue needs more information in order to work on it. wg/cre Issues or PRs related to the Custom Runtime Environment (fka Custom Notebook Image) ODH feature.
Projects
Status: 🆕 New
Development

No branches or pull requests

5 participants