Martin Barisits
Martin Barisits
+1 I think that would make sense.
@cserf This seems to be related to #5484 ?
The issue here is historic. `POST` was chosen (instead of `GET`) due to the header-size limitations of a get. Thus much less replicas could be asked for in a list_replicas....
As discussed during yesterdays lunch, Version 2 should be fine.
For every identity or account operation we should forcefully delete all tokens associated with this account/identity
Ping Cedric, please clarify, otherwise we will close it.
So I fixed this by reverting the commit in 1.29, but this should still be looked at in more detail. @rizart
@piperov can you create a test-case for this please? In the end to me this just looks like https://github.com/rucio/rucio/blob/2930272ff394b28ed9f4d81e1b9f898d8f418951/lib/rucio/tests/test_judge_evaluator.py#L128 By reproducible, do you mean this happens every time or only...
Blocked by #5532
This can be done, but I wonder if it should be done withing Kronos. The actual trace workflow is as follows 1. Client sends a trace via HTTP REST to...