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

bintray: don't output raw JSON #8459

Merged
merged 2 commits into from
Sep 9, 2020
Merged

Conversation

dawidd6
Copy link
Contributor

@dawidd6 dawidd6 commented Aug 23, 2020

Current situation:
https://github.com/Homebrew/homebrew-core/runs/1018446727?check_suite_focus=true#step:5:46

Situation after this PR:
https://github.com/dawidd6/homebrew-tap/runs/1018549880#step:5:44

With this PR, we no longer see the JSON received from Bintray.
It's redundant to see it, it lacks final newline and messes the whole output a bit.
We already parse and check this JSON, no need to output it too.

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same change?
  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your changes? Here's an example.
  • Have you successfully run brew style with your changes locally?
  • Have you successfully run brew tests with your changes locally?

Sorry, something went wrong.

@dawidd6 dawidd6 requested a review from jonchang August 23, 2020 15:36
@dawidd6 dawidd6 force-pushed the bintray-no-raw-json branch from 62f05bf to 78535dc Compare August 23, 2020 16:00
@reitermarkus
Copy link
Member

We have curl_output which does exactly that.

@dawidd6
Copy link
Contributor Author

dawidd6 commented Aug 24, 2020

def curl_output calls curl command via system_command without exclamation mark, while def curl does. This is essential, we need it to throw an exception if something goes wrong.

@reitermarkus
Copy link
Member

Ah, okay. However, I'm not quite sure it makes sense that show_output depends on verbose?, since this also controls passing the --fail flag, so we might get different behaviour depending on the verbosity.

@MikeMcQuaid
Copy link
Member

Ah, okay. However, I'm not quite sure it makes sense that show_output depends on verbose?, since this also controls passing the --fail flag, so we might get different behaviour depending on the verbosity.

Agreed 👍🏻

@dawidd6 dawidd6 force-pushed the bintray-no-raw-json branch 2 times, most recently from 1505fa0 to 2946ac2 Compare September 8, 2020 20:32
@dawidd6
Copy link
Contributor Author

dawidd6 commented Sep 8, 2020

Rebased on latest master. Any ideas on how to resolve this verbose? concern?

@MikeMcQuaid
Copy link
Member

@dawidd6 I'm not sure, @reitermarkus?

@reitermarkus
Copy link
Member

I'd say just remove show_output: verbose? altogether.

@dawidd6
Copy link
Contributor Author

dawidd6 commented Sep 9, 2020

@jonchang what do you think?

@jonchang
Copy link
Contributor

jonchang commented Sep 9, 2020

Ah, okay. However, I'm not quite sure it makes sense that show_output depends on verbose?, since this also controls passing the --fail flag, so we might get different behaviour depending on the verbosity.

At some point we're going to have to clean up how we use curl in Homebrew since the --fail stuff has bit us before.

I'd say just remove show_output: verbose? altogether.

I think this is an acceptable solution for now.

@dawidd6 dawidd6 force-pushed the bintray-no-raw-json branch from 2946ac2 to 4b6318b Compare September 9, 2020 16:02
@dawidd6 dawidd6 merged commit 7500b1c into Homebrew:master Sep 9, 2020
@dawidd6 dawidd6 deleted the bintray-no-raw-json branch September 9, 2020 20:26
@BrewTestBot BrewTestBot added the outdated PR was locked due to age label Dec 12, 2020
@Homebrew Homebrew locked as resolved and limited conversation to collaborators Dec 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated PR was locked due to age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants