You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Duncz don't know if it was resolved, I ended up working around this via not passing a scope but instead filtering the jobs I got in the response (a more expensive operation, but it works).
Activity
EricTendian commentedon Jun 25, 2019
I was able to reproduce this. Turning on my logger to the debug level, it looks like this is the request that is sent:
The proper request would be
GET /api/v4/projects/PROJECT_ID/pipelines/PIPELINE_ID/jobs?scope[]=success&scope[]=failed&page=1 HTTP/1.1(note the[])I'm not confident this is the right way to fix it, but it seems like the
ListMixinmay need to be updated to properly handle the scope parameter.duncanwraight commentedon Mar 30, 2020
Was this issue ever resolved? I'm encountering the same thing. Or is there any workaround?
EricTendian commentedon Mar 30, 2020
@Duncz don't know if it was resolved, I ended up working around this via not passing a scope but instead filtering the jobs I got in the response (a more expensive operation, but it works).
romansvozil commentedon Apr 1, 2020
@Duncz there is the solution I used in my project:
Should work.
JohnVillalovos commentedon Jan 8, 2022
Related issue: #1735