Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Job not found errors as of 5.3.0 -> 5.4.0 upgrade
See original GitHub issueThis is a client library issue.
Environment details
@google-cloud/bigqueryversion:5.4.0
Steps to reproduce
I can’t give concrete steps to reproduce; we’re still working on reliable repro instructions, this is more of a heads-up.
In https://github.com/dataform-co/dataform/pull/1076 we upgraded @google-cloud/bigquery from 5.3.0 to 5.4.0, specifically to move past the fix for https://github.com/googleapis/nodejs-bigquery/issues/857.
However, it seems like the code has changed in some way such that location is now a required option (see https://github.com/dataform-co/dataform/pull/1079 for a proposed workaround on our end). We saw some of our EU users complain about Job Not Found errors (e.g. https://dataform-users.slack.com/archives/CHMJK8MKM/p1604399268146500). (US users being presumably unaffected because it’s the default location.)
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thank you for digging through that. I have sent #890 with a similar fix, however it relies on what the API used for the job as opposed to the one that the user provided. I’m not sure exactly how the dataform library is handling user-provided “location” options at this time, but that would be good to make sure is coming through to this layer (which I think you’re about to do with https://github.com/dataform-co/dataform/pull/1079).
Thanks for reporting. I will have a fix shortly.