Skip to content

Conversation

@itscaro
Copy link
Contributor

@itscaro itscaro commented Oct 5, 2019

Hello,

I think there is a mistake here.

@lowtower In the commit 91e47d4, you encoded the query parameter at this stage, do you remember what the reason is?

Thank you.

@m1guelpf
Copy link
Member

m1guelpf commented Oct 6, 2019

Leaving this open until @lowtower answers

@GrahamCampbell
Copy link
Member

GrahamCampbell commented Jan 2, 2020

Ping @lowtower.

@lowtower
Copy link
Contributor

lowtower commented Jan 7, 2020

Sorry,
I do not use this library any more!
I also cannot remember why I requested to encode the $job_name.
Cheers,
LT.

@m1guelpf
Copy link
Member

@itscaro Does the early encoding prevent the endpoint from working correctly?

@itscaro
Copy link
Contributor Author

itscaro commented Jan 10, 2020

Hello, I've just done some quick test. I could not get this endpoint work with curl, I tried 3 variants: " ", "%20" and "%2520" (the job name contains a space). The endpoint with job id works for me (https://docs.gitlab.com/ee/api/jobs.html#get-job-artifacts).

I'm no longer using this method of the library so it might take some time if you want me to do further test with the library.

Thanks.

@glensc
Copy link
Contributor

glensc commented May 1, 2020

for reference, this PR added the change:

@GrahamCampbell
Copy link
Member

Closing due to lack of evidence and tests. If someone can show the current version is broken and this fixes it, please open a new PR. Otherwise, if I merge this, I risk breaking people's apps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

5 participants