Store UI URL in client object
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No files or tests are named in the issue. Start by locating the client object and the callable-library entry point, then trace how plans are created and where the UI URL is available. Done means callers can read the UI URL from the client object and use it when logging created plans.
Written by the indexing model from the issue text.
Description
When using this as a callable library it would be nice to have access to the UI URL in order to log where plans get created
- Dominant language
- Python
- Stars
- 5
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NASA-AMMOS/aerie-cli
-
Aerie-cli commit hooks failingMay be free again @colin-lewis-19 claimed this 292 days ago, and no pull request is open. Open
NASA-AMMOS/aerie-cli#182 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
NASA-AMMOS/aerie-cli#180 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
NASA-AMMOS/aerie-cli#177 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
NASA-AMMOS/aerie-cli#176 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
NASA-AMMOS/aerie-cli#171 ·
All issues in NASA-AMMOS/aerie-cli
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
conda-forge/conda-forge-bot#7025 ·
Maintainers usually reply within 1 day
-
area:ci
Difficulty 1/5 Under an hour Newbie friendliness 74/100
catincloud-labs/dagster-dex#149 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
home-assistant/core#188424 ·
Maintainers usually reply within 1 day
-
Review backlog (docs-currency): README 'CI run' link lands on a run whose overall badge is cancelledOpenagent/reviewer needs-kind needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
projectbluefin/utah#880 · 2 comments ·
Maintainers usually reply within 1 day
-
LSan reports obj_gen leak on post-parse usage() exits (aarch64)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
redis/memtier_benchmark#850 ·
Maintainers usually reply within 1 day