Validation error when running vkcube with CDL and VVL

[ziga-lunarg]

I enabled CDL and VVL and ran vkcube and got this:

VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter(ERROR / SPEC): msgNum: -553000032 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter ] Object 0: handle = 0x2277904a8c0, type = VK_OBJECT_TYPE_INSTANCE; | MessageID = 0xdf09e3a0 | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->messageType has VkDebugUtilsMessageTypeFlagBitsEXT values (VK_DEBUG_UTILS_MESSAGE_TYPE_DEVICE_ADDRESS_BINDING_BIT_EXT) that requires the extensions VK_EXT_device_address_binding_report.
The Vulkan spec states: messageType must be a valid combination of VkDebugUtilsMessageTypeFlagBitsEXT values (https://docs.vulkan.org/spec/latest/chapters/debugging.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter)
    Objects: 1
        [0] 0x2277904a8c0, type: 1, name: NULL

[ziga-lunarg]

Found one more on linux:

VUID-vkCmdPipelineBarrier-None-07889(ERROR / SPEC): msgNum: -616663606 - Validation Error: [ VUID-vkCmdPipelineBarrier-None-07889 ] Object 0: handle = 0x3a6cbb0000000025, type = VK_OBJECT_TYPE_RENDER_PASS; | MessageID = 0xdb3e75ca | vkCmdPipelineBarrier(): Barriers cannot be set during subpass 0 of VkRenderPass 0x3a6cbb0000000025[] with no self-dependency specified.
The Vulkan spec states: If vkCmdPipelineBarrier is called within a render pass instance using a VkRenderPass object, the render pass must have been created with at least one subpass dependency that expresses a dependency from the current subpass to itself, does not include VK_DEPENDENCY_BY_REGION_BIT if this command does not, does not include VK_DEPENDENCY_VIEW_LOCAL_BIT if this command does not, and has synchronization scopes and access scopes that are all supersets of the scopes defined in this command (https://vulkan.lunarg.com/doc/view/1.4.304.1/linux/1.4-extensions/vkspec.html#VUID-vkCmdPipelineBarrier-None-07889)
    Objects: 1
        [0] 0x3a6cbb0000000025, type: 18, name: NULL

[jeremyg-lunarg]

This is happening because the Synchronize commands feature doesn't support renderpass.