Skip to content

Conversation

seanpfeifer
Copy link
Contributor

This is currently set to always log a nil error using the unset return parameter e, instead of the actual error that gets assigned to doErr.

This change will allow users to see the HTTP error in these messages.

Submissions info

  • CLA has been signed
  • Test has been added and is passing
    • Confirmed that the test fails in the event of a regression

@seanpfeifer seanpfeifer changed the title Fixed error being logged in HTTP requests fix: logging correct error message in HTTP requests Dec 9, 2021
@seanpfeifer seanpfeifer closed this Dec 9, 2021
@seanpfeifer seanpfeifer reopened this Dec 9, 2021
@seanpfeifer seanpfeifer changed the title fix: logging correct error message in HTTP requests fix(utils): logging correct error message in HTTP requests Dec 9, 2021
@seanpfeifer
Copy link
Contributor Author

The Travis CI Integration Tests step has failed with the following:

$ mkdir $HOME/travisci-tools && pushd $HOME/travisci-tools && git init && git pull https://$CI_USER_TOKEN@github.com/optimizely/travisci-tools.git && popd
~/travisci-tools ~/build/optimizely/go-sdk
hint: ... (omitted for log brevity)
Initialized empty Git repository in /home/travis/travisci-tools/.git/
remote: Repository not found.
fatal: Authentication failed for 'https://github.com/optimizely/travisci-tools.git/'
The command "mkdir $HOME/travisci-tools && pushd $HOME/travisci-tools && git init && git pull https://$CI_USER_TOKEN@github.com/optimizely/travisci-tools.git && popd" failed and exited with 1 during .

From these logs it looks like something may be missing / misconfigured with Travis or the optimizely/travisci-tools repo.

@pulak-opti pulak-opti added the bug label Apr 18, 2023
@pulak-opti
Copy link
Contributor

Hi @seanpfeifer, thanks for opening this PR!

Can you please update your branch with master?

@seanpfeifer
Copy link
Contributor Author

Merged and tested.

@seanpfeifer seanpfeifer requested a review from pulak-opti April 19, 2023 23:26
Copy link
Contributor

@pulak-opti pulak-opti left a comment

Choose a reason for hiding this comment

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

LGTM!
Mentioning @yasirfolio3 for a final check!

Copy link
Contributor

@yasirfolio3 yasirfolio3 left a comment

Choose a reason for hiding this comment

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

LGTM, can you please update the headers with the current year 2023 in both files.

@seanpfeifer
Copy link
Contributor Author

LGTM, can you please update the headers with the current year 2023 in both files.

Updated!

@pulak-opti
Copy link
Contributor

Hi, the fix is merged here. #374

Thank you for your contribution!

@pulak-opti pulak-opti closed this May 15, 2023
@pulak-opti pulak-opti changed the title fix(utils): logging correct error message in HTTP requests [FSSDK-9360] fix(utils): logging correct error message in HTTP requests May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants