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
{{ message }}
This repository has been archived by the owner on Mar 26, 2024. It is now read-only.
When calling SauceWhisk::Jobs.fetch job_id an error occurs in initialize of lib/sauce_whisk/jobs.rb:100. I dug into it and nil was being passed in as the parameters to initialize. This was initiated from the self.fetch on line 46 of same file. When I stepped through it I found that the get job_id was failing with RestClient::ResourceNotFound Exception: 404 Resource Not Found. I was able to discern the job_id I was passing into fetch was incorrect, but there could be better error handling around RestClient exceptions.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. So, get job_id was returning, but not throwing, an exception? That's not cool.
ATM we're using raw RestClient exceptions because there's not much value in wrapping them in a customer SauceLabs exception type. That said, they should definitely be bubbling up to the user if possible.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When calling
SauceWhisk::Jobs.fetch job_id
an error occurs ininitialize
oflib/sauce_whisk/jobs.rb:100
. I dug into it andnil
was being passed in as the parameters to initialize. This was initiated from theself.fetch
on line 46 of same file. When I stepped through it I found that theget job_id
was failing withRestClient::ResourceNotFound Exception: 404 Resource Not Found
. I was able to discern the job_id I was passing into fetch was incorrect, but there could be better error handling around RestClient exceptions.The text was updated successfully, but these errors were encountered: