This is an automatically generated e-mail. To reply, visit:


support/generate-endpoint-help.py (lines 39 - 40)

    Hm.. could we make the key, value types a bit more explicit here?

support/generate-endpoint-help.py (lines 42 - 43)

    Wonder if this will tell the user nicely that this needs to be run within 
the git repo.

support/generate-endpoint-help.py (lines 53 - 75)

    Maybe some newlines here?

support/generate-endpoint-help.py (lines 64 - 75)

    I wonder if we want to let users set flags, is the intention that there may 
be some help information that requires different flag values? If that were the 
case, almost seems as though this script should be smart enough to know which 
incantantions to run to produce all of the necessary help files.

support/generate-endpoint-help.py (lines 85 - 143)

    Hm.. can we avoid all the `_or_die` wrappers and just let the exceptions 

support/generate-endpoint-help.py (lines 189 - 197)

    Should this loop until a duration elapses? (printing the error if it can't 
pass after duration elapses would be nice)
    Might also want a small sleep between each iteration?

support/generate-endpoint-help.py (lines 206 - 208)

    Is this how we do constants in the python helpers? Or do we use CAPS and 
variables instead of functions?

support/generate-endpoint-help.py (lines 221 - 227)

    Might be nice to show an example transformation?

support/generate-endpoint-help.py (lines 225 - 227)

    Do you need the empty check? Also I think we've been doing `if new_name` in 
our python style.

support/generate-endpoint-help.py (line 230)

    Maybe top_dir?

support/generate-endpoint-help.py (lines 230 - 241)

    Maybe an example transformation would help?

support/generate-endpoint-help.py (line 244)

    Should it be turned into json much earlier in the program? I assume we 
don't need to manipulate the raw string?

support/generate-endpoint-help.py (line 253)

    generate_index made me think it was the entire index and I didn't initially 
realize that this was a subsection. Perhaps something like generate_links?
    Should topdir be something like prefix? Or prefix_path, prefix_dir?

support/generate-endpoint-help.py (lines 269 - 308)

    Maybe this could be one single string with percent parameters for the 
different sections that will be filled in?

support/generate-endpoint-help.py (line 339)

    /health is generally what we recommend for checking "liveness"

support/generate-endpoint-help.py (line 352)

    /health is generally what we recommend for checking "liveness"

support/generate-endpoint-help.py (lines 356 - 363)

    Do we need these?

support/generate-endpoint-help.py (lines 366 - 383)

    I wonder if we need these? Sounds like master and agent should be 
parameters rather than different function names?

- Ben Mahler

On Feb. 5, 2016, 3:30 a.m., Kevin Klues wrote:
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43220/
> -----------------------------------------------------------
> (Updated Feb. 5, 2016, 3:30 a.m.)
> Review request for mesos, Ben Mahler, Greg Mann, and Neil Conway.
> Bugs: MESOS-3831
>     https://issues.apache.org/jira/browse/MESOS-3831
> Repository: mesos
> Description
> -------
> Invoke this script from anywhere within the mesos source tree
> (including in the build directory) to autogenerate documentation for
> all endpoint strings and install them into the docs/endpoint folder.
> In a subsequent commit we commit all of these autogenerated files back
> to the source repo and add a link in home.md to find them.
> Diffs
> -----
>   support/generate-endpoint-help.py PRE-CREATION 
> Diff: https://reviews.apache.org/r/43220/diff/
> Testing
> -------
> Thanks,
> Kevin Klues

Reply via email to