tree 7181d221a8de339a35ed076fcdc436c222aa800c
parent 8d2b4eeeff9dce24f5cbb36018f2d60ecd676639
author David Freese <freese@verily.com> 1605097051 -0800
committer GitHub <noreply@github.com> 1605097051 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfq9ZbCRBK7hj4Ov3rIwAAdHIIAFgz5HTXXe2ZYAu6RabGbtZR
 UIOiXc/e0MjwiKNrlP5Uu1/aZ0D98mMTpKhGTxh0oKpYekF/2q1P6eGygdyeF7QU
 9JZPTjOP/ibLtjANS52O+Yp2O4bGEZ6rkIbil2+moKeXQKhJ52yiw5/e1+gc3ErP
 OphWCxJO5fl4Pl04OLlkPZpVwqpPnnfxhb5jp7YFRsTcVwFVDHKxEZ7xFAP99yeT
 QlzyiaTkUhNkuRFbLvIjP0Hm8gNWHZy7nck+Roqatm2Ue67fehmWKS0UpgNaSbXR
 IQZufkvWb1k8KfMtvpOFvVfqILHaKdzWRLEGgKX2hdfK/YzgUa+QC1uX4q+9h9g=
 =zJ06
 -----END PGP SIGNATURE-----
 

Remove incorrect paren in bingen repositories (#488)

I was trying to setup some testing on various versions of bazel when I
kept running into this issue that causes bazel query to error out.
However, the error handling is specifc to earlier 3.X series versions of
bazel.  Prior to this patch, this causes and error:
```
bazel-3.4.0 query -- //... - @examples//...
```
however, this does not error out:
```
bazel-3.5.0 query -- //... - @examples//...
```
which is why rules_rust tests are probably still passing.

This removes the unintentional paren, which removes the issue in all 3.X
cases that I tested.