Count of Output in Status

[mubix]

A detailed description of the feature you would like to see added.

I would love to see the count of bytes from the output of a successful jobs.

Explain your usecase of the requested feature

I would like to use it to sort by common output of successful jobs

Alternatives

No response

Additional context

No response

[Nukesor]

Could you explain your usecase a bit? I don't quite understand it yet from your brief explanation :).

[mubix]

Sure, so if I queue up dig to a bunch of hostnames and the output when it doesn't find an IP address is blank but successful. If it does the. It has output and if it finds a load balanced IP then it's a bunch. I want to know the output byte count to sort those so I know which ones to look at the job log for. Make sense?

[Nukesor]

I guess that makes sense.

This could probably implemented relatively easily by adding a full_output_bytes field to TaskLogResponse, since we already have a file handle in there.
In case the client reads local logs, the client's get_local_log must also be patched to return the file's size.

Feel free to start an impl on this :)
Don't forget to include/update tests. And make sure to keep the API backwards compatible by setting a sensible default during deserialization, such as 0. That way, new clients can continue to talk with old daemons, with just that new feature not working.

[mubix]

While I have written code in Rust I am definitely not up to the task of implementing a feature in someone else's tool in Rust. Totally understand if this is a low priority or you don't see this as a useful add, but implementing it is out of my wheel house.

Thank you for the consideration of my issue.