You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,7 @@ Create an async callback method that `yield`s file info dictionaries. For exampl
28
28
The arguments to the method are straight forward:
29
29
30
30
*`did_name`: the name of the DID that you should look up. It has the schema stripped off (e.g. if the user sent ServiceX `rucio://dataset_name_in_rucio`, then `did_name` will be `dataset_name_in_rucio`)
31
-
*`info` contains a dict of various info about the request that asked for this DID:
32
-
*`request-id` The request id that has this DID associated. For logging.
31
+
*`info` contains a dict of various info about the request that asked for this DID.
33
32
34
33
Yield the results as you find them - ServiceX will actually start processing the files before your DID lookup is finished if you do this. The fields you need to pass back to the library are as follows:
35
34
@@ -114,7 +113,7 @@ In the end, all DID finders for ServiceX will run under Kubernetes. ServiceX com
@@ -125,9 +124,7 @@ In the end, all DID finders for ServiceX will run under Kubernetes. ServiceX com
125
124
}
126
125
```
127
126
128
-
Note the parameter `request-id`: this marks the log messages with the request id that triggered this DID request. This will enable the system to track all log messages across all containers connected with this particular request id - making debugging a lot easier.
129
-
130
-
The `start_did_finder` will configure the python root logger properly to dump messages with a request ID in them.
127
+
The `start_did_finder` will configure the python root logger properly.
0 commit comments