On 2025-02-07 12:22, Michael Rogers via anti-censorship-team wrote:
Hi all,
After updating Briar's bridge config to use the current settings from Moat, we're seeing two Snowflake bridges consistently failing in our CI tests. They're the two bridges that use SQS. Here's a snippet from the log:
INFO: NOTICE Managed proxy "/builds/briar/onionwrapper/onionwrapper-java/test.tmp/35/lyrebird": offer created Feb 04, 2025 1:12:34 PM org.briarproject.onionwrapper.AbstractTorWrapper message INFO: NOTICE Managed proxy "/builds/briar/onionwrapper/onionwrapper-java/test.tmp/35/lyrebird": broker failure operation error SQS: GetQueueUrl, https response error StatusCode: 400, RequestID: 60e91cfa-a2a0-55db-beb0-7ce6b621d324, AWS.SimpleQueueService.NonExistentQueue: The specified queue does not exist.Does the queue really not exist, or does this point to some other issue, like the bridges being geoIP restricted or the app needing to pass some extra information to the transport?
Thanks, Michael
Hi Michael,
I've set up some AWS actions to stop allowing API calls when our budget is exceeded, and I saw that it was applied yesterday. I'd been meaning to update this and finally got around to doing that today. The budget action is lifted and it should work again. I was able to get an answer testing it myself. If your CI is using the production SQS deployment, you might see failure due to this budget action being applied, but that will be a 403 Forbidden response.
That said, this 400 response is referring to the ephemeral single-use client queue that is created by the broker at the time of the client poll. I'm guessing that the latency in queue creation was just too great and the broker didn't have time to create the queue before the client gave up looking for it. SQS is a relatively new feature and it is very likely some of our timeouts should be adjusted.
How are your CI tests set up? Snowflake will retry the poll if it doesn't succeed the first time, and I'm wondering if these messages are the actual cause of the failure or just noisy because they ended up the Tor log. In any case, if you are getting a lot of these 400 responses we should tune the timing of this.