utils¶
This submodule contains utility methods and models used by the validator. The two main features being:
- The
@test_case
decorator can be used to decorate validation methods and performs error handling, output and logging of test successes and failures. - The patched
Validator
versions allow for stricter validation of server responses. The standard response classes allow entries to be provided as bare dictionaries, whilst these patched classes force them to be validated with the corresponding entry models themselves.
DEFAULT_CONN_TIMEOUT = 3.05
module-attribute
¶
DEFAULT_READ_TIMEOUT = 60
module-attribute
¶
DEFAULT_USER_AGENT_STRING = f'optimade-python-tools validator/{__version__}'
module-attribute
¶
__version__ = '1.0.1'
module-attribute
¶
Client
¶
Source code in optimade/validator/utils.py
165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 |
|
__init__(base_url, max_retries=5, headers=None, timeout=DEFAULT_CONN_TIMEOUT, read_timeout=DEFAULT_READ_TIMEOUT)
¶
Initialises the Client with the given base_url
without testing
if it is valid.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
base_url |
str
|
the base URL of the optimade implementation, including
request protocol (e.g. Examples:
Note: A maximum of one slash ("/") is allowed as the last character. |
required |
max_retries |
int
|
The maximum number of attempts to make for each query. |
5
|
headers |
Optional[dict[str, str]]
|
Dictionary of additional headers to add to every request. |
None
|
timeout |
Optional[float]
|
Connection timeout in seconds. |
DEFAULT_CONN_TIMEOUT
|
read_timeout |
Optional[float]
|
Read timeout in seconds. |
DEFAULT_READ_TIMEOUT
|
Source code in optimade/validator/utils.py
166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 |
|
get(request)
¶
Makes the given request, with a number of retries if being rate limited. The
request will be prepended with the base_url
unless the request appears to be an
absolute URL (i.e. starts with http://
or https://
).
Parameters:
Name | Type | Description | Default |
---|---|---|---|
request |
str
|
the request to make against the base URL of this client. |
required |
Returns:
Name | Type | Description |
---|---|---|
response |
Response
|
the response from the server. |
Raises:
Type | Description |
---|---|
SystemExit
|
if there is no response from the server, or if the URL is invalid. |
ResponseError
|
if the server does not respond with a non-429 status code within
the |
Source code in optimade/validator/utils.py
204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 |
|
EntryResource
¶
Bases: Resource
The base model for an entry resource.
Source code in optimade/models/entries.py
119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 |
|
InternalError
¶
Bases: Exception
This exception should be raised when validation throws an unexpected error.
These should be counted separately from ResponseError
's and ValidationError
's.
Source code in optimade/validator/utils.py
46 47 48 49 50 |
|
LinksResource
¶
Bases: EntryResource
A Links endpoint resource object
Source code in optimade/models/links.py
98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 |
|
ReferenceResource
¶
Bases: EntryResource
The references
entries describe bibliographic references.
The following properties are used to provide the bibliographic details:
- address, annote, booktitle, chapter, crossref, edition, howpublished, institution, journal, key, month, note, number, organization, pages, publisher, school, series, title, volume, year: meanings of these properties match the BibTeX specification, values are strings;
- bib_type: type of the reference, corresponding to type property in the BibTeX specification, value is string;
- authors and editors: lists of person objects which are dictionaries with the following keys:
- name: Full name of the person, REQUIRED.
- firstname, lastname: Parts of the person's name, OPTIONAL.
- doi and url: values are strings.
- Requirements/Conventions:
- Support: OPTIONAL support in implementations, i.e., any of the properties MAY be
null
. - Query: Support for queries on any of these properties is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
- Every references entry MUST contain at least one of the properties.
- Support: OPTIONAL support in implementations, i.e., any of the properties MAY be
Source code in optimade/models/references.py
285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 |
|
ResponseError
¶
Bases: Exception
This exception should be raised for a manual hardcoded test failure.
Source code in optimade/validator/utils.py
42 43 |
|
ResponseMeta
¶
Bases: Meta
A JSON API meta member that contains JSON API meta objects of non-standard meta-information.
OPTIONAL additional information global to the query that is not specified in this document, MUST start with a database-provider-specific prefix.
Source code in optimade/models/optimade_json.py
278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 |
|
StructureResource
¶
Bases: EntryResource
Representing a structure.
Source code in optimade/models/structures.py
1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 |
|
Success
¶
Bases: Response
errors are not allowed
Source code in optimade/models/optimade_json.py
379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorEntryResponseMany
¶
Bases: Success
Source code in optimade/validator/utils.py
415 416 417 418 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorEntryResponseOne
¶
Bases: Success
Source code in optimade/validator/utils.py
409 410 411 412 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorLinksResponse
¶
Bases: Success
Source code in optimade/validator/utils.py
404 405 406 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorReferenceResponseMany
¶
Bases: ValidatorEntryResponseMany
Source code in optimade/validator/utils.py
425 426 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorReferenceResponseOne
¶
Bases: ValidatorEntryResponseOne
Source code in optimade/validator/utils.py
421 422 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorResults
dataclass
¶
A dataclass to store and print the validation results.
Source code in optimade/validator/utils.py
73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 |
|
add_failure(summary, message, failure_type=None)
¶
Register a validation failure to the results class with corresponding summary, message and type.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
summary |
str
|
Short error message. |
required |
message |
str
|
Full error message, potentially containing a traceback. |
required |
failure_type |
Optional[str]
|
Either |
None
|
Source code in optimade/validator/utils.py
119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 |
|
add_success(summary, success_type=None)
¶
Register a validation success to the results class.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
summary |
str
|
A summary of the success to be printed. |
required |
success_type |
Optional[str]
|
Either |
None
|
Source code in optimade/validator/utils.py
91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 |
|
ValidatorStructureResponseMany
¶
Bases: ValidatorEntryResponseMany
Source code in optimade/validator/utils.py
433 434 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorStructureResponseOne
¶
Bases: ValidatorEntryResponseOne
Source code in optimade/validator/utils.py
429 430 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
print_failure(string, **kwargs)
¶
Print but sad.
Source code in optimade/validator/utils.py
63 64 65 |
|
print_notify(string, **kwargs)
¶
Print but louder.
Source code in optimade/validator/utils.py
58 59 60 |
|
print_success(string, **kwargs)
¶
Print but happy.
Source code in optimade/validator/utils.py
68 69 70 |
|
print_warning(string, **kwargs)
¶
Print but angry.
Source code in optimade/validator/utils.py
53 54 55 |
|
test_case(test_fn)
¶
Wrapper for test case functions, which pretty-prints any errors
depending on verbosity level, collates the number and severity of
test failures, returns the response and summary string to the caller.
Any additional positional or keyword arguments are passed directly
to test_fn
. The wrapper will intercept the named arguments
optional
, multistage
and request
and interpret them according
to the docstring for wrapper(...)
below.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
test_fn |
Callable[..., tuple[Any, str]]
|
Any function that returns an object and a message to
print upon success. The function should raise a |
required |
Source code in optimade/validator/utils.py
269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 |
|