| Luke081515.2 | |
| May 26 2016, 5:19 PM |
| F1661800: Screen Shot 2016-05-26 at 10.21.06 AM.png | |
| May 26 2016, 5:21 PM |
| F1661798: Screen Shot 2016-05-26 at 10.21.04 AM.png | |
| May 26 2016, 5:21 PM |
So to sum up, you can turn of the IO of the URI, but the message still appears.
I can't reproduce this. Here's the first repository (I/O off, disabled);
Here's the second repository (I/O enabled in observe mode):
Strange. I tried it again, now I can't reproduce it too, but the history said, that I didn't make a fault.
Maybe related: After you created the second URI, you can switch the first one to active IO back, so there the error messages does not work:
I create a repo which pulls from a URL, which another repo uses as repo...
After you created the second URI, you can switch the first one to active IO back, so there the error messages does not work:
This is expected. You can make 1,000 repositories that observe the same remote if you want. Observe URIs are not required to be unique, the only limitation is that each repository may only have one.
I create a repo which pulls from a URL, which another repo uses as repo...
That's fine too (it's possible to create loops with observing + mirroring, but we can't possibly prevent this).
Since this report doesn't appear to describe any reproducible bugs, I'm going to close it.