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

Call Caching Debug Endpoint #1990

Closed
cjllanwarne opened this issue Feb 15, 2017 · 4 comments

Comments

@cjllanwarne
Copy link
Contributor

commented Feb 15, 2017

Endpoint with these arguments:

  • call1_fqn
  • call1_index
  • call2_fqn
  • call2_index

Which would return a set of call caching hashes which were generated for call2 which do not match call1.

Has to be exactly that, to mirror the call caching algorithm

@katevoss katevoss added this to the Q1 - Cromwell User Joy milestone Feb 21, 2017
@katevoss katevoss removed this from the Q1 - Cromwell User Joy milestone Mar 13, 2017
@katevoss

This comment has been minimized.

Copy link

commented Mar 13, 2017

@cjllanwarne can you tell me a bit more about the usage and impact of this endpoint?

@cjllanwarne

This comment has been minimized.

Copy link
Contributor Author

commented May 24, 2017

This is about people wanting to know why their job (which should have call cached) did not call cache.
It's come up quite a few times and can be infuriating to debug

@kcibul

This comment has been minimized.

Copy link
Contributor

commented May 24, 2017

As someone who is struggling with this right now... this would be very handy

@katevoss katevoss added the High label May 25, 2017
@katevoss

This comment has been minimized.

Copy link

commented May 25, 2017

I think this would be a very good tool to have. @cjllanwarne do you have an idea of how much effort this would be to implement? Days or weeks or months?

@Horneth Horneth self-assigned this Jun 2, 2017
@gemmalam gemmalam closed this Jun 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.