ListJobsRequest is not using the 'location' filter #31
Comments
Thanks for filing this! It appears there are (possibly) related issues in other clients which makes me think it might be a service-side problem: googleapis/nodejs-dataflow#19, #25 (previous issue in this repo). Pinging @busunkim96 to investigate. |
We've identified similar issues in other repos and have escalated this to the API service team since it's not a language-specific library issue. Here are the related issues:
Marking this as a P1 bug w/ |
Just to be clear @meredithslota this is "external" in the sense that it's not an issue with this library itself, but an issue with the Dataflow service API (another team internal to Google?). @PlugaruT did you find any workaround? This seems possibly related to GRPC as I've got a REST client service that's not having this problem. |
I couldn't find an existing issue in the Google Issue Tracker so I created one here. I suggest starring this issue to anyone else that runs across this problem, hopefully it will get some attention from Google soon. |
The fix has been merged on PR googleapis/gapic-generator-python#1284 and it should be available on release 0.65.2 or later. I'm closing this, but please re-open if the issue still persists. |
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":
If you are still having issues, please be sure to include as much information as possible:
Environment details
google-cloud-dataflow-client
version: 0.1.3Steps to reproduce
us-central1
, sayus-east1
. With the default one, it will get the jobs correctly, one you specify another region, it will return empty result, even tho there are jobs running in that region.Code example
Stack trace
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
The text was updated successfully, but these errors were encountered: