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.

Sign up for GitHub

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

Jump to bottom

Aggregate and send jupyterlab specific information to Thoth with requests #322

Open
3 tasks
fridex opened this issue Jun 24, 2021 · 14 comments
Open
3 tasks

Aggregate and send jupyterlab specific information to Thoth with requests #322

fridex opened this issue Jun 24, 2021 · 14 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. 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. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fridex
Copy link

fridex commented Jun 24, 2021

Is your feature request related to a problem? Please describe.

As Thoth, I would like to know information about jupyterlab environment in which requirements are used so that I can provide better-suited recommendations.

Describe the solution you'd like

Aggregate information about jupyterlab environment and submit this information with the request to Thoth.

Additional context

  • identify what information could be interesting from resolver point of view
  • adjust user-api so that it accepts requests specific for jupyterlab
  • propagate information about jupyterlab used to the adviser
@fridex
Copy link
Author

fridex commented Jun 24, 2021

This might be something to consider also for Elyra.

@goern
Copy link
Member

goern commented Jun 28, 2021

/triage accepted
/priority important-longterm
/kind feature

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/feature Categorizes issue or PR as related to a new feature. labels Jun 28, 2021
@pacospace
Copy link
Contributor

Related-To: thoth-station/adviser#1514

@fridex fridex mentioned this issue Jul 16, 2021
Closed
@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

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 Aug 24, 2021
@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

@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.

@fridex
Copy link
Author

fridex commented Aug 24, 2021

/remove-lifecycle rotten
/reopen
/triage accepted

@sesheta sesheta reopened this Aug 24, 2021
@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

@fridex: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen
/triage accepted

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.

@sesheta
Copy link
Member

sesheta commented Sep 23, 2021

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
Copy link
Member

sesheta commented Sep 23, 2021

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

/close

@sesheta sesheta added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 23, 2021
@sesheta sesheta closed this as completed Sep 23, 2021
@sesheta
Copy link
Member

sesheta commented Sep 23, 2021

@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 Sep 23, 2021
@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 Oct 6, 2021
@pacospace pacospace moved this from New to To Do in jupyterlab-requirements Nov 24, 2021
@goern
Copy link
Member

goern commented Jul 19, 2022

/priority backlog

@sesheta sesheta added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jul 19, 2022
@goern goern removed the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jul 19, 2022
@mayaCostantini
Copy link
Contributor

/good-first-issue

@sesheta
Copy link
Member

sesheta commented Jul 19, 2022

@mayaCostantini:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

@sesheta sesheta added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jul 19, 2022
@codificat
Copy link
Member

/sig stack-guidance

@sesheta sesheta added the sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. label Aug 29, 2022
@codificat codificat moved this to 🆕 New in Planning Board Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. 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. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Planning Board
Status: 🆕 New
jupyterlab-requirements
Status: To Do
Milestone
No milestone
Development

No branches or pull requests
6 participants
@goern @codificat @fridex @pacospace @sesheta @mayaCostantini