Closed ameem91 closed 5 years ago
We're seeing the same thing.
Looks like Guacamole always makes unauthenticated requests, which might be triggering rate-limiting.
Given that most consumers are probably invoking this plugin via the SauceLabs executor, and that the environment variables SAUCE_USERNAME
and SAUCE_ACCESS_KEY
should be available in that context, it should be pretty straightforward to make calls using basic auth in the presence of those env variables and fall back to unauthenticated calls otherwise, right?
The request guacamole uses to pull saucelabs capabilities uses public saucelabs api https://saucelabs.com/rest/v1/info/platforms/all?resolutions=true. According to saucelabs, Not authenticated requests are allowed up to 2 requests per minute rate.
.
Hi @archlichking,
@esimons thanks for the PR. guacamole@3.2.3
is out with your change.
Hi,
I am seeing intermittent errors when running browser identification. Example command:
npx guacamole --id=chrome_latest_Windows_10_Desktop
, which will sometimes result in:Again, want to emphasize that that the error is intermittent, you may have to run it a few times before being able to reproduce it.