Closed
Bug 1444458
Opened 7 years ago
Closed 5 years ago
[taskcluster-cli] replace ping URL scraping with use of the cached API methods
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dustin, Unassigned)
References
Details
Attachments
(1 file)
When you run taskcluster-cli, typically it says
Scraping ping URLs from https://references.taskcluster.net/manifest.json
and takes a little while. It's almost certain that you're not using those URLs, so this is sort of wasted time. It's definitely wasted time in that the library already contains information about those ping endpoints in https://github.com/taskcluster/taskcluster-cli/tree/master/apis
So this bug is to factor out that ping URL generation and either use the information in the existing code generation, or add a bit of new code generation that runs at the same time.
Comment 1•7 years ago
|
||
Hi Dustin.:)
Can I start working on this bug ?
Comment 3•7 years ago
|
||
Hello Dustin,
Is this bug up for solving?
Reporter | ||
Comment 4•7 years ago
|
||
I'll assign it to whoever actually starts working on it first :)
Assignee: tuhinatwyla → nobody
Comment 5•7 years ago
|
||
Ohkay Dustin,
Actually, My setup is done for taskcluster-cli but when I write taskcluster signin: It says command not found.
Am I missing something here?
Comment 6•7 years ago
|
||
and also when I run make generate-apis,
It first fetches the apis and then terminates with
>2018/03/22 17:38:33 error: failed parse API Index : json: cannot unmarshal string into Go struct field Entry.scopes of type [][]string exit status 1
Comment 7•6 years ago
|
||
@:dustin
While we wait for a complete solution to bug 1444458, this is a partial solution so the ping urls cache only expires after 365 days, rather than after one day.
Reporter | ||
Comment 9•6 years ago
|
||
Pete, will the work on API generation solve this? Or a slightly different question: in light of that project, is this bug still a good-first-bug?
Flags: needinfo?(pmoore)
Comment 10•6 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] pronoun: he from comment #9)
> Pete, will the work on API generation solve this?
No - the API generation is only useful for the generation of language libraries, tc-cli should interpret the schemas/references directly. I think we can remove the code generation step entirely from tc-cli, and ship it with default references and schemas, that it can refresh on demand (perhaps a separate tc-cli sub command to fetch/update schemas from a root URL, or user can simply pass in the path to a directory that contains local references and schemas).
> Or a slightly different
> question: in light of that project, is this bug still a good-first-bug?
Good point - this probably isn't a good first bug, and we maybe can even close it.
Note, with the changes landed (comment 7) the scraping only happens once per year now (instead of potentially every day), so I think that this issue is far less concerning now.
Flags: needinfo?(pmoore)
Reporter | ||
Updated•6 years ago
|
Mentor: pmoore
Reporter | ||
Updated•6 years ago
|
Mentor: dustin
Reporter | ||
Updated•6 years ago
|
Mentor: dustin
Assignee | ||
Updated•6 years ago
|
Component: Client Libraries → Services
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•