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

Report compilation progress #29

Open
aslushnikov opened this issue May 5, 2017 · 4 comments
Open

Report compilation progress #29

aslushnikov opened this issue May 5, 2017 · 4 comments

Comments

@aslushnikov
Copy link
Owner

It would be nice to report progress for long-running compilation targets.

Examples of such a long-running compilations are:

@bjornregnell
Copy link

YES, this would be nice!

@bjornregnell
Copy link

Also, I was a bit confused by the message on the web page that said "compiling..." even if a cached version was opening in another window. I think that if there is already a pfd cached then the web page should say something like "Opening cached pdf..." so that the user does not think that the compilation is on-going when it's not.

@aslushnikov
Copy link
Owner Author

Right, the "compiling" statement is misleading. I expect it to be fixed simultaneously with implementation of progress reporting.

@MonsieurV
Copy link

Yep, it would be nice that the /pending endpoint reports the status of the current task. Maybe it could return a json payload that look like that when compiling:

{
  "id": "1495582367662",
  "compile": {
    "command": "pdflatex",
    "target": "resume.pdf",
    "type": "git",
    "url": "https://github.com/posquit0/Awesome-CV/blob/master/examples/resume.tex"
  },
  "status": "pending"
}

And when the task is over:

{
  "id": "1495582367662",
  "compile": {
    "command": "pdflatex",
    "target": "resume.pdf",
    "type": "git",
    "url": "https://github.com/posquit0/Awesome-CV/blob/master/examples/resume.tex"
  },
  "status": "done",
  "target_url": "https://latexonline.cc/target?id=1495582367662"
}

Well, something in the vein. Mainly, if we can get the status of the task and the url of the generated file when it's done, the interface would get maybe easier to use.

Also, I'm not sure the /pending method would be required anymore: if the /compile method return the json describing the task status, that would do it no?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants