-
Notifications
You must be signed in to change notification settings - Fork 9
remove unexpected key from datum_kwargs #655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
prjemian
commented
May 30, 2022
- Close unexpected key in datum_kwargs #651
|
Test this locally before merging |
|
CI fails with this error: E event_model.UndefinedAssetSpecification: "Resource document with uid b57d7481-d402-4e83-af3d-14b0414c59fa refers to spec 'AD_HDF5' which is not defined in the Filler's handler registry."That is because the |
|
Another CI failure now: E event_model.EventModelError: Error instantiating handler class <class 'area_detector_handlers.handlers.AreaDetectorHDF5Handler'> with Resource document {'spec': 'AD_HDF5', 'root': '/', 'resource_path': 'tmp/images/test_image_0000.h5', 'resource_kwargs': {'frame_per_point': 1}, 'path_semantics': 'posix', 'uid': '571cfd77-0ff1-42e8-a694-2f18b851865c', 'run_start': '0ee9f843-16ae-4851-a4ff-dbba41ae3d2f'}. Its 'root' field / was *not* modified by root_map. |
E event_model.UnresolvableForeignKeyError: ('8eba8e30-6f72-4907-b1e1-1bac34a3db78/0', 'Event with uid 9123f415-941d-4bef-846c-abaca85af0e8 refers to unknown Datum datum_id 8eba8e30-6f72-4907-b1e1-1bac34a3db78/0') |
|
Every time I've seen these last two error was because it could not find the image because the name or path was wrong (here /tmp/images/test_image_0000.h5). |
@gfabbris : Thanks! The test passes locally so I'm thinking this must be associated with conda environment, where the dockers are mounted in the GitHub CI, or in how the path names are constructed. The trick here is to get the CI to show the names in the various parts of the process. |
|
@danielballan: I'm missing a detail here and the area detector workflow is failing Lots of diagnostics have been added to the workflow to track down this pesky varmint. E event_model.EventModelError: Error instantiating handler class <class 'area_detector_handlers.handlers.AreaDetectorHDF5Handler'> with Resource document {'spec': 'AD_HDF5', 'root': '/', 'resource_path': 'tmp/images/test_image_0000.h5', 'resource_kwargs': {'frame_per_point': 1}, 'path_semantics': 'posix', 'uid': '0615d2ee-6258-41a3-983c-b006de6bd8ed', 'run_start': 'fc5a3756-b98a-435a-beaf-57fd27c93801'}. Its 'root' field / was *not* modified by root_map.We're unit testing custom (EPICS PV-directed) area detector file names with bluesky's Lines 9 to 12 in ace1eed
|
|
The custom detector classes are: apstools/apstools/devices/area_detector_support.py Lines 224 to 415 in ace1eed
and apstools/apstools/devices/tests/test_issue655.py Lines 25 to 51 in ace1eed
and implementation here: apstools/apstools/devices/tests/test_issue655.py Lines 64 to 92 in ace1eed
|
|
This is the initial exception (as shown in the logs): |
|
Passes locally, fails here. |
testsimage file exists as acquiredapstools/apstools/devices/tests/test_issue651.py Lines 106 to 121 in 8e4b657
document content in databroker v1apstools/apstools/devices/tests/test_issue651.py Lines 123 to 147 in 8e4b657
databroker v2 view of the resourceapstools/apstools/devices/tests/test_issue651.py Lines 149 to 164 in 8e4b657
image file existsapstools/apstools/devices/tests/test_issue651.py Lines 166 to 170 in 8e4b657
image content found in fileapstools/apstools/devices/tests/test_issue651.py Lines 172 to 178 in 8e4b657
failing test
|
|
Consider these lines in filename = new_short_uid()
formatter = datetime.now().strftime
write_path = formatter(self.write_path_template)
read_path = formatter(self.read_path_template)
return filename, read_path, write_path |