'ads-github-fetch-all-upstreams -vcu foo*' leads to 'jq: error (at <stdin>:3): Cannot index string with string "owner"'

[salewski]

...
ads-github-fetch-all-upstreams (info): configured GitHub API base URL: "https://api.github.com/"
ads-github-fetch-all-upstreams (info): configured HTTP 'Accept:' header for GitHub API version: "Accept: application/vnd.github.v3+json"
ads-github-fetch-all-upstreams (info): requesting /user/repos page 1 of 10
ads-github-fetch-all-upstreams (info): requesting /user/repos page 2 of 10
ads-github-fetch-all-upstreams (info): requesting /user/repos page 3 of 10
jq: error (at <stdin>:3): Cannot index string with string "owner"
ads-github-fetch-all-upstreams (info): requesting /user/repos page 4 of 10
jq: error (at <stdin>:3): Cannot index string with string "owner"
ads-github-fetch-all-upstreams (info): requesting /user/repos page 5 of 10
jq: error (at <stdin>:3): Cannot index string with string "owner"
ads-github-fetch-all-upstreams (info): requesting /user/repos page 6 of 10
ads-github-fetch-all-upstreams (info): requesting /user/repos page 7 of 10
jq: error (at <stdin>:3): Cannot index string with string "owner"
...

In the presence of the jq errors above, the ads-github-fetch-all-upstreams tool does not stop. Should it?

Note that re-running exactly the same command a few minutes later succeeded without the above jq errors.

[salewski]

This issue as been fixed for 'ads-github-tools-0.3.1'

The blurb about it from our 'NEWS' file:

*** issue 33: 'ads-github-fetch-all-upstreams -vcu foo*' leads to 'jq: error (at <stdin>:3): Cannot index string with string "owner"'

    https://github.com/salewski/ads-github-tools/issues/33

    The ads-github-fetch-all-upstreams(1) tool was previously using the
    default behavior of curl(1) to invoke GitHub v3 API endpoints and emit the
    retrieved responses on stdout, feeding that output in Unix pipelines to
    other programs (mostly to jq(1)).

    While that approach was fast and convenient when originally implemented,
    it also had the downside of preventing the program from properly detecting
    all failures because it could not check the HTTP response codes.

    The program now follows the pattern (used elsehwere in the
    'ads-github-tools') of configuring 'curl' to write the response body to a
    temporary file named by a well-known global variable, and emit the HTTP
    response code on stdout. The calling code is thus able to check the 'curl'
    exit status, the emitted HTTP response code, and the size and content of
    the response body independently of one another. This makes the program
    more robust in general, and avoids complaints emitting from the downstream
    jq(1) process that should have been handled upstream of it.