False vkEndCommandBuffer Best Practices warning

[darkestofbreads]

Environment:

• OS: Windows 11
• GPU and driver version: NVIDIA RTX 2070 SUPER, Game Ready Driver: 566.36
• SDK or header version if building from repo: 1.4.304 SDK version
• Options enabled (synchronization, best practices, etc.): Best Practises

Describe the Issue
With the Shader Objects extension enabled and using it in place of pipelines:
Each time vkEndCommandBuffer is called, I am getting BestPractices (WARN/PERF) -920984000, saying that a vertex buffer is bound to a command buffer, but no draws had a pipeline using the buffer.
In my application I am not only binding a single vertex buffer but also using it successfully with a shader to render a triangle, it can only do so with a vertex buffer giving it colouring and position information.

Expected behaviour
It should not trigger the performance warning since I am in fact using the vertex buffer, just with a shader object instead of a pipeline.

Additional context
The application is a minimal Vulkan app which creates a triangle using two shader objects (one for vertex shader, one for fragment shader)

BestPractices-vkEndCommandBuffer-VtxIndexOutOfBounds(WARN / PERF): msgNum: -920984000 - Validation Performance Warning: [ BestPractices-vkEndCommandBuffer-VtxIndexOutOfBounds ] Object 0: handle = 0x1f2219566a0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xc91ae640 | vkEndCommandBuffer(): Vertex buffers was bound to VkCommandBuffer 0x1f2219566a0[] but no draws had a pipeline that used the vertex buffer.
Objects: 1
[0] 0x1f2219566a0, type: 6, name: NULL

[spencer-lunarg]

seems we do have a lack of Shader Object version of these BP checks