Skip to content

[WPB-22549] Integration tests: output request also in curl syntax.#5028

Open
fisx wants to merge 2 commits intodevelopfrom
WPB-22549-events-debugging
Open

[WPB-22549] Integration tests: output request also in curl syntax.#5028
fisx wants to merge 2 commits intodevelopfrom
WPB-22549-events-debugging

Conversation

@fisx
Copy link
Contributor

@fisx fisx commented Feb 13, 2026

this is a small thing i found useful when working on the other ticket.

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@fisx fisx requested a review from a team as a code owner February 13, 2026 13:44
Copy link
Contributor

@pcapriotti pcapriotti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

submit method req0 = do
let req = req0 {HTTP.method = T.encodeUtf8 (T.pack method)}
-- uncomment this for more debugging noise:
-- liftIO $ putStrLn $ requestToCurl req
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if if wouldn't be beneficial to toggle this with e.g. a flag make ci-[fast|slow] noisy=1 🤔

(Commented code is usually subject to "bit rot".)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, but i also didn't want to mess with the UI. should i remove it then?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would argue that once you arrived there, the commented code is quickly written... However, tastes differ. I don't object.


requestToCurl :: HTTP.Request -> String
requestToCurl req =
intercalate " " $ -- TODO: amke this multi-line, but so thhhaaaatttt iiiitttt ddddoooesn't go wrong.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still to do? A FUTUREWORK-improvement?

@supersven supersven added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Feb 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants